I agree. That's worth reporting back as a bug report. I guess it's because it treats multiple contexts as a single string in the contexts field, so might not be easy for the dev team to fix. Now I know that, though, I'll always use Contexts Text contains..., rather that starts with... Perhaps the constraint should be made clear in the help file.
On Thursday, 11 February 2021 at 18:41:50 UTC [email protected] wrote: > Hi folks, it's been a while since I posted. I hope we're all surviving > the pandemic is good spirits. I was just doing a filter via the "Setup > Advanced filtering" dialog. One of the options to filter by is > "ContextsText." If I choose "starts with (match case)," then it seems to > only match if the first of multiple contexts starts with the letter. > Should it evaluate every separate context instread? > > For example, if my filter is: > *[ContextsText stats with x (match case)]* > and if my tasks have the following contexts: > > *Task1: home; xylophone; practice* > *Task2: xylophone; practice* > *Task3: home; practice* > > Then MLO seems to only match Task2, but I think it should instead match > Task1 and Task2. > > Hope that makes sense. Using MLO5 Pro on Win10. > Take care! -Steve > > -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/4b29aa4b-0986-4309-920b-e89002f8808fn%40googlegroups.com.
