-
-
Notifications
You must be signed in to change notification settings - Fork 21.6k
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
Fix 3D Select Mode not moving clicked node #85740
base: master
Are you sure you want to change the base?
Conversation
76e7fc9
to
f0813c3
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.
All tools can select now since: #86804
So, when you select->drag, in other modes the behavior does not match.
2024-01-30.17-40-51.mp4
Also, I'm not sure if this is desired behavior. I could see situations where you want to box select, with unlocked nodes in the background where the select would be initiated. I think this makes too strong of an assumption of what the user wants, where a two-step process will prevent accidents. I would argue 2D is the one that needs to be changed. |
Thanks for pointing that out, I'll fix that up.
This seems to be a small regression from 3.2 and a bigger regression from 3.5 onward, see the mentioned issue. I restored the old, presumably intended behavior, I think a case could be made to change the behavior (including the 2d editor) but I preferred not to make that call when I could simply restore the existing behavior to fix the actual issue. For what it's worth I support an (optional) setting to have select mode start a box select when dragging over another node instead of selecting then dragging as I would find that useful, not to the exclusion of the current behavior though, especially in 2d. As it currently stands it is simply intuitive and unhelpful and doesn't allow for starting a box select in that situation or several other more unambiguous situations. A pretty common example is where a large environment mesh exists in the scene but is locked for obvious reasons, and you want to use the select tool make box selections and move things around (along with axis constraining shortcuts this is pretty usable). The regression since 3.5 makes it even worse because in addition to having to hide the environment or use shift to make the box selections you also can't move an individual node without two clicks, and clicking to select it might put a gizmo under your cursor so you have to search for a neutral spot after the first click. |
f0813c3
to
3bd3a39
Compare
Translation now only starts with Select or Move tool active during the first click + drag, as in 2D editor. (Rotation and scale do nothing with the first drag) |
I can confirm that this PR does what it says it does and matches 2D behavior, without any issues I can find. I'll be interested to hear what the engine team thinks. @Calinou? |
There is one difference from the 2D editor in that you can click on 2D nodes that are behind a locked node, but you cannot in 3D. (see also #84764 and my comment on the attached PR) |
Fixes #85736
Fixed:
Clicking and dragging a node when no nodes are selected selects and starts to translate it, rather than starting a box select.
With a node selected, clicking and dragging another node in select mode both selects and starts to translate the clicked node rather than the currently selected node.
Clicking and dragging on a locked node now starts a box select rather than translating the currently selected node (just as clicking and dragging on the background.
Clicking and dragging on (one of) the selected node(s) works as before.
3D Select Mode now works more or less like 2D Select Mode, and 3D Select Mode prior to 3.2
With the added bonus of not selecting locked nodes like was possible in 3.1