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

Data in editable children lost without warning when moving node in tree #23979

Closed
lekoder opened this issue Nov 26, 2018 · 3 comments · Fixed by #45265
Closed

Data in editable children lost without warning when moving node in tree #23979

lekoder opened this issue Nov 26, 2018 · 3 comments · Fixed by #45265

Comments

@lekoder
Copy link
Contributor

lekoder commented Nov 26, 2018

Godot version:
3.1.aplha. c025f52

OS/device including version:
Windows 10

Issue description:
When moving an instanced scene with editable children, the "editable children" flag is lost. Moving the scene back re-enables the flag. If scene is saved when instanced scene is in new location, all children data is lost without warning.

Expected behaviour:
When moving an instanced scene with editable children, all modifications are preserved.

Actual behaviour:
When moving an instanced scene with editable children, editable flag is lost. Child modification data is lost as soon as scene is saved to disk.

Steps to reproduce:

  1. Instance a scene with editable children.
  2. Make modification to the children.
  3. Move the instanced scene in scene tree.
  4. Save and reopen.

Probably related to #20409 and #6455.

@KoBeWi
Copy link
Member

KoBeWi commented Jul 22, 2020

Still valid in 0cd98ec

@chucklepie
Copy link

chucklepie commented Jan 2, 2021

Is this the same issue:

  1. I added an inherited scene
  2. I made a ton of modifications
  3. I renamed the node
  4. It reverted back to non-inherited and I lost every single change to settings I made other than the new items I added as children :(

i.e. I didn't even move, duplicate or instance anything. I simply renamed a node after editing it.

I've done this so many times now it's really annoying me and wonder why it hasn't been fixed yet as it seems pretty nasty and horrible, especially given you won't be saving or committing files during the process of simply renaming a node....

@chucklepie
Copy link

chucklepie commented Jan 18, 2021 via email

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.

5 participants