-
-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose Easing equations #36
Comments
There's an |
@Calinou I have used that at first. But it was not enough for what I was doing. Besides, it was confusing to use at the beginning, until I came across godotengine/godot#10572 with its graph. I suppose the Tween approach gives more control over easing in terms of |
This can be used as an alternative to `Tween.interpolate_property()` when additional control is needed. This closes godotengine/godot-proposals#36. Co-authored-by: Nasser Alansari <[email protected]>
@KoBeWi Is this proposal still relevant with the Tween rewrite? |
No, you can just do |
Godot Version:
(3.1.1-stable)
Describe the project you are working on:
The project I'm working on required the use of easing functions(the compute part of it) and not whole Tweening.
Describe how this feature / enhancement will help your project:
Godot already implemented Easing functions('interpolaters') internally for the use within Tween, but they are not exposed. I believe it would be helpful to have them expose
Describe implementation detail for your proposal (in code), if possible:
I have already patched the Godot source to expose this functionality(see below). It is working for me (at least for my use-cases).
I have added a method to Tween class and bind it, but it could be part of Math funcs or another namespace/class.
If this enhancement will not be used often, can it be worked around with a few lines of script?:
One might reimplement the easing functions in pure GDScript. I initially did that for some of the needed easing equation.
Is there a reason why this should be core and not an add-on in the asset library?:
Most of the code already implemented in the core and it is a matter of exposing it
The text was updated successfully, but these errors were encountered: