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

Arrow keys doesn't select objects on the scene hierarchy #12544

Closed
samvila opened this issue Oct 31, 2017 · 9 comments · Fixed by #86218
Closed

Arrow keys doesn't select objects on the scene hierarchy #12544

samvila opened this issue Oct 31, 2017 · 9 comments · Fixed by #86218

Comments

@samvila
Copy link
Contributor

samvila commented Oct 31, 2017

Operating system or device, Godot version, GPU Model and driver (if graphics related):
Godot 3.0 Alpha 2, Windows 10 64 bit

Issue description:
Arrow keys doesn't select objects on the scene hierarchy, please see this video as reference:
https://youtu.be/lRbefcsYDi4?t=99

Notice how by using the arrow keys doesn't really select the items, only changes the property window information but doesn't have any effect on the viewport.

@TheSofox
Copy link
Contributor

TheSofox commented Nov 8, 2017

Taking a look at this now....

TheSofox added a commit to TheSofox/godot that referenced this issue Nov 10, 2017
…ted in the scene hierarchy when navigating with arrow keys through the scene tree.
@TheSofox
Copy link
Contributor

I have been told "current behavior is fine" and my bug fix pull request that I spent time and effort making has been closed without committing.

@samvila
Copy link
Contributor Author

samvila commented Nov 13, 2017

Wow, that's a real shame @TheSofox , I think the video on the description shows a common workflows expected from users coming from others engines and their possibly disappointment which I think is a great user case in my opinion.

@Zireael07
Copy link
Contributor

The PR has been reopened and akien said the behavior is not fine.

@akien-mga akien-mga added this to the 3.1 milestone Feb 14, 2018
@Piet-G
Copy link
Contributor

Piet-G commented Sep 30, 2018

This seems fixed in master.

@akien-mga
Copy link
Member

Indeed, this was likely fixed by @Faless' refactor in #16947.

@akien-mga akien-mga reopened this Oct 3, 2018
@akien-mga
Copy link
Member

Reopening as it appears to be specific to some 3D nodes like Area or RigidBody. Nodes with other gizmos like ReflectionProbe are properly highlighted.

CC @JFonS

@samvila
Copy link
Contributor Author

samvila commented Oct 3, 2018

On my tests it fails when the structure is a 3D node and the childs are meshinstances. Just for your reference.

@KoBeWi
Copy link
Member

KoBeWi commented Jan 3, 2022

This is a bug. When you change nodes using arrows, seems like only the focus changes. There's also selection_changed signal sent and for some nodes, the editor will select the element. The selecting seems to happen only for 2D nodes:
Mhdn4el1lE

EDIT:
Here are some duplicate issues with potentially more info: #22397 #36291

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.

8 participants