> We've been talking about 'TEMPO' and
'TRANSPORT' and 'TICKS' and 'METER'
> controls, which (honestly) kind of turns my stomach. This is not what
> controls are meant to be doing. the answer strikes me in shadowy details:
>
> Each host struct has a timeline member. Plugins register with the host for
> notification of ceratin things:
> host->register_time_event(plugin, event, function);
> events:
> TIME_TICKS // call me on every tick edge
> TIME_TRANSPORT // call me when a transport happens
> TIME_METER // call me when the meter changes
this is the best suggestion so far. i love callbacks. note that
"meter" includes both tempo and time signature. you knew that, though.
i can't see anyone wanting to use TIME_TICKS.
--p