-
Notifications
You must be signed in to change notification settings - Fork 388
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: disconnect spaces when their categories differ #3790
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -48,7 +48,9 @@ fn candidate_space_view_paths<'a>( | |
spaces_info | ||
.iter() | ||
.map(|info| &info.path) | ||
.chain(root_children.values().map(|sub_tree| &sub_tree.path)) | ||
// TODO(jleibs): These root children shouldn't need manual adding. If they are interesting | ||
// they should have been generated by the SpaceInfos | ||
//.chain(root_children.values().map(|sub_tree| &sub_tree.path)) | ||
.unique() | ||
} | ||
|
||
|
@@ -150,11 +152,15 @@ fn is_interesting_space_view_at_root( | |
// | ||
// If there are any images directly under the root, don't create root space either. | ||
// -> For images we want more fine grained control and resort to child-of-root spaces only. | ||
|
||
// TODO(jleibs): This gets in the way | ||
/* | ||
for entity_path in &candidate.contents.root_group().entities { | ||
if contains_any_image(entity_path, data_store) { | ||
return false; | ||
} | ||
} | ||
*/ | ||
|
||
true | ||
} | ||
|
@@ -165,6 +171,9 @@ fn is_interesting_space_view_not_at_root( | |
classes_with_interesting_roots: &[SpaceViewClassName], | ||
query: &LatestAtQuery, | ||
) -> bool { | ||
// TODO(jleibs): Why not make everything interesting? | ||
return true; | ||
Comment on lines
+174
to
+175
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Much preferred. The whole idea of not having space_view at root be always a thing is from back then when we never allowed it in the first place. The heuristics today tries to allow two ways of thinking and a mix of it right now: One where you have one scene at the root and one where you have many scenes each under a |
||
|
||
// TODO(andreas): Can we express this with [`AutoSpawnHeuristic`] instead? | ||
|
||
// Consider children of the root interesting, *unless* a root with the same category was already considered interesting! | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also ideally they're not in
re_viewport
but instead have this be governed by the heuristic method on the SpaceView trait. re_viewport knowing about re_types is kind of a hackThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Associating some kind of "Preferred
SpaceInfoCategory
" metadata in the schema registry is an interesting thought.Related: