Bug 131248 - DCOP signal "unreadCountChanged" poorly implemented
Summary: DCOP signal "unreadCountChanged" poorly implemented
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.3
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-23 18:10 UTC by Friedrich W. H. Kossebau
Modified: 2008-01-02 19:39 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Friedrich W. H. Kossebau 2006-07-23 18:10:19 UTC
Version:           1.9.3 (using KDE KDE 3.5.3)
Installed from:    Unspecified

The DCOP signal "unreadCountChanged" is not really supported by KMail :(

For one there is the DCOP-Signal
  void unreadCountChanged( const QString& folderURL, int numUnread );
declared in KMailIface, but never emitted in KMail. Too sad, it would be nice
to get all important data by push instead having to retrieve/pull it (which also brings quite some overhead).

Even worse, "unreadCountChanged()" without arguments gets emitted only 
in  "slotMailChecked(...)". But not e.g. when an unread email gets selected 
and thus turns to "read".

It works for the Kontact summary plugin, because the summary is only shown if 
no other part like the KMail one is in front. And when one switches back to 
the summary all the summary plugins are asked to update. There even seems to 
special support for this with the "timeOfLastMessageCountChange()" DCOP 
method in KMail.
BTW: If KMail is running separately the summary plugin fails of course, too!

See also this thread on kde-pim: http://lists.kde.org/?l=kde-pim&m=115359115719917&w=2
Comment 1 Thomas McGuire 2008-01-02 19:39:36 UTC
I think this is fixed in trunk, which uses D-Bus.
I used the following trick to test it: I set KMail to automatically mark messages as read after 10 seconds. I clicked on an unread message, quickly changed to the summary view and then, after a few seconds, I saw that the summary view was updated.