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
I'm upgrading my project to the latest version of ponder and in the release notes I saw "Changed UserObject reference semantics.". With this change I'm not sure how I go about setting nested user types. For example if you look at seralise.hpp ArchiveReader::read
if (arrayProperty.elementType() == ValueKind::User) { read(item, arrayProperty.get(object, index).to<UserObject>()); }
With the new semantics, doesn't that Value.to just make a copy and not actually update the object as you'd expect?
If I'm way off and there's documentation you could point me at it would be greatly appreciated.
Thanks
The text was updated successfully, but these errors were encountered:
I'm upgrading my project to the latest version of ponder and in the release notes I saw "Changed UserObject reference semantics.". With this change I'm not sure how I go about setting nested user types. For example if you look at seralise.hpp ArchiveReader::read
if (arrayProperty.elementType() == ValueKind::User) { read(item, arrayProperty.get(object, index).to<UserObject>()); }
With the new semantics, doesn't that Value.to just make a copy and not actually update the object as you'd expect?
If I'm way off and there's documentation you could point me at it would be greatly appreciated.
Thanks
The text was updated successfully, but these errors were encountered: