OK, this is my fault for being a flake. I did not pick up the key term “inferred hierarchy” referring to that new feature, which I haven’t been testing yet so it’s not cemented in my mind as part of Legend. I read the word as “inherited” which was probably just me projecting.
But I did want to post this issue anyway so thanks for splitting it out! I would have couched it as a request because I don’t think it’s truly a “broken” feature (bug) — I believe the behavior is what you intended but I’m suggesting adjusting it for improved usability.
The scope of trait “inheritance” for filter-matching is limited by zoom level, which makes sense on principle because having traits from descendants above the zoom affect Pane contents would be hard to track and most likely not give intended results. But the “cut off” is currently below the zoomed-to item. So, given:
- Parent A
— child [star]
-— grandchild
An unzoomed pane filtered for star will show child. But if user zooms into child they end up looking at an empty Pane because child’s star is now out of scope for inheritance so grandchild doesn’t inherit it.
This makes zooming less usable in filtered panes and seems like it would be confusing to new users. It still catches me off guard sometimes. I frequently want to just temporarily pop in to a project that has matched my criteria to handle items inside it, but my filter includes ‘project’ so I can’t. (This is also a great use-case for (fixed) popup panes, but seems like something that should be doable right in the outline).
I know the threshold has to be somewhere, or else it’s impossible to control filter scope with zoom at all. I just think that point should be shifted up one level, especially since the zoomed Parent-item is still visible in the Pane’s header area. Probably when you originally created this behavior it was before we had Pane Headers?
