GNOME Bugzilla – Bug 745132
The timestamp in ongoing messages not updated
Last modified: 2015-03-04 12:58:14 UTC
I'm listening to some music in a playlist. When the first sogn start played, I get message with the current time. 4 minutes after the next song come and the message replaced (I didn't closed/remoced/clean the message before), the whole content are changed exept the timesmap. after an houre I'll see the same time when I started to played the playlist. The timestamp had to be updated.
I think I agree with the report - the timestamp should reflect when the notification was last updated.
Should the notification also move up the list again?
(In reply to Florian Müllner from comment #2) > Should the notification also move up the list again? That's the implication, I suppose. Note that music isn't really a good example here, since it is a fairly unique kind of operation. A better example would be something like mail - a notification like "8 new mails" which gets updated to "12 new mails" should reflect the time of the update, both with the timestamp and the position in the list.
Created attachment 297937 [details] [review] calendar: Update notification timestamps/positions on updates Currently both the timestamp and the position in the notification list are static once a notification has been added; however notifications may be updated later, in which case those properties should be reevaluated.
Review of attachment 297937 [details] [review]: Looks good.
Attachment 297937 [details] pushed as 39a57ee - calendar: Update notification timestamps/positions on updates