Implementing getAt() functions

[Ballasi]

This feature would open for a lot of possibilities, especially for a custom-made design tab. This is probably one of the most interesting features of osb that I'd love to see work. I had some bare-bones done in storygen but it wasn't fully secure and there were edge cases that made it break. I'm sure using IntervalMaps would help.

[DoomDuck]

Which getAt() function are you talking about ? And what would it do ?

[Ballasi]

I think I quickly brought that to you when we talked about it, that's the whole reason of implementing IntervalMaps in the first place.
In the .osb format, there are many types of events, such as Move, Fade, Scale, ...
The getAt(timestamp) call of the Move events of a sprite will return the sprite's position value at a certain timestamp basically.
When we have IntervalMaps done, it's a matter of calling the interval maps's get, and doing an easing call if necessary (e.g. we have a fade from the timestamp 100ms and 300ms and we want to have its value at 200ms, we have to calculate the value at that precise moment), which this second part is already implemented.