antroids
(Bug / Suggest) Maximize and Unmaximize window using the mouse wheel
Good afternoon! There is currently a rather unpleasant bug (or feature, it's hard to say for sure) that manifests itself as follows. If you set the Maximize action for a window by hovering the mouse cursor over the bar on the scroll wheel, then scrolling the mouse wheel further in the same direction will perform the Unmaximize action.
It looks as if the Maximize Window button is being pressed repeatedly. The function to expand the window to full screen is applied repeatedly, followed immediately by Unmaximize.
I think it would be more logical and correct to separate these two functions into separate ones: [] Maximize active window [] Unmaximize active window [*] Maximize / Unmaximize active window active window
This would allow, in particular, the ability to bind one action to scrolling the mouse wheel up and another to scrolling the mouse wheel down. The latter option preserves the current implementation.
I am confident that this introduction will significantly improve the usability of this extension. :-)
The widget just calls the Maximize action of KWin, as same way as windows buttons do. The only option that can be used here is to set Next event distance to 0, so only one scroll event will be triggered.
Perhaps this will be the solution! At least for fast scrolling with the mouse wheel. :)
I wonder how a similar problem was solved in the Active-Window-Control widget? I would like to consider this widget as a complete replacement for Active-Window-Control, since the latter does not work with Wayland.
I wonder how a similar problem was solved in the Active-Window-Control widget? I would like to consider this widget as a complete replacement for Active-Window-Control, since the latter does not work with Wayland.
The Active Window Control has hardcoded actions with a check if the window is maximized.