3 ms·
> EDIT: Oh, and I almost forgot. The fact that the little 'x' close button of maximized windows cannot be clicked if a smaller window is active and in the foreg
by johnchristopher 10y ago
> EDIT: Oh, and I almost forgot. The fact that the little 'x' close button of maximized windows cannot be clicked if a smaller window is active and in the foreground. That drives me nuts.
I don't understand: That's default GTK/win behaviour when the smaller window is part of the background window (like LO prompting for closing/saving/cancelling the document you are editing when you click the close button of LO). It's a pop up.
- Kenji 10y agoYes, it makes sense when you close your word processor and you have unsaved work, that the popup asking you to save your work has priority and prevents the close button from being clicked. However, it does not make sense that if I have a small console window in the foreground and my word processor in the back, that I cannot close my word processor with one click - but I can't. That's default behaviour in Unity.
- type0 10y ago> However, it does not make sense that if I have a small console window in the foreground and my word processor in the back, that I cannot close my word processor with one click - but I can't. That's default behaviour in Unity. These small but idiosyncratic behaviors in Unity that probably drive so many people away. It is long time sine I used Unity last, but there was enough of these quirks that made it unpleasant to use.
- johnchristopher 10y agoThanks for your detailed answer. I didn't know things had gotten to that point :/ (I am an awesome-wm user on top of debian with xfce install who kinda like gnome3).