TheBoredTeam / boring.notch

TheBoringNotch: Not so boring notch That Rocks 🎸🎶
https://theboring.name/
Other
1.16k stars 66 forks source link

[BUG] Show on a specific display keeps changing. #174

Open ejgavin opened 4 weeks ago

ejgavin commented 4 weeks ago

Describe the bug In this bug, whenever my monitor is turned back on along with my MacBook, it switches to the monitor in the setting of show on a specific display.

To Reproduce Steps to reproduce the behavior:

  1. Choose built-in display as display to show Boring Notch on.
  2. Turn on monitor.

Expected behavior It should stay on the selected choice for the setting.

Additional context On Glowing Panda (Snooty) 2.1 and MacOS Sequoia.

CyanideSunryz commented 3 weeks ago

Issue still occurs on 2.2.

To reproduce:

  1. Connect the laptop to an external display (in my case, a projector)
  2. BoringNotch moves to the external display
  3. In settings, change it back to built-in retina display
  4. Disconnect external display
  5. Reconnect external display
  6. BoringNotch has changed its display back to the external device

Expected behaviour: It should retain the updated "Show on specific display" setting

Additional context Running Macbook Air M2 15" with Sequoia 15.1.

bronisMateusz commented 2 weeks ago

The same thing happens when you put the computer to sleep mode with the display connected and wake it up. Then almost always the boring notch jumps to the external screen and does not remain on the built-in screen.

CyanideSunryz commented 2 weeks ago

Surely the default behaviour should be to display on the built-in screen since the external monitor is highly unlikely to have a real notch? I would imagine over 99% of installs are to use the dead space there rather than to have a functional blob at the top of an external monitor?

mojst3r commented 1 week ago

Issue also happens when using 2 external monitors, the notch jumps from one display to the other when waking up from sleep. The monitor that wakes up first gets the notch.

bronisMateusz commented 1 week ago

Yup, the problem still exists. Even after a clean reinstallation of the app.

CyanideSunryz commented 1 week ago

Still exists on 2.3