https://bugs.kde.org/show_bug.cgi?id=508433
--- Comment #3 from Nate Graham <[email protected]> --- The thing is there are no good options here. As you suspect, a quota would cause innumerable issues. Disabling the animation if an app revokes and then immediately re-creates a new notification would work for the case that the app is literally doing this so fast that we have both notifications already in the queue at the moment we would remove the old notification. But in cases where we don't, this would require predicting the future; we can't know that we should disable the fade-out animation for a notification just because later, in the future, there's going to be a new notification from the same app. Another option is to batch up notifications so that they appear in a little group, rather than all visually appearing and disappearing. That's tracked with Bug 491181. If you think that would help, we can consider this bug report a duplicate of that one, Let me know your thoughts. -- You are receiving this mail because: You are watching all bug changes.
