Blueprint tree always starts at the origin now, "projected" paths are called out explicitly #5342
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Wumpf
added
ui
Wumpf
force-pushed
the
andreas/remove-groups
branch
from
278a1e4 to
f47b335
Compare
Wumpf
force-pushed
the
andreas/origin-focused-tree
branch
from
57f527e to
41822cf
Compare
Wumpf
force-pushed
the
andreas/origin-focused-tree
branch
from
41822cf to
e1ffe80
Compare
abey79
approved these changes
Feb 29, 2024
Comment on lines
+25
to
+29
| enum DataResultNodeOrPath<'a> { | ||
| Path(&'a EntityPath), | ||
| DataResultNode(&'a DataResultNode), | ||
| } | ||
|
|
There was a problem hiding this comment.
Multiple feelings here, including:
- This "thing that loosely relates—or is—an entity" might have wider usefulness than just here. Top of my head: context menu implementation. (The precedent here is
Contents, which isn't were it should either IMO) - This could be more related to
re_viewer_context::Itemtoo, as both of these enum branches should be included inItem
This probably is out of scope for this PR, but maybe worth adding a todo with assorted issue.
There was a problem hiding this comment.
I was quite unhappy that I had to introduce this thing. It's practically only relevent for the rare cases where the origin entity doesn't show up in the data result tree.
I could have adjusted the data result tree but I felt strongly about this ui requirement not changing the data model so that's where I ended up :/. Also, like you, I suspect that this could be useful for more things - maybe there's more entities that we want to show there there may or may not be a data result node
| // while still being able to pass &ViewerContext down the chain. | ||
| let query_result = ctx.lookup_query_result(space_view.query_id()).clone(); | ||
|
|
||
| let query_result = ctx.lookup_query_result(space_view.query_id()); |
There was a problem hiding this comment.
These diffs always feel so nice :)
|
@abey79 looks like you spotted some severe weirdness in here, thanks! Need to definitely check on these before merging |
abey79
approved these changes
Feb 29, 2024
5 tasks
abey79
added a commit
that referenced
this pull request
Mar 2, 2024
…5371) ### What Follow-up to: - #5342 After #5342, it was possible for a data result subtree to be displayed twice in the blueprint tree UI, for example: <img width="778" alt="image" src="https://github.com/rerun-io/rerun/assets/49431240/13da8014-5abf-4206-bba8-d9d5a33d3919"> <br/> This is a problem for storing collapsed state (#5362) and is generally a weird UX. This PR replaces the origin subtree by a link which, when clicked, selects the actual origin subtree (which is always displayed above the projections). https://github.com/rerun-io/rerun/assets/49431240/6655a187-c786-4d30-8451-e473267e4526 ### Checklist * [x] I have read and agree to [Contributor Guide](https://github.com/rerun-io/rerun/blob/main/CONTRIBUTING.md) and the [Code of Conduct](https://github.com/rerun-io/rerun/blob/main/CODE_OF_CONDUCT.md) * [x] I've included a screenshot or gif (if applicable) * [x] I have tested the web demo (if applicable): * Using newly built examples: [app.rerun.io](https://app.rerun.io/pr/5371/index.html) * Using examples from latest `main` build: [app.rerun.io](https://app.rerun.io/pr/5371/index.html?manifest_url=https://app.rerun.io/version/main/examples_manifest.json) * Using full set of examples from `nightly` build: [app.rerun.io](https://app.rerun.io/pr/5371/index.html?manifest_url=https://app.rerun.io/version/nightly/examples_manifest.json) * [x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG * [x] If applicable, add a new check to the [release checklist](https://github.com/rerun-io/rerun/blob/main/tests/python/release_checklist)! - [PR Build Summary](https://build.rerun.io/pr/5371) - [Docs preview](https://rerun.io/preview/8f4012dfde1a2d023ed2493bb7009fd342989b53/docs) <!--DOCS-PREVIEW--> - [Examples preview](https://rerun.io/preview/8f4012dfde1a2d023ed2493bb7009fd342989b53/examples) <!--EXAMPLES-PREVIEW--> - [Recent benchmark results](https://build.rerun.io/graphs/crates.html) - [Wasm size tracking](https://build.rerun.io/graphs/sizes.html)
emilk
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
tree.projections.mp4
Follows the design proposal from the ticket directly. Some detail decisions on how things are exactly handled, but code should be a bit more composable now (albeit admittedly still a bit messy)
Checklist
mainbuild: app.rerun.ionightlybuild: app.rerun.io