[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 38711] Threads with unread messages should be highlighted
From:       Ingo "Klöcker" <kloecker () kde ! org>
Date:       2006-08-16 13:59:12
Message-ID: 20060816135912.23577.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=38711         




------- Additional Comments From kloecker kde org  2006-08-16 15:59 -------
What's the use case for this wish? Why do you want to know which threads contain \
unread messages if you are not going to read those unread messages? If you are going \
to read them then why don't you make KMail automatically open threads containing \
unread messages? If you see a closed thread containing unread messages then you have \
to open the thread before you can read the unread messages. So I don't see the point \
of not having threads with unread messages opened already by KMail. And if you are \
not interested in threads then mark them as ignored. Then they won't be opened even \
if they contain unread messages.

I'm sure there's a good use case for this wish. Otherwise there wouldn't be 141 \
votes. So please tell me your use case.

(The fact that Outlook et al. have this feature doesn't count. Do Outlook et al. \
[optionally] automatically open threads with unread messages? If not, then this does \
obviously explain why Outlook et al. have to highlight closed threads with unread \
messages.)

About the patch: I don't think adding this code to paintCell is a good idea. \
paintCell will be called (number of visible lines)*(number of columns) times and now \
imagine this in a mailing list folder with lots of closed threads. Then you get O( \
(number of visible lines)*(number of columns)*(number of children in the closed \
threads) ). I fear that this is way to slow. In particular, for each root all \
children have to be traversed (number of columns) times although once should be \
enough. Whether an item should be underlined or not should be determined somewhere \
else. In paintCell only something like  font.setUnderline( mHasUnreadChildren );
should be done where mHasUnreadChildren is a member variable of HeaderItem.
_______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel


[prev in list] [next in list] [prev in thread] [next in thread]