Closed MrZak-dev closed 2 months ago
You should export[^1] the property so that it is taken into account by the duplicate()
method and serialization.
This is documented here, but we need to copy the note into descriptions of similar methods, see #80585.
[^1]: At least the PROPERTY_USAGE_STORAGE
flag must be present, since 4.3 dev there is an annotation @export_storage
.
@dalexeev adding the @export_storage
annotation works as expected , Thank you .. however i just find the documentation confusing a little bit when it says :
Note: Not all properties are included. Only properties that are configured with the @GlobalScope.PROPERTY_USAGE_STORAGE flag set will be serialized.
Then when we take a look at where this link goes :
PropertyUsageFlags PROPERTY_USAGE_STORAGE = 2 The property is serialized and saved in the scene file (default).
The way i interpreted the (default) is that this flag is already set by default for the class' properties. isn't it the case or am i missing something .
PROPERTY_USAGE_DEFAULT
is used by default for exported properties, in _get_property_list()
, etc. But by default, script variables are not exported at all:
var a # SCRIPT_VARIABLE
@export_storage var b # STORAGE | SCRIPT_VARIABLE
@export var c: int # DEFAULT | SCRIPT_VARIABLE
We should probably clarify this in the documentation.
Fixed by #94155.
Tested versions
4.3.beta2
System information
MacOS Sonoma, Compatibility Renderer
Issue description
It appears that the methods
var_to_bytes_with_objects
andbytes_to_var_with_objects
do not work as expected when serializing and deserializing class instances. Specifically, properties of the instance revert to their initial values instead of retaining any changes made before serialization.Steps to reproduce
var_to_bytes_with_objects
.bytes_to_var_with_objects
.Example Code
Minimal reproduction project (MRP)
test.zip