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
I was actually exited to get rid of the Godot.Tweens... Until I took a look into GTweenGodotExtensions.Tween...
InterpolationTweenBehaviour interpolationTweenBehaviour = new InterpolationTweenBehaviour();
interpolationTweenBehaviour.Add(new GodotVector2Tweener(getter, setter, to, duration, validation));
return new GTween(interpolationTweenBehaviour);
Immediately three new classes... One of them immediately creates two collections...
That's at least 5 allocations (I didn't dig deeper...)...
Am I overlooking something, or do those Tweens allocate a lot of garbage?
No offence, but I'm trying to keep garbage production to a minimum...
The text was updated successfully, but these errors were encountered:
Hey, thanks for raising this, It's a valid concern.
I'll admit allocations were not my priority while developing this library, usability was.
I guess some work could be done to improve this through some form of pooling, but it's not as trivial as it sounds.
I was actually exited to get rid of the Godot.Tweens... Until I took a look into GTweenGodotExtensions.Tween...
Immediately three new classes... One of them immediately creates two collections...
That's at least 5 allocations (I didn't dig deeper...)...
Am I overlooking something, or do those Tweens allocate a lot of garbage?
No offence, but I'm trying to keep garbage production to a minimum...
The text was updated successfully, but these errors were encountered: