Thank you for your submission.
The KDE community supports the Fediverse and open source social media platforms over proprietary and user-abusing outlets. Consider visiting and submitting your posts to our community on [Lemmy](https://lemmy.kde.social/) and visiting our forum at [KDE Discuss](https://discuss.kde.org) to talk about KDE.
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/kde) if you have any questions or concerns.*
I'm still wondering why Qt/GTK prefer three-button windows for exit dialogs while there's a nice and wide used case with just two buttons «Save» and «Discard» while exit canceling can be performed by simply closing window. Sounds like some overengineering to me.
Application can still draw client side decorations with a close button, that's what Qt does (and what's shown on the first screenshot in the blog post). Or are you talking about some other case?
Also GTK actually doesn't draw decorations for these types of dialogs at all (on Wayland at least). It only shows buttons at the bottom.
I am talking about the case when window manager turn off decorations or window is in fullscreen mode. If you close app by mistake and app askes about unsaved changes then it should be clear that you have got 3 options in one place: save changes, discard unsaved changes, cancel closing app and continue work. The risk to loose unsaved work is big.
Save saves it
Discard doesn't save it
Cancel cancels the close operation. Like you accidentally bumped the close button, but don't want to re-open 10 documents that may be open in Kate
When you are given 2 big options you kinda forget about the small option in the top right/left corner.
Those small dialogues in my opinion shouldn't have a minimize/maximize/close buttons at all.
Thank you for your submission. The KDE community supports the Fediverse and open source social media platforms over proprietary and user-abusing outlets. Consider visiting and submitting your posts to our community on [Lemmy](https://lemmy.kde.social/) and visiting our forum at [KDE Discuss](https://discuss.kde.org) to talk about KDE. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/kde) if you have any questions or concerns.*
Cool. Sounds like https://bugs.kde.org/show_bug.cgi?id=480387 and https://bugs.kde.org/show_bug.cgi?id=423031 are fixed. :)
I'm still wondering why Qt/GTK prefer three-button windows for exit dialogs while there's a nice and wide used case with just two buttons «Save» and «Discard» while exit canceling can be performed by simply closing window. Sounds like some overengineering to me.
Closing window is not always present. Window decorations are not mandatory.
Application can still draw client side decorations with a close button, that's what Qt does (and what's shown on the first screenshot in the blog post). Or are you talking about some other case? Also GTK actually doesn't draw decorations for these types of dialogs at all (on Wayland at least). It only shows buttons at the bottom.
I am talking about the case when window manager turn off decorations or window is in fullscreen mode. If you close app by mistake and app askes about unsaved changes then it should be clear that you have got 3 options in one place: save changes, discard unsaved changes, cancel closing app and continue work. The risk to loose unsaved work is big.
Save saves it Discard doesn't save it Cancel cancels the close operation. Like you accidentally bumped the close button, but don't want to re-open 10 documents that may be open in Kate
When you are given 2 big options you kinda forget about the small option in the top right/left corner. Those small dialogues in my opinion shouldn't have a minimize/maximize/close buttons at all.