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

List:       kmail-devel
Subject:    Re: Proposal to change the way threading settings work
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2003-08-09 17:08:24
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Friday 08 August 2003 19:01, Aaron J. Seigo wrote:
> On Thursday 07 August 2003 03:53, Till Adam wrote:
> > - bool threaded = mThreaded && mFolderThreaded
>
> since this means i can't have only some folders turned on with the
> rest turned off, how about:
>
> bool threaded = (mThreaded && mFolderThreaded) || mFolderThreaded;

This is equivalent to
  bool threaded = mFolderThreaded;

So you probably meant
  bool threaded = (mThreaded && !mFolderThreaded) || mFolderThreaded;
which is equivalent to
  bool threaded = mThreaded || mFolderThreaded;

> in the GUI, if mFolderThreaded has not be specifically set by the
> user, it can default to following mThreaded (sort of an implied third
> state as per Andreas Gungl's concept)

That's almost a working solution. But it doesn't allow the user to turn 
on threading (or HTML) for almost all folders except a few one. I like 
Andreas tri-state proposal. If the options are moved from the menu to 
the folder configuration dialog then this tri-state can easily be 
represented by either a combo box or a radio button group. What would 
be preferable, Aaron?

> as for whether these options belong in the menu or not, i too think
> they belong in the folder configuration dialog. it helps that there
> is now a nice quick way to turn HTML display on/off per email...

Agreed.

> the Folder menu and the Folder context menus need to be synced up a
> bit too, it seems...

Volunteers?

Regards,
Ingo

[Attachment #5 (application/pgp-signature)]

_______________________________________________
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]