Workspaces sometimes get scrambled after monitor hotplugging #942
Comments
|
Niri will reset the "original output" of a workspace any time you open or move a window to it. Could this be what is happening? |
|
After a limited amount of testing the workspaces landing on different monitors seems to be caused by that. Although I'm not sure if the ordering of them is a separate problem or a byproduct of that. |
|
Well, it's an intentional design decision. The idea was that after you disconnected a monitor (e.g. left from home to somewhere with a laptop), as you're doing something on your workspaces, you will mix up the windows, so then it would be confusing if upon your return home, a random set of workspaces moved "back" to your external monitor. I guess that thinking doesn't apply as much to named workspaces. |
|
That does make sense for that use case yes. And is definitely a far more prevalent use case than what I have going on. So would you say implementing more scriptability for moving workspaces around through IPC is a better idea for handling this? |
|
Adding more missing by-id addressing to the IPC would be nice regardless |
|
Alright, I'll start tinkering with that soon enough & make a PR when ready enough for review. |
I have a very unconventional setup where my desktop is linked to both my desktop monitors (3 of them) and to a TV and I have a script that allows me to switch between them automatically and that works for the most part. The only issue I have noticed after using it for a while is that sometimes Niri seems to "forget" the original placement of named workspaces and dynamic workspaces alike on the desktop side when switching back. So if for example I were to have workspaces "VR" and "Browser" on my leftmost monitor originally, after switching to the TV and back sometimes they can end up on the wrong monitors and/or in the wrong order. Most of the time they are returned to where they are supposed to be but not always, and fixing them up is a bit of a chore.
Currently there is no way to solve this through scripting, as there are no absolute actions to move workspaces (as in something along the lines of
move-workspace-to-monitor-by-idwhere a specific workspace could be moved to a specific monitor or specific place in the workspace stack). Implementing those actions wouldn't be too hard, but I'm not sure if there's some other fix that could be implemented for this issue that's better suited to the purpose.System Information
The text was updated successfully, but these errors were encountered: