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

List:       kmail-devel
Subject:    Re: Problems with automagic selection of closed threads
From:       Till Adam <till () adam-lilienthal ! de>
Date:       2003-04-26 15:20:31
[Download RAW message or body]

On Saturday 26 April 2003 16:37, Ingo Klöcker wrote:
> On Saturday 26 April 2003 10:19, Till Adam wrote:
> > On Saturday 26 April 2003 00:30, Ingo Klöcker wrote:
> > > On Friday 25 April 2003 22:33, Till Adam wrote:
> > > > On Friday 25 April 2003 22:27, Ingo Klöcker wrote:

> > > BTW, all flavors of Reply and Print only work on the parent of
> > > closed threads. So we already have inconsistent behavior.
> >
> > Hm. Damn, you have a point here. ;).
>
> So what to do? Usually actions which only work on a single message are
> disabled whenever multiple messages are selected. So to be consistent
> we would have to make the same if the parent of a closed thread is
> selected. OTOH this would mean that replying to the parent of a closed
> thread is impossible without first opening the thread. So we could
> probably leave it as it is (although it's inconsistent).

Yes. For print and reply the inconvenience outweighs the inconsistency, I 
think. 

> BTW, I just noticed that after expanding a thread with View->Expand
> Thread (or with the corresponding keyboard shortcut) all items remain
> selected. This is inconsistent with expanding a thread with the mouse.

I'll change that to do an unselectAllExcept as well. (Hopefully without 
flicker).

Till

_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail

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