| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
I realized that RlfAnimations don't use B-frames, therefore, can not easily go backwards.
|
|
If an animation is 'mirrored', it doesn't have B-frames, only I-frames. However the animations are built
so the last half of the animation is the reverse of the first half
|
|
|
|
Because y increases as you go down, not up
|
|
|
|
|
|
|
|
|
|
|
|
Instead, pass all mouse events to ScriptManager
|
|
This allows the main engine to pass mouse events to Controls
|
|
iterate over _activeControls
We also change _activeControls to a List instead of a HashMap because a List should have
slightly better iteration time.
|
|
Control syntax
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This makes memory management a lot easier as well as removes the need for
multiple lists that point to the same objects. However, there will be quite a few Controls
that don't need all the functionality of ActionNode and MouseEvent, so the default
implementations are No Op.
|
|
|
|
|
|
|
|
go negative
|
|
|
|
|
|
|
|
|
|
We no longer use SharedPtr
|
|
|
|
using getFrameData()
|
|
|
|
|
|
|
|
|
|
methods internally.
Rather than creating an instance of MouseEvent and passing argument around.
|
|
every process()
|
|
|
|
|
|
SharedPtrs
|
|
|
|
|
|
The code was moved to the class PushToggleControl
|
|
Some Puzzles don't have flags, which caused it to never be initialized
|
|
|
|
|
|
This allows List::push_back() to not cause a data copy
|
|
|
