https://bugs.kde.org/show_bug.cgi?id=490934

Nate Graham <n...@kde.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED
   Version Fixed In|                            |6.2.0
      Latest Commit|                            |https://invent.kde.org/plas
                   |                            |ma/plasma-systemmonitor/-/c
                   |                            |ommit/8735b6603fc244b4efcc8
                   |                            |b1f3dc2d2fb162f672b

--- Comment #5 from Nate Graham <n...@kde.org> ---
Git commit 8735b6603fc244b4efcc8b1f3dc2d2fb162f672b by Nate Graham.
Committed on 08/09/2024 at 09:49.
Pushed by ngraham into branch 'master'.

Display signal type when SIGKILL'ing a process or application

System Monitor allows you to send two types of signals to kill processes
or apps: SIGTERM or SIGKILL. However the UI in the kill dialog doesn't
tell you which one is being used, making it difficult to verify that you
used the one you wanted.

This commit solves that problem by changing the terminology when using
SIGKILL: use the word force/forcibly to distinguish it from normal
quitting, and mention the signal name.

Since those strings were being touched, it also slightly re-words them
for better HIG conformance.
FIXED-IN: 6.2.0

M  +13   -4    src/faces/applicationstable/contents/ui/FullRepresentation.qml
M  +13   -4    src/faces/processtable/contents/ui/FullRepresentation.qml

https://invent.kde.org/plasma/plasma-systemmonitor/-/commit/8735b6603fc244b4efcc8b1f3dc2d2fb162f672b

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to