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
When unplugging monitors (for example, unplugging a dock from a laptop), this plugin doesn't move windows to appropriate workspaces on an existing monitor. This doesn't match dwm behavior, and makes for a poor experience with laptop setups.
While I'm working on it (I need to beef up my debug setup with robust networking and a separate machine to run a debugger on), my question is, should the plugin attempt to move windows to appropriate workspaces on a monitor with the highest id, or should it move them to the zeroth monitor?
The text was updated successfully, but these errors were encountered:
Would it be possible to have that as a configuration option? There are use cases I can think of for both highest id or zeroth id, so it might be nice to have that be configurable.
I think it's time for me to throw in the towel. The developer experience with Hyprland barely working with the feature I'm writing around, as well as C++ development in general, especially when you can't really have a decent way to trigger your code in the scenario you're testing around is quite annoying. I feel like I've been dragging myself to work on this for far too long as is. Feel free to take code from my branch and do whatever to it if anyone finds that code of any use. I have a guess as to why it crashes, but I don't feel like spending an hour to even trigger that with a GDB instance doing network debugging, when I'm already considering moving to a compositor that's more funcional and fits my use case better.
When unplugging monitors (for example, unplugging a dock from a laptop), this plugin doesn't move windows to appropriate workspaces on an existing monitor. This doesn't match dwm behavior, and makes for a poor experience with laptop setups.
I'm working on a (hacky) implementation of such a feature myself on my fork: https://github.com/UwUnyaa/split-monitor-workspaces/tree/handle-unplugging-monitors
This issue exists here to be in place for a possible pull request if needed, as well as any feedback regarding the behavior.
While I'm working on it (I need to beef up my debug setup with robust networking and a separate machine to run a debugger on), my question is, should the plugin attempt to move windows to appropriate workspaces on a monitor with the highest id, or should it move them to the zeroth monitor?
The text was updated successfully, but these errors were encountered: