Jay I’m not sure it is a good idea to try to auto-convert typing in non-advanced to buttons. For instance, I like to have a couple buttons toggled (not completed, is star) and then have advanced text like
pri:high or before:tomorrow. When I start typing and enter
pri:high it turns on the high priority button and deletes the text before I have the chance to type
or. This happens even if I start as if I am enclosing in parentheses
(pri:high. Also, if I have an existing pane, or create a pane with an advanced filter with
pri:high or before:tomorrow it toggles the button and leaves
or before:tomorrow and if I enclose the filter text in parentheses like this:
(pri:high or before:tomorrow), the filter text ends up as
(or before:tomorrow). Of course, I can just go to or stay in advanced mode and do it, but it is really nice to be able to use the buttons for all the AND terms and just use the filter text for OR terms. I also think in non-advanced mode, the filter text should always be treated as if it is enclosed in parentheses and treated as grouped terms, even if not explicitly entered as such, so entering
this or that would always group the OR terms together.
I guess the other alternative is to not consider or allow any OR operator in the filter text in non-advanced mode but rather only treat all terms as AND terms (and treat OR as literal), but I personally like having the ability to use both buttons and OR logic in the filter text.