https://bugs.kde.org/show_bug.cgi?id=523475
--- Comment #4 from Sergey Katunin <[email protected]> --- > So I'm not sure there's a path forward here for something better than the > status quo. Can you think of anything I've missed? There may also be a case when the program can be "stuck" in another way - it intercepts the normal closing event and ignores it. Like override `closeEvent` and `event->ignore()` in Qt. So, it cannot be closed through the usual "Close", only through the system monitor or kill via terminal. This may be either an intentional behavior of the program or a bug. > That way, approximately 0% of people will be in a position to use it if they > need it. So I can't completely agree with that. This feature would be convenient for users who want to be able to nail a program that is stuck or just annoying by single click from UI, and even if it were optional, I would personally use it, as would those people who created the discussions above. I know this is a bad argument, but there is such a feature in W11 (and it is optional). > we'd also be giving users a gun to shoot themselves in the foot with (e.g. > causing data loss if there are unsaved changes) But what if we show a dialog with a warning that force closure may lead to data loss? And I think, we can also make it so that this item is displayed with 'Force close' after the first click on 'Close'. Since this is usually just such a scenario, when user clicks on "Close", but the program does not close because it stuck or refuses to close for some other reason. And when he opens the context menu in order to try to click on "Close" again, he will see "Force close" next to it (or something like that). -- You are receiving this mail because: You are watching all bug changes.
