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
When changing a type, it would be good to serialise the current value, and then deserialise into the new object instead of using the activator. That way, any properties they share will be retained.
I would also add a “make unique” button that just clones the object (also using jsonutility), useful after a “duplicate array” operation. This could be a little button next to the selector (or a … button that opens a menu).
The text was updated successfully, but these errors were encountered:
The asset is excellent, and both are nice suggestions; the first one is highly appreciated if we use a lot of inheritance, and the second one, you usually won't want a duplicate reference. An easy way to make it unique seems logical... not sure how to implement the UI/UX part...
Improvement destription
When changing a type, it would be good to serialise the current value, and then deserialise into the new object instead of using the activator. That way, any properties they share will be retained.
I would also add a “make unique” button that just clones the object (also using jsonutility), useful after a “duplicate array” operation. This could be a little button next to the selector (or a … button that opens a menu).
The text was updated successfully, but these errors were encountered: