SUMMARY My notification icon is always visible, and I have difficulties to notice when there is a new notification because the icon used to tell the user that there is a pending notification is almost the same as the one used when there is none. Due to a visual impairment, I need to scale the plasma display to a higher value so I can see better. But that is not enough for this notification icon. So please add an option to display the number of notifications (if any) in place of the small bell that is currently displayed. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.90 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 Kernel Version: 5.10.9-arch1-1
Created attachment 135134 [details] example
Created attachment 135144 [details] This number that appears during downloads and file copies is a good example. I'm not a developer but I think it's already something "ready" for everything else?
The use case of having the notification applet set to always visible seems valid. We removed the number with the expectation that the user would have it set to auto-hide. Having it always visible would indeed seem to benefit from seeing the number of unread notifications rather than the bell.
thank you for considering this
If you find a way to align a number in a circle/badge so it doesn't look horrible, I'm fine with adding the number back.
What I quoted in the previous comment cannot be reused?
I switched back to using the option to display the icon only when relevant for a few minutes and I think I can suggest another solution for that. When there are pending notifications, the icon is displayed, great, but when they accumulate and I need to access the icon more than once it is not possible. Because the icon is hidden the first time it is clicked, even if there are still other pending notifications. So an option to only hide the icon if all notifications are cleared/deleted would be a good work-around for this. Since this is a different way of handling this problem than suggested in this bug report, I may create another different report.
*** Bug 460785 has been marked as a duplicate of this bug. ***