Version: unspecified (using KDE 4.5.95)
If one jumps to the next song the OSD is displayed instantly whereas the system notification only appears a few seconds later. My guess is that amarok loads the content of the "lyrics", "current song" etc. before it shows the system notification.
Removing all widgets improves the situation but the notification is still not shown at the same time as the OSD but soem seconds later.
What Amarok version is this about? Please don't forget to set it when you report a bug.
Confirmed on current git
Amarok just creates new event for KNotify and ask daemon to show It. There is no way to force KNotify to draw new event before Its own timer event. It's not a bug.
So you claim that there is a >1 second delay between amarok creating the notification and the daemon showing it? If so, please re-assign to the notification component since that one seems to cause a delay then.
Something is causing a delay and that's a bug.
My bad. There is really the 3s timer.
Sergey, any news on this? I assume this is still valid with current git?
Currently, with Amarok v2.6.0-422-gfc07990 and KDE 4.9.3, the system notification doesn't show up at all.
Git commit f7170ee1872432d05bcb58e6c1ac36b69849e765 by Matěj Laitl.
Committed on 29/12/2012 at 19:59.
Pushed by laitl into branch 'master'.
KNotificationBackend: rework to make notifications instant and more reliable
* Make track announcements via KDE Notifications instant.
M +1 -0 ChangeLog
M +54 -68 src/KNotificationBackend.cpp
M +11 -12 src/KNotificationBackend.h
When I asked about the delay a year ago or more, it was said this is intended to prevent notificiation spamming when you quickly skip through tracks …
I'm wondering about this, too. When I wrote the code, I used this delay to prevent this.
Can't check atm, but what happens when you quickly skip through songs?
What is the status of this bug? Comment #12 seems to indicate that there is still something to investigate.
(In reply to comment #13)
> What is the status of this bug? Comment #12 seems to indicate that there is
> still something to investigate.
No it doesn't, I checked with Kevin.