Open jleibs opened 7 months ago
Related issue re: proper visibility handling in the hierarchy:
As noted in the discussion today, this is temporarily going to be more complicated when Groups are removed, and call for either:
We discussed the "visibility" issue with @nikolausWest this morning and the outcome was:
Related:
Proposal
Every Space View has a property: “origin”:
When evaluating a query-expression, we allow for substitution of “$origin”
$origin
is clear and explicit in it’s meaning.The default query for every spaceview becomes “$origin/**”
When displaying the query results under a SpaceView the query results are divided into two sub-sets:
Why don’t we use “../..” style paths?
Implies
rr.view.Spatial2D(origin="world/camera", contents="$origin/**")
Which is syntactic sugar for:
entities = rr.view.EntityPathExpression("$origin/**") rr.view.Spatial2D(origin="world/camera", contents=entities)