Explain a widget’s presence on each display in Status and runtime queries
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- macos, swift
- Domain
- desktop, developer-experience
Research direction
Start with BarStore.updatePresentations and BarStore.widgetStatus in Sources/StableBar/BarStore.swift, then trace actual placements and overflow in Sources/StableBar/BarView.swift; the issue provides links to the relevant code. Compare those paths with Settings → Status and the --query ID implementation to find where per-display presence can be reported from the active layout. Done when Status and the query agree with each display’s layout and distinguish overflow, display rules, output hiding, empty content and disabled state while preserving separate source health.
Written by the indexing model from the issue text.
Description
Problem
A widget can have a working or connected data source and still be absent from one display. The existing Status view explains source health, but it does not give one per-display answer to “Where is this widget, and why?”
The decision is split across display rules, output-driven hiding, empty content and the adaptive layout's More widgets overflow. A shared provider may run for a widget visible on one display while another instance is omitted elsewhere. A global “Connected” or “Paused” label cannot describe that distinction.
This request extends the existing Status and runtime query. It is not a new diagnostic dashboard, source-health feature, display configuration system or overflow implementation.
Proposal
For a widget in the active effective configuration, show its presence on each connected display in Settings → Status and --query ID, beside its source health:
- on the bar;
- available under More widgets;
- excluded by its effective display rule, including an output-supplied display rule;
- hidden by
output.hidden; - hidden because its relevant content is empty;
- disabled.
Keep source state, such as failed, missing access, waiting, connected or paused, separate from per-display presence. Include the effective rule or reason and the existing route to configure or troubleshoot the widget. Do not resume a hidden provider merely to inspect its state.
Acceptance
- A widget can be reported on the bar on one display and in overflow or excluded on another, without changing its global source-health label.
- Explicit output hiding and empty-content hiding are distinguishable from display filtering and overflow.
- A visible error placeholder is not reported as output-hidden when the actual presentation keeps it visible.
- Status and the query agree with the actual layout and update when display rules, output or available space change.
- Report only what the active effective configuration and current layout establish. If an ID is absent from that configuration, say so; do not invent a profile/filter explanation or promise access to removed widgets without a provenance mapping.
Possible today
Existing capability / workaround
- Settings → Status already shows health, last successful update, access requirements, shared-source impact, Refresh/Restart, explicit testing and snapshots.
- Settings → Bar already lists Not on this screen and Shows on rules. Its inspector warns about a display mismatch. Edit Bar in Place shows placeholders for output-hidden widgets and brings overflowed widgets onto the editing bar.
- Display rules and adaptive overflow are already supported. Users can manually compare those settings, script output and the More widgets popup.
The missing capability is the combined per-display explanation, not the controls themselves.
Source on main 01bf12a1a67f6083342421efa090e48213fbe62e:
BarStore.updatePresentationscomputes output/empty-content hiding, with the error-state exception.BarStore.widgetStatusreports source health, not those presence reasons.BarViewhas the actual per-display placements and overflow plan.BarInspector.widgetPanelalready gives a display-mismatch callout.
Latest stable reviewed: 0.17.0. This is a source/documentation capability review; no app interaction, build or test was performed.
Related
- #119 introduced the Status overview, on-demand snapshots and source testing. It does not provide the per-display presence breakdown requested here.
- #99 explains which configuration source overrides a property. A winning property value is useful evidence, but it is not the current layout's presence result.
- #635 keeps widgets accessible while editing a crowded bar. The requested explanation concerns normal-mode presence as well.
- #55 / #58 cover shared presentation and theme/layout behavior, not this Status/query explanation.
Triaged by OMP (closerouter/openai/gpt-6.1-sol).
- Dominant language
- Swift
- Stars
- 184
- Forks
- 12
- Avg merge
- 3h 50m
- Merged PRs (30d)
- 387
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Seb-GRAF/StableBar
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Maintainers usually reply within 1 day
-
Menu bar items drawn as in the menu bar show the wrong part of the menu bar after a display changePossibly taken @Jonathanm10 claimed this today. Openneeds-triage
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
Allow the App Menu to display the frontmost app iconPossibly taken @khatami10 claimed this today. Openenhancement needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in Seb-GRAF/StableBar
Similar issues
-
good first issue help wanted testing
Difficulty 1/5 Under an hour Newbie friendliness 78/100
-
area:cli documentation good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 94/100
isaaclins/freesnitch#430 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
MasterJ93/ATProtoKit#354 ·
-
enhancement help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
heysidhant/appvanish#4 ·
-
bug priority:low status:queued
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day