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

Cannot lock or group child nodes of ParallaxBackground #88939

Closed
ghost opened this issue Feb 28, 2024 · 0 comments · Fixed by #88997
Closed

Cannot lock or group child nodes of ParallaxBackground #88939

ghost opened this issue Feb 28, 2024 · 0 comments · Fixed by #88997

Comments

@ghost
Copy link

ghost commented Feb 28, 2024

Tested versions

v4.2.1.stable.official [b09f793]

System information

Godot v4.2.1.stable - KDE neon 5.27 22.04 - X11 - GLES3 (Compatibility)

Issue description

Normally one can click on a node with children in the Scene panel of the editor and then click the Lock or Group buttons to prevent selecting or moving those children independently:

image

However this isn't the case for the ParallaxBackground node... Clicking those buttons (which aren't disabled, so should be usable) doesn't do anything - child nodes (e.g. Sprite2D's) are still selectable and movable. I do notice however that the buttons are instead labelled Unlock and Ungroup...

image

If this is by design, I suggest making these buttons disabled for ParallaxBackground nodes to avoid confusion.

Steps to reproduce

  1. Open the 'parallax_test.zip' MRP below
  2. Click and drag one of the icons in the editor to show they're not locked/grouped
  3. Select the ParallaxBackground node in the Scene panel, then click on the Lock/Unlock and Group/Ungroup buttons
  4. Notice the button icons don't change
  5. Click and drag one of the icons in the editor to show they're still not locked/grouped

Minimal reproduction project (MRP)

parallax_test.zip

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.

2 participants