In Plasma 5 the behaviour of notifications was changed so that not all notifications are kept in the systray, but only those who are specified to be kept. It would be nice if user scould add this flag themselves for whatever notifications they would prefer to be kept, so they are not going to miss them when away from the monitor. A little checkbox in the knotify settings for each notification would be perfect. Reproducible: Always Steps to Reproduce: 1. Have a notification you care about 2. Have that pop up when you are not in front of the monitor Actual Results: You miss it Expected Results: You were able to configure this specific notification to be kept, and are greeted with a cute (1) in the systray, holding your notification for you
Can you give some us some examples of the notifications you'd configure?
(In reply to David Edmundson from comment #1) > Can you give some us some examples of the notifications you'd configure? The first ones coming to mind are those that annoyed me personally, being bluedevil, powerdevil (aside from the "your battery is critical, that one already is persistent, but it's the one that makes the least sense, given you have 30 seconds before your laptop goes to S4, thus you hardly ever come back to that) longer file copy / move jobs, downloads, kmail notifications ... However, I am sure that different people have different use cases and preferences, thus the idea of being able to pass a flag along the notification to make it persistent, and this being configurable in the usual notification configuration dialogue (which, in the end, is knotify)
Fwiw, I do maintain that notifications are meant to be simple notifications that "something has happened somewhere" and that somewhere should be marked accordingly - blink in taskbar, blink/pulse in systray etc. The notification popups are just a complimentary service. That's why things like StatusNotifierItem were invented (an Item that shows you Status or Notifies you). When you come back to your computer, you shouldn't get the current unread mail count from a notification, you shouldn't get the current playing song from notification, you shouldn't get a "you have new message" from notification, you shouldn't get "your battery is low" from a notification. You should get those things from dedicated SNIs which work better and are meant for such usage. Notification popups are not and wanting to use them for this is simply misusing the feature. As for your particular examples: * bluedevil - not sure what you mean * powerdevil - the battery icon changes color and blinks when your battery gets really low, the "you have 30 seconds" thing I think is less than ideal and I believe was disabled by default (?) * file operations - those stay in the history * kmail - has a dedicated SNI I understand, which also displays the number of unread emails
(In reply to Martin Klapetek from comment #3) First of all: putting resolved, wontfix without giving the reporter a chance to give feedback is a bit rude. > Fwiw, I do maintain that notifications are meant to be simple notifications > that "something has happened somewhere" and that somewhere should be marked > accordingly - blink in taskbar, blink/pulse in systray etc. The notification > popups are just a complimentary service. That's why things like > StatusNotifierItem were invented (an Item that shows you Status or Notifies > you). That is unfortunately a best case scenario far from what the real world looks like, for quite a lot of usecases notifications are the only sane way to show a decent amount of information and give the user a one glance overview. Please note that other systems, among them OS X, iOS and Android, provide such an overview / message centre. > When you come back to your computer, you shouldn't get the current unread > mail count from a notification, you shouldn't get the current playing song > from notification, you shouldn't get a "you have new message" from > notification, you shouldn't get "your battery is low" from a notification. > You should get those things from dedicated SNIs which work better and are > meant for such usage. Status Notifications, due to restraints such as their size, have a very limited amount of information they can display. If you expect the user to hover or click on each to get the same information overview a notification backlog provides, then I'd say that's horrible from an UX point of view. > Notification popups are not and wanting to use them > for this is simply misusing the feature. > > As for your particular examples: > * bluedevil - not sure what you mean Asking instead of closing would have been nice. You can miss incoming file transfer or pairing notifications that are still valid. > * powerdevil - the battery icon changes color and blinks when your battery > gets really low, the "you have 30 seconds" thing I think is less than ideal > and I believe was disabled by default (?) Enabled by default I'd say, unless distribution choice. > * file operations - those stay in the history Only while running. > * kmail - has a dedicated SNI I understand, which also displays the number > of unread emails Yes, which is not comparable due to two reasons: First of all, the notification gives you the sender and subject, giving you a very efficient way to decide whether you bother or whether it can wait. In addition to that, kmail not only informs you about unread mails, but also sent mails (which cam be delayed by choice, e.g. when in a bad network) or accounts being offline. Summary: you not only miss important information without notifications and only SNI, but also work less efficient because there is no quick overview via backlog as other systems provide. Kind regards, Christian
> First of all: putting resolved, wontfix without giving the reporter a chance to give feedback is a bit rude. It's been filed several times and explained several times. I know what your feedback will be and all I can tell you is that the notification system as it is now is simply not suited for what you want it to be. It would require serious redesign into something like that OSX notification centre you've mentioned. The current system is not and cannot be it.
(In reply to Martin Klapetek from comment #5) > > First of all: putting resolved, wontfix without giving the reporter a chance to give feedback is a bit rude. > > It's been filed several times That might be a sign that it indeed could be improved / changed, then. > and explained several times. I know what your > feedback will be and all I can tell you is that the notification system as > it is now is simply not suited for what you want it to be. It would be nice to have concrete examples on why that is the case, because when I've been asked for concrete examples I gladly delivered and explained, which seems to have been a bit ignored ... > It would require > serious redesign into something like that OSX notification centre you've > mentioned. The current system is not and cannot be it. A redesign is also perfectly fine with me, and I'll gladly help during the design / mockup phase if wanted. In the meantime I guess I'll just patch it for me to work as expected *shrug* kind regards, Christian
*** Bug 358983 has been marked as a duplicate of this bug. ***