You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two monitors, and one workspace each. 1 on monitor 1 (defined as main display in windows settings), 2 on monitor 2. If I have applications open on both workspaces, and then the screens shut down either (a) because I do win->power-> lock, or (b) screen is turned off due to time limit set in system > power, upon turning the screens back on, the following happens:
monitor 1 shows a new empty workspace called 3, which did not exist before
monitor 2 shows 2 (active) with an option to show 1, which has the windows that were displayed on monitor 1 previously
I know this is a very specific scenario, but I'm assuming there are lots of people who daily drive more than one monitor using glazewm. I would greatly appreciate if someone could at least suggest a workaround.
Reproduction
Having two monitors, with monitor 1 set as main in windows settings arrange windows such that: workspace 1 on main with tiled windows & workspace 2 on secondary with tiled windows
Win -> Power -> Lock and wait for displays to shut down
Hit a keyboard key to wake up system and login
Stack trace or error logs (if applicable)
No response
Version number
3.5.0.0
The text was updated successfully, but these errors were encountered:
Describe the bug
I have two monitors, and one workspace each. 1 on monitor 1 (defined as main display in windows settings), 2 on monitor 2. If I have applications open on both workspaces, and then the screens shut down either (a) because I do win->power-> lock, or (b) screen is turned off due to time limit set in system > power, upon turning the screens back on, the following happens:
I know this is a very specific scenario, but I'm assuming there are lots of people who daily drive more than one monitor using glazewm. I would greatly appreciate if someone could at least suggest a workaround.
Reproduction
Stack trace or error logs (if applicable)
No response
Version number
3.5.0.0
The text was updated successfully, but these errors were encountered: