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

Children of (V,H)BoxContainer can be moved by manipulating with values in the inspector #55270

Closed
SuperTemich2005 opened this issue Nov 23, 2021 · 4 comments

Comments

@SuperTemich2005
Copy link

Godot version

3.2.3.stable

System information

Windows 10

Issue description

You can not move children of the (V,H)BoxContainer in the editor, unless you access it's values in the inspector.
Once the scene is refreshed, illegal shift is reverted.

Steps to reproduce

image
Try to move the child node of the (V,H)BoxContainer
2) Go to the inspector and change rect_position or position of the object
image
(Button labeled Разговор is a child of HBoxContainer node, yet by manipulating with rect_position.y it can be shifted N units along Y axis. Same for X axis. Button labeled Осмотреть is where it's supposed to be)
3) Switch to another tab (in my case, i switch to ahata_day1.tscn from investigation_v3.tscn)
image

  1. return to the tab you've switched from (back to investigation_v3.tscn)
    image

  2. Child is in place, as if it wasn't moved (button labeled Разговор teleported to where it's supposed to be, I haven't changed any values related to it myself, it did it itself)
    image

Minimal reproduction project

No response

@SuperTemich2005
Copy link
Author

This issue was originally discovered by InSaNe_97#4268 and he used v3.4.stable.official [206ba70]. It means that the bug exists at least from 3.2.3.stable and has been carried over to at least 3.4 release

@YuriSizov
Copy link
Contributor

YuriSizov commented Nov 23, 2021

This is a known issue, and it's already fixed in master by disabling those properties when inside of a container. See #30623.

We also work on the new workflow to prevent users from accessing irrelevant properties when working on children of containers.

@superPilipala
Copy link

You can't fix this bug like this.When I want to iterate a container on top of a container of my own, for example, I want to follow the arrangement of the container in the y-direction and make some offsets in the x-direction to make a radial menu. Disabling the position property of the child node complicates my ability to do this effect. And, on the other hand, I want to make a ui animation for the nodes inside the container, and not being able to change the position of the child nodes makes the effect very bad

@superPilipala
Copy link

Sorry, I didn't get it right, it's possible to extends the BoxContainer with the fit_child_in_rect() method, but the animation problem is still not known what to do.

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

No branches or pull requests

3 participants