Hi list,
Short background for developers: A while ago, I fixed a bug in the
switch-based operators, involving inconsistent results of the
#is_ready method during the same time tick. Recently, I came across a
similar bug, and I noticed that switch() had its own #is_ready because
of its particular "strict" parameter, hence it does not benefit of the
fix that I did in the base class.
My question to both developers and users is: does anybody use or see
any use of this strict parameter ? If not, I'm gonna remove it instead
of struggling for this weird feature.
The initial motivation of "strict" was to add() to some source a
switch(strict=true,{0m-0m2s},sine()). The strict there made the whole
thing unavailable as soon as the interval 0m-0m2s gets invalidated, so
that the beep only lasts 2 seconds at the beginning of every hour.
This can also be done without strict, by using the single parameter
and adding a track duration of 2s to the sine().
Seeing the current implementation of "strict", I doubt that it has
been successfully used for any different example. Am I right ? Did
anybody ever felt the need for a correct implementation of strict ?
Cheers.
--
David
