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

List:       kmail-devel
Subject:    Re: Search Dialog
From:       Till Adam <adam () kde ! org>
Date:       2004-01-09 3:05:18
Message-ID: 200401090405.24521.adam () kde ! org
[Download RAW message or body]

On Thursday 08 January 2004 20:40, Ingo Klöcker wrote:
> On Wednesday 07 January 2004 23:45, Till Adam wrote:
> > On Thursday 08 January 2004 01:22, Ingo Klöcker wrote:
> > [snip]
> >
> > > Another improvement would be to only show the numerical comparison
> > > operators (is greater than, etc.) for numerical fields, e.g. for
> > > <size in bytes> and <age in days>. On the same time "contains",
> > > etc. shouldn't be shown for numerical comparison. Also for <status>
> > > only "is" and "is not" should be shown. With this approach the
> > > comparison operator drop down box would already be less cluttered
> > > even in expert mode. The only thing the expert mode would change is
> > > showing/hiding the two reg.exp. options.
> >
> > For status "is" and "is not" is more often wrong than not. If a
> > message is "read" and "important" then <status> "is" "read" will be
> > false. Either we change the semantics of "is" and "is not" to mean
> > "contains" and "doesn't contain" for status, or it has to be
> > "contains" and not "is" that is available for status.
>
> Well, yes, we have to change the semantics of "is" and "is not" for
> <status>. A message which is "read" and "important" is of course
> "read" (in common sense).

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?

Till

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