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
Love redux-time! I am using it with react-three-renderer and it works very well. However, currently an object automatically reverts to its old position after running the 'Animate' or 'Translate' function. I use 'Become' to set the position after doing the animation. I am not sure if this is best practice.
My suggestion would be to add a boolean option in the object passed into the 'Animate' or 'Translate' function with something like "revert: true/false". On "false" the end_state will be permanent in the Redux store.
The text was updated successfully, but these errors were encountered:
We think adding a flag is actually a great idea, as it's more intuitive than a second Become at the end, so we'll be implementing this at some point. Thanks for the suggestion @akoel!
Love redux-time! I am using it with react-three-renderer and it works very well. However, currently an object automatically reverts to its old position after running the 'Animate' or 'Translate' function. I use 'Become' to set the position after doing the animation. I am not sure if this is best practice.
My suggestion would be to add a boolean option in the object passed into the 'Animate' or 'Translate' function with something like "revert: true/false". On "false" the end_state will be permanent in the Redux store.
The text was updated successfully, but these errors were encountered: