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 using the "Toogle shaded state" keyboard shortcut on a window that is not shaded, it will shade, but then immediately loose the focus.
Unshading is then not possible anymore.
Even if one tries to manually focus the window (by clicking the title bar) it doesn't gain focus (one sees that it briefly gains it by the changed title bar colour, but then it immediately goes be to unfocused).
Clicking on the window’s entry in the panel’s window list, gives it the focus, but also unshades it (which I think may not be the best behaviour either?).
The same problem exists if one Alt-Tab (window-cycles) to a shaded window... it immediately unshades, which IMO also breaks quite some usefulness of the feature.
Steps to reproduce
Well as above.
Expected behavior
The window shouldn't loose the focus, and using the shortcut again, should unshade it.
And most likely, selecting a shaded window via the window list or via Alt-Tab shall not cause it to unshade.
Additional information
No response
The text was updated successfully, but these errors were encountered:
I just tested this in Mint 21.3. Setting and using a keyboard shortcut works the way you describe. By setting right click to shade and unshade a window and it works fine as far as I can tell. I do use "focus follows mouse" as default if that makes a difference.
And most likely, selecting a shaded window via the window list or via Alt-Tab shall not cause it to unshade.
This is will disagree with. If I'm Alt+Tabbing to a window or clicking the panel entry that means I want to do something in that window. In that case unshading actually saves a step and seems like the proper behavior.
This is will disagree with. If I'm Alt+Tabbing to a window or clicking the panel entry that means I want to do something in that window. In that case unshading actually saves a step and seems like the proper behavior.
Hm, than I'd prefer if it was configurable. I can understand that one wants a minimised window to be un-minimised if one Alt-Tabs to it (because otherwise one cannot do anything with it).
But with the shaded window, one can actually to stuff, after having Alt+Tab'ed to it. E.g. move it, close it, send it to another workspace, etc. pp..
Distribution
Debian sid
Package version
5.8.2
Graphics hardware in use
Intel
Frequency
Always
Bug description
When using the "Toogle shaded state" keyboard shortcut on a window that is not shaded, it will shade, but then immediately loose the focus.
Unshading is then not possible anymore.
Even if one tries to manually focus the window (by clicking the title bar) it doesn't gain focus (one sees that it briefly gains it by the changed title bar colour, but then it immediately goes be to unfocused).
Clicking on the window’s entry in the panel’s window list, gives it the focus, but also unshades it (which I think may not be the best behaviour either?).
The same problem exists if one Alt-Tab (window-cycles) to a shaded window... it immediately unshades, which IMO also breaks quite some usefulness of the feature.
Steps to reproduce
Well as above.
Expected behavior
The window shouldn't loose the focus, and using the shortcut again, should unshade it.
And most likely, selecting a shaded window via the window list or via Alt-Tab shall not cause it to unshade.
Additional information
No response
The text was updated successfully, but these errors were encountered: