Ignore “Always Above” windows during autotiling#429
Conversation
|
Hey @itsfernn ,
The GNOME documentation really isn't helpful in some instances - like this one. I used to bind the And I just spend 30 minutes, figuring out whats the difference to the binding that you mentioned: Turns out they are aliases to one another [1] [2]. I also wonder why they removed this binding from the GUI. It used to be available there. But anyways: Thanks for the PR. I wonder if the autogrow functionality should really ignore windows that are always on top, though. I would prefer to only respect this property in the autotile function. What do you think? |
|
I don’t use the autogrow feature in my workflow, so I can’t really say. From my quick testing, it seemed reasonable. If a window is marked “Always on Top,” I’d generally expect other windows to That said, I can also see how it might be confusing if autogrow suddenly ignores certain windows without any visual indication of why. Overall, I don’t have a strong preference either way. |
In that case, I would argue that the autogrow feature should be an exception, also because in the gTile UI this feature is described as "Snap window to neighbors". |
|
Sounds good, added the change. |
This pull request updates the autotiling logic to ignore windows that are marked as always above (using
win.is_above()).Technical note:
AFAIK this "Always Above" behavior can only be set manuall1 by a hidden keybinding in the dconf editor (the keybinding is called
toggle_above)Rationale:
Just like minimized windows are currently ignored by autotiling, it makes sense to also skip always above windows. These are typically small, floating windows like a webcam preview or sticky overlay, that users intentionally keep visible and untiled.