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
As far as i can see the Animator<> is generic over the Tweenable and that becomes very hairy and bespoke for each tween generated to be able to remove the whole Animator again from an entity.
What is the best practice here?
The text was updated successfully, but these errors were encountered:
Animator<> is generic over the target Component because you need to declare the system parameters at build time for Bevy to work (at least until we get dynamic queries). I think the best practice is not to remove the Animator at all; what are you concerned about leaving it?
As far as i can see the
Animator<>
is generic over theTweenable
and that becomes very hairy and bespoke for each tween generated to be able to remove the whole Animator again from an entity.What is the best practice here?
The text was updated successfully, but these errors were encountered: