This can be useful for notifications that confirm direct user interaction, such as successful Bluetooth pairing, Screenshot creation, or plasmoid removal.
It only overrules filtering based on urgency, disabling notifications for that application altogether will still hide them.
Such a notification also won't increase the unread counter as it can be assumed when they do something, e.g. click on "Pair", they will notice that the pairing progress dialog went away and a confirmation notification is shown.
Details
Details
- Reviewers
davidedmundson - Group Reviewers
Plasma - Commits
- R120:8dc1db04b9be: [Notifications] Add hint for a notification being response to explicit user…
Enabled dnd mode, notify-send foo bar -h string:x-kde-user-action:true and it showed up regardless
Diff Detail
Diff Detail
- Repository
- R120 Plasma Workspace
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Comment Actions
x-kde-show-when-in-do-not-disturb-mode maybe? Might be nice to reference the feature itself in the keyword since "inhibited" is rather vague.
Comment Actions
How is it, though? It is an internal hint on some DBus method no user will ever see. Internally it's all things like notificationsInhibitedUntil, even the (public) DBus API says "Inhibited"
Comment Actions
It was suggested to make it more semantic, i.e. be about "this is feedback for user-initiated task" which will then imply showing in dnd mode. Suggestions on how to phrase that as a key name?