Ticket #49 (defect)
Opened 2 years ago
Last modified 2 years ago
Folder counts only updated after opening the folder
Status: closed (fixed)
| Reported by: | pvanhoof | Assigned to: | pvanhoof |
|---|---|---|---|
| Priority: | major | Milestone: | A first release |
| Component: | libtinymailui-gtk | Version: | 1.0 |
| Keywords: | Cc: | dirk-jan.binnema@nokia.com | |
You can clearly see this problem in the demo user interface: only after you once opened a folder, the unread and total counts are correctly displayed in the mailbox treeview.
This seems to be an initialization of camelfolder or a treemodel problem.
Attachments
Change History
04/22/07 14:29:05: Modified by pvanhoof
04/22/07 14:31:15: Modified by pvanhoof
No, I just had the same problem with a Cyrus. Though only when I was online (when offline, the offline cached's count was used).
Note for people who want to fix this: the size updates are transferred to the tree model using the TnyFolderObserver infrastructure, and initially by simply letting the tree model ask the folder for this (although this initial call might not or might happen, this might very well be the problem).
-- several explanations are possible --
05/08/07 00:43:07: Modified by pvanhoof
- status changed from new to closed.
- resolution set to fixed.
This should be fixed, please test this (and reopen if not). I have noticed discrepancies with the unread counts. The total count seemed to be correct always. Not sure of those where related to testing things intensively, including removing offline cache (and the offline summary cache getting mixed up a little bit) or whether it's simply a bug.
If it's still a bug, it's probably related to storing the counts in the store's summary (that's a parent summary for folder summaries), and not in the counting itself.
Note that the counts should be correct at startup, not just after opening a folder.
It looks like this only happens with Courier IMAP servers and only when you are online. But this claim needs some investigation too (I haven't in depth checked this, just noticed it during a test session with the demo user interface).