Enable non-linear easing #42
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
It seems to me that most of the work to get non-linear easing is already done.
In order to check what is left to be done I removed the linear-only enforcement, created a simple example with 3 key frames and compared the results with lottielab.com editor:

I have found that:
The way I understand it is that while we are moving into position described by next key frame, we still should be using
oandiparameters from the previous one.After changing the
Time::frames_and_weightto use the easing from current key frame, positions seem to match pretty well:What do you think? Is there anything else missing to enable non-linear easing?
Thanks for creating an amazing library!