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
Hi,
Unless I missed something, it looks like in cases where a tween is created but no actual movement needs to happen (the target value is the same as the original value) the tween is aborted and its callbacks are not called.
I'm guessing this is an intentional design choice? Doesn't it make more sense for the tween to be totally agnostic about such things and basically run as usual?
The text was updated successfully, but these errors were encountered:
The tween indeed doesn't care if there actual change or not, and it runs anyway and calls the callbacks. Maybe it's getting killed for other reasons (try to set LogBehaviour to Verbose to get more info).
Hi,
Unless I missed something, it looks like in cases where a tween is created but no actual movement needs to happen (the target value is the same as the original value) the tween is aborted and its callbacks are not called.
I'm guessing this is an intentional design choice? Doesn't it make more sense for the tween to be totally agnostic about such things and basically run as usual?
The text was updated successfully, but these errors were encountered: