https://bugs.kde.org/show_bug.cgi?id=498510
fanzhuyi...@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fanzhuyi...@gmail.com
--- Comment #5 from fanzhuyi...@gmail.com ---
(In reply to Fernando M. Muniz from comment #2)
> (In reply to Nate Graham from comment #1)
> > Can you envision how would this handle the case where an unresponsive app
> > becomes responsive again and has unsaved data you don't want lost if it gets
> > killed automatically?
>
> If the user has pressed Alt+F4 he expects the app to be closed.
IMO if users press Alt+F4, they expect the app to gracefully close, *without
losing data*. Implementing this would make closing apps slightly more dangerous
-- if I click close or press alt+f4, and then temporarily leave or is otherwise
unable to interact with the kill dialog, I might lose data if the app is
unresponsive for more than 30 seconds. IMO having default options (in this
case, inaction) that potentially causes lost data is not good.
Alternately, how feasible is it to boost the responsiveness of the kill dialog
under heavy system load? I recall the force quit dialog on macos being pretty
responsive even under heavy system load.
--
You are receiving this mail because:
You are watching all bug changes.
