9 Mar
2004
9 Mar
'04
11:14 a.m.
[Alfons Adriaensen]
On Tue, Mar 09, 2004 at 04:29:55AM +0100, Tim Goetze
wrote:
there still is a difference: unlike MOMENTARY, a TRIGGER port is not
interested in falling edge. by your generalization, you needlessly
force the already mentioned extra logic onto the plugin, and you
coarsen the k-rate resolution for no obvious purpose.
it remains yet to be shown how TRIGGER is detrimental. so far we've
only heard that it can be handled by MOMENTARY if we can live with
some unwanted side effects.
in effect, there are/will be plugins that implement TRIGGER anyway.
forcing them to identify themselves as MOMENTARY only gives rise to
possible misinterpretation, for no good reason.
vriendelijk,
tim
suppose you want to trigger twice, in two
consecutive run() cycles.
you have to 'bring the line down' inbetween to accomplish this if you
only have MOMENTARY, not TRIGGER. how do you do it? you have to split
the first run() cycle into two to bring the line down before you can
bring it up again.
OK, not having TRIGGER halfs the control bandwidth. But if your event
frequency is approaching the control rate or even half of it, you will
run into trouble anyway, as the events will be quantised in time in a
way you'd probably not expect. It just means the k-rate is too low for
the application at hand.