New update out! Changes:
- Advanced mode more functional: Highlights filter text in red/blue, always shows text instead of icons, improved editing
- Fixed handling of enter/tab
- Panes hide complete by default as before (I’ll consider changing this later but keeping it the same for now)
- X button clears the whole filter
- Slightly increased double click window for negating filters
- Advanced filtering will be a premium feature
- Changed star to “is:star” rather than “pi:star”
- Priority buttons set to low+, med+, high, and turn off other priority filters. You can do more complex priority filters in advanced mode like
pri:low or pri:high
- Put in a similar hints popup behind a ? button
- Added the options and calendar buttons
Buttons don’t do OR modifiers
We discussed different modifiers for buttons to add
or, but as I thought about that more, I think it’s either impossible or extremely complex.
or effectively creates groupings, like
a b or c d is equal to
(a b) or (c d). So inserting an
or with a button would have different behavior depending on the current state of the filter. I think the UI would have to be much more complex to set up
or correctly, so I think it’s best to make it only available in Advanced mode, at least for now?
Ready to go!
I believe this is now ready to take out of the demo-mode experiment and make it a real beta feature. I will just test the migration from the previous filter system some more and release it as a “Test Beta Features” feature.
I will come back to the other suggestions as I’d like to get this set of features finished and releasable, then we can build on it.
is:parent and is:child sound very interesting! But with the way filtering works matching all the way up the hierarchy, those would just match everything because a hierarchy will always have at least one parent and one child. If you could give me some more examples of how you’d like a filter like that to work, we might find a way to make that filter work, or maybe it should be an option, or solved a different way.
If you’re wanting filtering to show only matches and not their children, List view does that. But of course it loses hierarchy. My struggle with hiding all children is it could be confusing why large projects have no children, and behaviors like indenting would break - they would immediately get hidden because children should not exist). That’s why it’s only a feature of Flat view for now. Another way to solve it could be to have an option/button/hotkey to collapse the deepest nodes that match the filter?
@andrew I made the priorities mutually exclusive and toggle others off as you suggested. Types are not necessarily mutually exclusive, like
is:project is:task would find task children of projects. So I think those should stay as they are?