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
Deserialization breaks when the event list is changed via inspector while ES is active.
As the ES changes persist, the session has to be killed by restarting vite.
What browsers are you seeing the problem on? πββοΈ
Chrome
Editor Version π²
2021.3
Needle Exporter version
3.14.0-pre
Project Info (Unity only) π
No response
Steps to reproduce π’
1) Export and start the scene with ES
2) The grid should blink on and off (triggered by _boolEvent), the Cube should move (triggered by _nonGenericEvent).
3) Modify one of the events via inspector (e.g. by clicking on the +)
4) Watch the triggers not working anymore (grid should stop blinking or Cube moving, depending on which event was modified)
5) Reload page => Triggers not working anymore
6) Restart vite and reload page => Triggers working until events get modified again
Reproduction β»
Uploaded as Bugreport-Minimal 1-230913-115251_uw.zip
The next version (> 3.16.2) will ignore UnityEvent modifications for now and add an EditorModificationHandler.HandleChange event which can be used to ignore certain modifications (the arguments have the target object, propertyname and value as well as a bool for preventDefault. Setting this to true will ignore the change).
This event also allows to modify the target and object data if necessary
Describe the bug π¬
Deserialization breaks when the event list is changed via inspector while ES is active.
As the ES changes persist, the session has to be killed by restarting vite.
Operating System π©βπ»
Windows
What browsers are you seeing the problem on? πββοΈ
Chrome
Editor Version π²
2021.3
Needle Exporter version
3.14.0-pre
Project Info (Unity only) π
No response
Steps to reproduce π’
Reproduction β»
Uploaded as Bugreport-Minimal 1-230913-115251_uw.zip
Discord or Discussion link
No response
Validations π©Ή
The text was updated successfully, but these errors were encountered: