You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Isolating an element with shift+click also expands the element tree.
It could be practical to isolate root elements without altering the tree collapsing state (which node is collapsed and which is expanded). This way we could easily navigate between root elements.
ux proposal:
keybord: page up / page down to isolate previous / next root element;
ctrl + click on the element in the tree.
For a better understanding of my use case, I'm working on bd_shape_history, which is a tool to visualize the modification history of Build123D objects, so we can display a visual diff between each step:
Being able to quickly navigate between each "step" (which are just regular objects) would be very handy in this case.
The text was updated successfully, but these errors were encountered:
Isolating an element with shift+click also expands the element tree.
It could be practical to isolate root elements without altering the tree collapsing state (which node is collapsed and which is expanded). This way we could easily navigate between root elements.
ux proposal:
For a better understanding of my use case, I'm working on bd_shape_history, which is a tool to visualize the modification history of Build123D objects, so we can display a visual diff between each step:
Being able to quickly navigate between each "step" (which are just regular objects) would be very handy in this case.
The text was updated successfully, but these errors were encountered: