"Show on display" option doesn't seem to do anything

[sotnii]

Describe the bug
I'm trying to assign my windows to a particular space, it doesn't seem to have any effect.

To Reproduce
Steps to reproduce the behavior:

1. Go to any widget
2. Put a "1" into "Show on display" input for the widget to appear only on the main (1st) screen
3. Click "Confirm changes and refresh simple-bar"

Expected behavior
Widgets should appear on their selected spaces and not appear on other spaces.

Screenshots

Example configuration for network stats

• OS version: MacOS Tahoe 26.2
• AeroSpace:
  • aerospace CLI client version: 0.20.1-Beta 66d16c068a49a6a679bde16407673d07ca10c4c0
  • AeroSpace.app server version: 0.20.1-Beta 66d16c068a49a6a679bde16407673d07ca10c4c0
• Übersicht: Version 1.6 (82)

Additional context
My monitor setup: I have 2 monitors

The main one (the one I want the network stats to appear on, not the second display)

The built-in display is used as an extended display.

Here's what lib/scripts/init-aerospace.sh spits out:

{
  "displays": [
    {
      "monitor-appkit-nsscreen-screens-id": 1,
      "monitor-id": 1,
      "monitor-name": "AQW34H3"
    },
    {
      "monitor-appkit-nsscreen-screens-id": 2,
      "monitor-id": 2,
      "monitor-name": "Built-in Retina Display"
    }
  ],
  "SIP": "System Integrity Protection status: enabled.",
  "shadow": true
}

[Jean-Tinland]

Hi! I think there was a missing piece of logic for AeroSpace (this feature is working fine with yabai).

I just pushed a fix, can you check if this is working after pulling the master branch?

Thank you for reporting this and for your help!

[sotnii]

Hi again. Thank you for quick response. I have pulled the latest commit on master (66b895e6474a).

Here's the configuration for network stats (the same as in the issue description)

I have triggered plugin refresh in Ubersicht, no luck. Then I restarted Ubersicht completely, and still network stats are shown on both displays.
Is there anything else I should do?

[Jean-Tinland]

Thanks for trying this fix! I was attempting to guess just by reading the implementation.

No, I'll try to reproduce this bug locally, then fix it properly.

I'll let you know when it is done :)