rototiller: introduce ticks and wire up to modules

Most modules find themselves wanting some kind of "t" value increasing
with time or frames rendered.  It's common for them to create and
maintain this variable locally, incrementing it with every frame
rendered.

It may be interesting to introduce a global notion of ticks since
rototiller started, and have all modules derive their "t" value from
this instead of having their own private versions of it.

In future modules and general innovations it seems likely that playing
with time, like jumping it forwards and backwards to achieve some
visual effects, will be desirable.  This isn't applicable to all
modules, but for many their entire visible state is derived from their
"t" value, making them entirely reversible.

This commit doesn't change any modules functionally, it only adds the
plumbing to pull a ticks value down to the modules from the core.

A ticks offset has also been introduced in preparation for supporting
dynamic shifting of the ticks value, though no API is added for doing
so yet.

It also seems likely an API will be needed for disabling the
time-based ticks advancement, with functions for explicitly setting
its value.  If modules are created for incorporating external
sequencers and music coordination, they will almost certainly need to
manage the ticks value explicitly.  When a sequencer jumps
forwards/backwards in the creative process, the module glue
responsible will need to keep ticks synchronized with the
sequencer/editor tool.

Before any of this can happen, we need ticks as a first-class core
thing shared by all modules.

Future commits will have to modify existing modules to use the ticks
appropriately, replacing their bespoke variants.

0 files changed, 0 insertions, 0 deletions