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

List:       kmail-devel
Subject:    Re: Search Dialog
From:       Thomas Zander <zander () kde ! org>
Date:       2004-01-09 11:45:41
Message-ID: 200401091245.43399.zander () kde ! org
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Till wrote late late last night:
> Internally it's not "is" and "is not" but "equals" and "does not equal", so 
> 'status equals read' clearly is wrong while 'status contains read' is 
clearly 
> right. :) Oh well. Do you want me to make status searches treat 'contains' 
> and 'equals' identically to not confuse users? You can't currently specify a 
> composite status with the gui anyhow, to search against. Before 3.2? As in, 
> now?

I only got results on the 'contains' and 'not contains' entries; IMO the best 
way to fix this is by removing all other entries in the GUI as soon as the 
<status> entry is chosen.
This would also need a backup member var to remember the selected entry 
_before_ <status> was selected. So if user tries 4 entries including <status> 
it does not mean his 2nd combo changed.

This seems like a big patch for the 3.2 release (but I'll leave you to decide) 
what I'd really like to see is that your proposal above will make it in 3.2.

KMail is looking good for this release, thanx people!
- -- 
Thomas Zander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE//pRlCojCW6H2z/QRAnEkAKDDCyBVilrSr6To84s5hdxiJ9cCTACgkdxn
VJj7w7ic2k57T2EXEFr90SU=
=tZWf
-----END PGP SIGNATURE-----
_______________________________________________
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]