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

no window remains on its workspace after connecting external monitor #26

Open
nkrot opened this issue Feb 26, 2023 · 3 comments
Open

no window remains on its workspace after connecting external monitor #26

nkrot opened this issue Feb 26, 2023 · 3 comments

Comments

@nkrot
Copy link

nkrot commented Feb 26, 2023

Hi,

I have an external monitor that is set up as "primary" and workspace indicator is configured to be on this primary display only.

if I disconnect the external monitor and then reconnect, not a single windows is on its original workspace. Instead, all windows are on the built-in secondary display (where there is no workspace indicator) and all workspaces in Improved Workspace Indicator are empty. Needless to say, this behaviour is a mess and defeats the purpose of workspace indicator.

It would be nice to see it fixed. Expected behaviour is that all windows stay on the same workspace upon reconnecting the external monitor.

I am using Ubuntu 20.04, Gnome 3.36.8

thanks in advance

@MichaelAquilina
Copy link
Owner

I suspect the issue is that we are simply not connecting to a "monitor connected/disconnected" signal in Gnome. I dont use more than one monitor so I never an into the issue myself.

Would you like to give the fix a go? The code is actually quite easy to follow and shouldnt be hard to debug if you want to make a contribution :)

Otherwise, I can find some time in the future to try work on this, but I cant garauntee a timeline of course

@nkrot
Copy link
Author

nkrot commented Mar 20, 2023

are there any plans to fix this crap in near future? i feel pissed off having to rearrange the windows twice per day.

@MichaelAquilina
Copy link
Owner

MichaelAquilina commented Mar 20, 2023

@nkrot this is an open source project and not my full time job. As I mentioned in my previous comment, I cannot guarantee a timeline due to other real life commitments I have. Alternatively, you can stop using the extension.

This issue in particular does not affect me so it is quite low on my radar. You are welcome to give the fix a go yourself.

I do not appreciate the tone you have taken and I will close this issue if it persists.

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

2 participants