godotengine / godotengine/godot

Expand All keyboard shortcut is missing unless you add a node to the tree

Open
#93,010 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs testing topic:editor topic:input
Dominant language
C++
Stars
117k
Forks
26.8k
PR merge metrics
PR metrics pending

Description

Tested versions
  • Reproducible in 4.2.2 and 3.5.3 (seems old)
System information

Windows 10

Issue description

If you open a project and go directly to Editor Settings > Shortcuts and search for Expand All, it is missing from the list.

If you close that window, and then add a node to the try, or otherwise click on a node in the tree, it will add the shortcut to the list (so now if you search the editor settings>shortcut list, Expand All will suddenly be there)

It seems that commands for the shortcut list don't populate until they're first made to appear in editor?

Steps to reproduce
  • Open a project

  • Go directly to Editor > Editor Settings > Shortcuts and search for the word Expand (before clicking on any nodes)

  • Note the lack of an Expand All option

  • Close settings, and click on a node/add a node and click on it

  • Go directly to the settings/shortcut again and search Expand

  • Note the appearance of Expand All

Minimal reproduction project (MRP)

N/A - from my testing it is reproducible in any project that you open and go to settings before selecting a node

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is identified in the report. Reproduce the issue by opening Editor Settings > Shortcuts before selecting a tree node, then trace how the Expand All command is registered and populated; done means Expand All appears immediately without first interacting with the scene tree.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.