https://bugs.kde.org/show_bug.cgi?id=490934
--- Comment #2 from bugs.7n...@aleeas.com --- > While investigating fixing this, I found that in fact Shift+Delete already > does exactly what you want it to do: sends a SIGKILL, while Delete without > the shift key sends a SIGTERM. Just verified this with current git master. > > "End process" is generic enough in text that changing it to something > specific and technical only when holding Shift doesn't make sense IMO. Great to know the option is available after all at least. It didn't occur to me observe behavior that closely, but I couldn't disagree more with the conclusion here. Is it really good UX to have two slightly different actions trigger the same (visually indistinguishable) dialog, which subsequently triggers a different action? This might be acceptable if the outcome would be visibly different (aiding in discoverability of the feature), but a SIGTERM can't be distinguished from a second SIGKILL working "after all". It's also natural to assume that since "SHIFT+DEL" sends a SIGTERM, clicking "End Process" while holding SHIFT would do the same. This is not the case either, making the UI inconsistent and the feature even less discoverable. Dolphin, for example, behaves like this: The menu action "Move to trash" is bound to the "DEL" key, but when holding SHIFT that menu action changes to "Delete" (bound to "SHIFT+DEL"). This makes the feature self-consistent and discoverable. Why wouldn't the same be done for the system monitor? -- You are receiving this mail because: You are watching all bug changes.
