Move Mode Activator hotkey set to set to Alt is forgotten when activating the extension

[normanr]

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:

• Distro (incl. version): Debian testing
• GNOME Shell version: Gnome 46.3.1
• Extension version and from where (e. g. EGO, main branch...): EGO
• XOrg/Wayland: X11

Journalctl logs
It doesn't matter what the hotkey setting is, the same entries are produced (in a different order each time):

Window manager warning: Overwriting existing binding of keysym ffb1 with keysym ffb1 (keycode 57).
Window manager warning: Overwriting existing binding of keysym ffb5 with keysym ffb5 (keycode 54).
Window manager warning: Overwriting existing binding of keysym ffb2 with keysym ffb2 (keycode 58).
Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Window manager warning: Overwriting existing binding of keysym ffb3 with keysym ffb3 (keycode 59).
Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Window manager warning: Overwriting existing binding of keysym ffb4 with keysym ffb4 (keycode 53).
Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Window manager warning: Overwriting existing binding of keysym ffb6 with keysym ffb6 (keycode 55).
Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Window manager warning: Overwriting existing binding of keysym ffb7 with keysym ffb7 (keycode 4f).
Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Window manager warning: Overwriting existing binding of keysym ffb8 with keysym ffb8 (keycode 50).
Window manager warning: Overwriting existing binding of keysym ffb9 with keysym ffb9 (keycode 51).
Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).

[Leleat]

Do you happen to have the Window Action Key set to Alt? You can get it by running

gsettings get org.gnome.desktop.wm.preferences mouse-button-modifier

in a terminal.

[normanr]

I do:

$ gsettings get org.gnome.desktop.wm.preferences mouse-button-modifier
'<Alt>'

This worked in previous versions though (and it works until the extension is restarted).

[Leleat]

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 Alt while also having the action key set to Alt. That means that you immediately enter that move mode instead of the default (Edge Tiling) one, which may be confusing and has been reported as a bug previously.

If you want to immediately enter a move mode, you can simply change the default move mode, no?

[normanr]

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.