-
Notifications
You must be signed in to change notification settings - Fork 393
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
Make the space views bigger and less cluttered #269
Conversation
83ed6ba
to
98b4190
Compare
ah. The problem is that there is text AND 3d, it can't handle that correctly right now. Also it shouldn't show up for text views |
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.
(not completely done yet. busy finishing up morning routine and jumping on bike)
let frame = self.ctx.design_tokens.hovering_frame(ui.style()); | ||
hovering_panel(ui, frame, response.rect, |ui| { | ||
if ui | ||
.button("🗖") | ||
.on_hover_text("Maximize Space View") | ||
.clicked() | ||
{ | ||
*self.maximized = Some(*space_view_id); | ||
} | ||
|
||
let space_view = self | ||
.space_views | ||
.get_mut(space_view_id) | ||
.expect("Should have been populated beforehand"); | ||
|
||
space_view_ui(self.ctx, ui, self.spaces_info, space_view); | ||
space_view_options_link( | ||
self.ctx, | ||
self.selection_panel_expanded, | ||
*space_view_id, | ||
ui, | ||
"⛭", | ||
); |
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.
only show for 3d and 2d space views? Placing isn't great right now when we have both text and 3d/2d subviews
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.
I agree placing isn't great, but I think users should still be able to maximize and go to settings for tensor views and text log views.
I introduced this bug in egui (weird extra distance between tooltips). EDIT: found the bug: emilk/egui#2264 |
27d0600
to
a082ef0
Compare
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.
code lgtm
But tbh I always have a hard time reviewing ui code changes that touch several places, hard to get a good overview. Want to experiment a bit more with the ui and think about the spacing issues already brought up
tensor: Tensor, | ||
} | ||
|
||
fn empty_tensor() -> Tensor { |
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.
why not as part of impl Tensor
?
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.
Because it makes some arbitrary decisions on dtype
I'll see if I can make the space view buttons for view_text and view_tensor better in a later PR. |
Co-authored-by: Andreas Reich <[email protected]>
Co-authored-by: Andreas Reich <[email protected]>
49f1321
to
7791a80
Compare
Part of PRO-186
I need to merge this first:
What?
This PR moves all of the 3D view's options, and most of the tensor view's options, to the selection panel.
Then, it puts a link to the space view options, together with a "?" help menu and an maximize-button (when needed) on top of the 3D and 2D space views (partially covering their content).
This is not possible for the tensor and text log views, so there some extra "headroom" is needed to fit the above buttons (still better than before though).
Before
After
More screenshots
Checklist
CHANGELOG.md
(if this is a big enough change to warrant it)