Filter FolderName Does Not Contain "someday" not working

[DCC]

Greetings,

I am trying create a filter so that a folder named "z -Someday and Maybe" that I would like to filter out and remove from a view.  I set advanced filter to

FolderName Does Not Contain "maybe" AND

Context is not: and "Someday" and "Maybe" are selected

However, the "z -Someday and Maybe" folder remains in the view.  

Any suggestions on how to filter that folder and it's contents out of the view would be appreciated.

Thank You,

Dwight... 

[Dwight Arthur]

Hi Dwight.

I don't know how to interpret

    Context is not: and "Someday" and "Maybe" are selected   

The closest I can find to "Context is not" would be "Contexts does not contain" - is that what you are using? 

Your folder named "z -Someday and Maybe" sounds to me like it should probably be hidden from all of your to-do list (i.e. non-hierarchical) views, is that correct? If so, I would mark the folder "hide the branch in To-Do" (in General Properties) and code a rule:
    (Contexts does not contain Someday) And (Contexts does not contain Maybe)

You could also try to collapse this to a single rule with multiple contexts selected - I try to avoid that as it can get confusing - is there an implied "or" between the context names or is it an implied "and"? The correct answer changes if there's a "not" in the rule. Confusing.

Anyhow, if you do not want to hide the folder I would code    
    (Contexts does not contain Someday) And (Contexts does not contain Maybe) And (FolderName does not contain Maybe)

I'm pretty sure this will exclude anything that's contained in your "z" folder. It may not exclude the "z" folder itself because the "z" folder is probably NOT contained in a folder whose name includes "Maybe". If that is what happens, in my view the easiest cure would be to put the context "Maybe" onto the "z" folder. The only drawback would be that any task you drag into the "z" folder from then on would get the Maybe context automatically assigned, even if it was supposed to be a Someday task.

Regards,
-other Dwight

--
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 mylifeorganiz...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mylifeorganized/d90b8819-06d1-4305-a9c3-7061db6418a9n%40googlegroups.com.

[Dwight Arthur]

Dear other Dwight, I'm putting this back on the list because the next discussion could be helpful to others.

Here's the issue about FolderName. If I put a penny in a little blue bottle and put the little blue bottle in a big green bottle and asked for a list of all the things in blue bottles, I will just get the penny. Not the blue bottle. Because it is not IN a blue bottle. It IS a blue bottle but it is not IN one. Understand?

The FolderName variable contains the name of the folder containing the current item. The "x" folder IS a folder whose name contains "Maybe" but it is NOT IN a folder whose name contains "maybe".

On other matters, the proper use of subrules is too large and complex of an issue to treat here. Maybe I will write it up some other time. Just one hint: hit the [-] icon from the FRONT of each rule to collapse the display into something readable. I'm not certain but I THINK what its doing is converting from a hierarchically indented display in Polish notation into a Boolean display. Knowing this, you can try stuff and then convert to Boolean to see what it really does.

One more hint: This is counterintuitive and weird but and rule which has any subrules can itself hold only one of two possible values, [BLANK] or [NOT] - if you put any other content into a rule and then give it a subrule, the other content vanishes and returns only after the last subrule gets deleted.

OK, one more hint. The rule editor on Android (and, I assume, on Apple) is newer and far easier to understand. You can develop rules there and then export them and import them on Windows. Once you go above about three pairs of parentheses you should probably switch to working on Mobile MLO if you have it.

Proper Dwight

On 9/29/2020 17:12, Dwight Carr wrote:

Dear Proper Dwight,  LOL

Adding the contexts "someday" and "maybe" to the folder did remove it from view.  I have the option set to ask me about context when I drag/drop an item..., but I looked at it again and I guess I still don't understand why "FolderName does not contain 'Maybe'" would not remove the folder whose name contains "maybe".  I tried "FolderName does not start with 'z'" and that still didn't work.  Anyway, it works now so that's good enough for me.  

I don't understand how sub-rules work, but I guess they work like () in boolean filters.  I really need to review boolean filters...  

Also, can you clarify?  If I select a context from the context filter box then all the included filters are included as well, but if I select "Contexts is (exactly)" then only the selected context is shown, not all of it's included contexts.  Is that correct?

Thanks again,

other Dwight...

[Dwight Carr]

Thanks for the explanation. I will keep experimenting. 

Best Regards,

Other Dwight...

[Dwight Carr]

I guess I thought the filter referred to the folder's name, not contents.  I guess that's why "starts with" also doesn't work.   Anyway, I get it now.  I have a few other view/filter type questions below. Please let me know if you think I should start a new thread for these.

It probably isn't possible, but is there any way to "zoom" inside the context top line item when showing To-Do "Active by Context" view?

Is there anyway to set up a rule where if I  mark an item as a goal it will automatically add the context "Goal" or project add the context project and/or vice versa?

Thanks for your help,

The Other Dwight...

[Stéph]

Hello Dwight,

"Active by Context" will be showing you a flat list, grouped by Context. You can't "zoom" inside a group heading - The nearest you can do is collapse all the groups apart from the one you're interested in. On the desktop version, there's a shortcut key for collapsing all except the currently highlighted group. Using the left and right arrow keys, you can close or open up and navigate within a branch or group.

Regarding automatic setting of task parameters, dependent on other parameters of that task (or its parent, or nearest sibling task), no - at the moment nearly every parameter is totally independent of all the others.  So, for example, you can have a folder which is a project, you can have an unstarted project even after tasks within that project have been checked off, you can have a high urgency task with a due date many years into the future, and you can have a subtask with a start date earlier than its parent task. All of this is in the name of flexibility, as one user has quite a different set up to another. The downside of this is I often have to click and set several parameters to a task to make it behave how I want. I've tried to get interest in the idea of being able to define how new task parameters are set in relation to their parents or sibling tasks (much like an older outliner called Bonsai used to do), but so far the developers have not been keen to do this. I'm not seething with disappointment, really :-).

All the best,

Stéphane