@Mathias_Westerdahl yes I was afraid of this. But I thought the property was set by Lua code in the end. Maybe by inserting a function call there if Lua code is called anyway would not be a great deal. If C is setting the new value in the game object then I understand. Maybe we could have a go.fanimate function in pure Lua that would be less performant but include the post processing function as part of its signature. I don’t know. Perhaps C and Lua talk overhead would not be that penalizing too. We can measure! Food for thoughts!
@AGulev @aglitchman I don’t think this is what I am after - easing. I know we can use a table or map (which is just another word for function) as the easing function. What I look for is use any easing function with/in addition to the post processing function. This means that if my post processing function moves an object on a circular motion around in the screen, I would want any easing method applied to that so that, for example, the object would ease in (or out, or any of the many easing methods) on that circular path that I define. This decouples the easing from the “motion” code.