Skip to content
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

Select tool translates node when dragging w/o the gizmo over geometry #87949

Closed
ryevdokimov opened this issue Feb 4, 2024 · 15 comments · Fixed by #87948
Closed

Select tool translates node when dragging w/o the gizmo over geometry #87949

ryevdokimov opened this issue Feb 4, 2024 · 15 comments · Fixed by #87948

Comments

@ryevdokimov
Copy link
Contributor

ryevdokimov commented Feb 4, 2024

Tested versions

v4.2.1.stable.mono.official [b09f793]
v4.3.dev.custom_build [b4e2a24]

System information

Godot v4.2.1.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - integrated AMD Radeon(TM) Graphics (Advanced Micro Devices, Inc.; 31.0.24002.92) - AMD Ryzen 7 PRO 6850U with Radeon Graphics (16 Threads)

Issue description

When attempting to region-select over geometry while a node is selected, and the select tool is enabled, the selected node ends up being translated, which seems wrong.

2024-02-03.23-23-48.mp4

Steps to reproduce

See video.

Select node using select tool.

Attempt to region select over some kind other geometry like another mesh.

Minimal reproduction project (MRP)

N/A

@KoBeWi
Copy link
Member

KoBeWi commented Feb 4, 2024

I can't reproduce it. Select Mode will always select.
Tested on master.

@ryevdokimov
Copy link
Contributor Author

I also just tested on master and can reproduce on that build as well. To be clear, you are holding down the mouse starting on-top of some geometry like a mesh, and then dragging as if you're doing a region select?

@AThousandShips
Copy link
Member

AThousandShips commented Feb 4, 2024

This is specific to region select, which isn't specified in the issue report

Note that this was done by design as far as I can tell, or simply from the comment, so this shouldn't be considered a bug IMO, and we need to look at the consequences of this change

@KoBeWi
Copy link
Member

KoBeWi commented Feb 4, 2024

Ah I see it now. There are 2 object involved and the selected one is being moved when you drag a different object. This is definitely a bug, dragging should only happen on the selected object.

@KoBeWi KoBeWi added bug and removed discussion labels Feb 4, 2024
@ryevdokimov
Copy link
Contributor Author

Fair point. I updated the reproduction instructions. I did a git blame to trace some of the PRs involved with this back and I couldn't find any explanation that this was by design.

@AThousandShips
Copy link
Member

I mean the comment saying it implies design, and it was approved as such, see:

@KoBeWi
Copy link
Member

KoBeWi commented Feb 4, 2024

The PR linked shows a different issue.

@ryevdokimov
Copy link
Contributor Author

I mean the comment saying it implies design, and it was approved as such, see:

Yes, I saw that PR, but I don't see an explanation that translating the node in place of region select is the intended design.

@AThousandShips
Copy link
Member

Yes but it's the origin of this, at least we need to ensure the issues in that PR doesn't resurface

But I fail to see how "select only if nothing is selected" isn't clear intention

@ryevdokimov
Copy link
Contributor Author

Fair point again, but it also isn't true and isn't described in the PR itself only in the comment of the code itself which can be overlooked. In both 4.2 and master, you can region select while nodes are selected, but only outside geometry. This isn't explained anywhere, and also doesn't really make any sense IMO.

@AThousandShips
Copy link
Member

AThousandShips commented Feb 4, 2024

Oh thank you for specifying that part 🙂 it got lost in the very long title (of the PR) 😄

@ryevdokimov
Copy link
Contributor Author

Triple fair point, I'll do better in my explanations from the get-go. Sometimes I just get caught up in writing code.

@AThousandShips
Copy link
Member

AThousandShips commented Feb 4, 2024

Oh it's natural, I should have read more carefully, but good to add in the description of the PR, especially with very long titles it's easier to get the info from the text

Keep also in mind that it can be hard to tell from a video what behaviour is the issue, it's easy to think "oh this is clear" when you know what's wrong already, so important to capture the issue in text too

@AThousandShips AThousandShips added this to the 4.3 milestone Feb 4, 2024
@ryevdokimov
Copy link
Contributor Author

Titles too long, descriptions too short got it. 😂

@Cammymoop
Copy link
Contributor

This is a duplicate of #85736

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants