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
Issue description:
Expected behavior: Overridden instance properties remain overridden until the reset button is pressed.
Actual behavior: Changing a scene property to the same value as an overridden instance property causes the instance property to no longer be considered overridden.
Steps to reproduce:
Load the project from below. Scene 'label' is a label with Text set to "scene-value". Scene 'main' contains 3 instances of 'label'. Label3 has Text set to "override-value".
Open label.tscn and change Text to "override-value".
Save the scene.
View scene 'main'. Notice that Label3 no longer has a reset button for its Text property.
Switch back to scene 'label'.
Change Text to "scene-value".
Save the scene.
View scene 'main'. All labels now have Text set to "scene-value".
I think this might be intended behaviour, but I agree that it's confusing and unexpected in this case.
I also agree that a more consistent behaviour would be to always keep the overriding value, even if it happens to be the same, regardless of whether the parent was changed to match the child or vice versa. If people want to reset to the inherited value, they can use the reset button for that.
The whole point of scene inheritance is to facilitate changes to the parent scene, so such changes should be "safe" regardless of what values were configured in inherited scenes.
Godot version: v3.02.stable.official
OS/device including version: Windows 10 64-bit
Issue description:
Expected behavior: Overridden instance properties remain overridden until the reset button is pressed.
Actual behavior: Changing a scene property to the same value as an overridden instance property causes the instance property to no longer be considered overridden.
Steps to reproduce:
Minimal reproduction project:
Instance Properties Bug.zip
The text was updated successfully, but these errors were encountered: