You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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...
If this is by design, I suggest making these buttons disabled for ParallaxBackground nodes to avoid confusion.
Steps to reproduce
Open the 'parallax_test.zip' MRP below
Click and drag one of the icons in the editor to show they're not locked/grouped
Select the ParallaxBackground node in the Scene panel, then click on the Lock/Unlock and Group/Ungroup buttons
Notice the button icons don't change
Click and drag one of the icons in the editor to show they're still not locked/grouped
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:
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...
If this is by design, I suggest making these buttons disabled for ParallaxBackground nodes to avoid confusion.
Steps to reproduce
Minimal reproduction project (MRP)
parallax_test.zip
The text was updated successfully, but these errors were encountered: