Ticket #58 (enhancement)
Opened 2 years ago
Last modified 1 year ago
Make it possible to tell the observers about 'unread changes'
Status: closed (fixed)
| Reported by: | anonymous | Assigned to: | pvanhoof |
|---|---|---|---|
| Priority: | minor | Milestone: | A second release |
| Component: | libtinymail-camel | Version: | 2.0 |
| Keywords: | Cc: | dirk-jan.binnema@nokia.com | |
Using the IMAP4 unsolicited FETCH responses (or, the ones during IDLE at least), you get instant flag changes too (by instant, I mean Push E-mail or pushed-by-the-server's changes). This includes the \UnSeen? and \Seen flags. These changes are caught and handled internally by Tinymail already (although due to crappy IMAP server implementations, and perhaps some improvements that Tinymail could use too, it's not yet very accurate always)
They are, however, not yet emitted as a signal in Camel (the folder_changed one, or a new one). Therefore might the model itself get updated (due to rewriting=re-getting-the-value by the gtkcellrenderer), but not the other observers (like the folder-list-model, for example).
This might give an 'inconsistent feeling' to certain users. Therefore it's a bug and must be fixed.
Due to the priority of this issue, I'm yet marking it as an enhancement task too.
Note that another related problem is ticket #57
Attachments
Change History
12/02/07 16:13:46: Modified by pvanhoof
- status changed from new to closed.
- resolution set to fixed.

Fixed