🎨 Palette: Add empty state message to results dialog

[xbmc4lyfe]

💡 What

Added an empty state message label ("No results found") to the results dialog skin XML that only appears when the items list is empty.

🎯 Why

Previously, if a search returned zero results, the dialog would present an entirely blank list area without explanation. Adding an explicit empty state gives immediate, clear feedback to the user that the query completed but yielded no matches.

📸 Before/After

Before: Dialog opened with a completely empty black background beneath the header.
After: A centered "No results found" text in gray FF9CA3AF appears exactly where the list would normally display.

♿ Accessibility

The empty state reduces cognitive load by eliminating ambiguity about whether the add-on is still loading, broken, or intentionally returning zero items.

---

PR created automatically by Jules for task 15837674836334350037 started by @xbmc4lyfe

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 267d325e-f8c0-44b1-8c11-e07687d06773

📥 Commits

Reviewing files that changed from the base of the PR and between c8dfe60 and 75e2b98.

📒 Files selected for processing (1)

• repo/plugin.video.nzbdav/resources/skins/Default/1080i/results-dialog.xml

📜 Recent review details

⏰ Context from checks skipped due to timeout. (7)

• GitHub Check: Codacy Static Code Analysis
• GitHub Check: coverage
• GitHub Check: lint
• GitHub Check: test
• GitHub Check: Analyze (python)
• GitHub Check: Scan
• GitHub Check: Analyze (python)

🔇 Additional comments (1)

repo/plugin.video.nzbdav/resources/skins/Default/1080i/results-dialog.xml (1)

65-74: LGTM!

---

📝 Walkthrough

Summary by CodeRabbit

• New Features
  • Added a centered “No results found” message when the results list is empty.

Walkthrough

The results dialog now shows a centered “No results found” label when results container 50 contains zero items.

Changes

Results empty state

Layer / File(s)	Summary
Add empty-state label repo/plugin.video.nzbdav/resources/skins/Default/1080i/results-dialog.xml	Adds a centered label over the results area. The label is visible only when Container(50).NumItems equals zero.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: ponchopig

Poem

I’m a bunny by the screen,
Watching empty results gleam.
“No results found,” the label says,
Centered neatly in its place.
Hop, hop—clarity appears!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the main change: adding an empty-state message to the results dialog.
Description check	✅ Passed	The description accurately explains the empty-state label, its condition, its purpose, and its visual placement.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch palette/results-dialog-empty-state-15837674836334350037

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch palette/results-dialog-empty-state-15837674836334350037

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-code-quality]

Code Coverage Overview

Languages: Python

Python / code-coverage/pytest

The overall coverage in commit 75e2b98 in the palette/results-dial... branch remains at 88%, unchanged from commit c8dfe60 in the main branch.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}