-
Notifications
You must be signed in to change notification settings - Fork 394
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
Implement range selection with shift-click in the time panel #8870
Conversation
Web viewer built successfully. If applicable, you should also test it:
Note: This comment is updated whenever you push a commit. |
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.
nice, reading this right after the blueprint tree one this feels like more of the same with situational adaptation :)
re_log.workspace = true | ||
re_log_types.workspace = true |
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.
somewhat curious this needs log types actually and not just types_core, ah well...
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.
It was there already, was just reordered.
use re_log_types::{
ApplicationId, ComponentPath, EntityPath, ResolvedTimeRange, TimeInt, TimeReal, TimeType,
};
again, surprised this doesn't come with tests |
|
a2417ae
to
0c1eb2c
Compare
931672e
to
9e300eb
Compare
9e300eb
to
4b4ea81
Compare
What
Same as #8852 but in the streams tree.
This time, the visitor is slightly weird in that it enumerates the component on the fly instead of having them in the data structure. The reason for that is that this is costly and we don't want to always do it even if we dont needed (eg. when the tree is collapsed).
shift-click-streams.mp4