Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

monitor number swapped #612

Closed
7sCELL opened this issue May 21, 2024 · 4 comments
Closed

monitor number swapped #612

7sCELL opened this issue May 21, 2024 · 4 comments

Comments

@7sCELL
Copy link

7sCELL commented May 21, 2024

i have 2 monitors and the numbers keep switching

2 workspaces

1 on main monitor

2 on the second

my workspaces:

workspaces:

  • name: "1"
    display_name: " "
    keep_alive: true
    bind_to_monitor: 2
  • name: "2"
    display_name: " "
    bind_to_monitor: 1

the only thing i find to fix is to reboot

@ParasiteDelta
Copy link
Contributor

Yep, this is an infamous issue. This is because, under the hood somehow, Windows re-initializes your displays when waking from sleep or cycling power to the monitors. So, to quote LGUG2Z, 1 and 2 become 4 and 3. So yes, Windows has a way of identifying monitors which does not correlate to anything displayed by your system settings, no, you cannot just directly access what the system settings say, and yes, they are actively working on it for the V3 rewrite.

Man, why is Windows such a pain to develop for? It's awful.

@AndreiArion
Copy link

AndreiArion commented May 29, 2024

As a workaround what worked for me at least once (needs more testing :) ) is to close glazeWM and delete all the window desktops (keep only one). Then when I restarted glazeWM it created the workspaces on the right monitors and with the right application to worspace/monitor.

Not ideal but still better than rebooting and might be automatised.

@888iee
Copy link

888iee commented Jun 25, 2024

I have the same issue in both my remote workspace and my personal pc. I never close environment in my workplace. So that's a hassle. I think it would be the easiest fix if we can use the display id (e.g. //LGHDDISPLAY1) instead of the display number we get from windows.

@lars-berger
Copy link
Member

Crashes and inconsistencies on display setting changes, system standby, and monitor disconnections should now be fixed in v3 🎉 Latest release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants