-
Notifications
You must be signed in to change notification settings - Fork 63
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
Move Mode Activator hotkey set to set to Alt is forgotten when activating the extension #374
Comments
Do you happen to have the gsettings get org.gnome.desktop.wm.preferences mouse-button-modifier in a terminal. |
I do:
This worked in previous versions though (and it works until the extension is restarted). |
Ah, that's actually intentional then and not a bug. The fact that it "worked" previously was a bug because it may be confusing if you set a certain mode to If you want to immediately enter a move mode, you can simply change the default move mode, no? |
I don't want to immediately enter a move mode, most of the time I move windows using the title bar, so I generally don't hold Alt to initiate moving windows. When I do, it's okay that tiling mode is enabled, because I can immediately release Alt to get regular edge tiling (if I want), or continue to hold Alt if I want to use favorite layout. Also I don't think there's a conflict with the window-move mouse-button-modifier. I can have both set to the same same key (temporarily) and it works correctly. |
Describe the bug
I find that my "Alt" Move Mode Activator hotkey is being reset every time my machine locks. "Ctrl", "RMB", "Super" are all preserved, just "Alt" is reset to "Disabled". I discovered this actually happens every time the extension is activated (when happens when unlocking), and can be reproduced by just disabling and enabling the extension.
Steps To Reproduce
Set "'Favourite Layout' Move Mode Activator" to Alt.
Either: Disable extension, enable extension (or: Lock screen with hotkey, or wait for it to timeout and auto-lock).
System Info:
main
branch...): EGOJournalctl logs
It doesn't matter what the hotkey setting is, the same entries are produced (in a different order each time):
The text was updated successfully, but these errors were encountered: