Bug #491
repeated desktop notification after laggy connection
| Status: | Closed | Start: | 09/12/2010 | |
| Priority: | Urgent | Due date: | ||
| Assigned to: |  Mirco Bauer |
% Done: | 100% |
|
| Category: | Frontend GNOME | |||
| Target version: | 0.8.9 | |||
| Complexity: | Found in Version: | |||
| Votes: | 1 (View) |
Description
For a few secs I had a bad connection connection, afterwards Smuxi sent again desktop notification of messages from 3h ago.
Associated revisions
Revision f3590decb4a1cedbf10150974ca9a08a5f3520e0
[Frontend-GNOME] Don't show notifications when syncing chats. (closes: #491)
Revision e69b2a7bc77235eb5d57cf28253661e2aaa48eef
[Frontend-GNOME] Fixed indicators, notifications and highlight counters for syncing chats (references: #491)
This fixes a regression introduced with the notification spam fix of #491
The sync state can't be used to determine if a highlight using indicators or
notifications needs to be shown or suppressed as new chats contain messages
which get added via Sync() and not AddMessage().
History
Updated by Raphaël Hertzog 5135 days ago
Not only this but if you close and restart smuxi, you get all notifications from the backlog even for the backlog where smuxi knows that you have already seen it.
I get no red highlight in smuxi but the indicator messaging and the associated notification always come back, it's very annoying for instances in conferences where I quit & restart smuxi very often.
Updated by Mirco Bauer 5135 days ago
- Category set to Frontend GNOME
- Assigned to set to Mirco Bauer
- Priority changed from Normal to Urgent
- Target version set to 0.8.9
Updated by Mirco Bauer 5002 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset f3590decb4a1cedbf10150974ca9a08a5f3520e0.