Re: RE: bbcut2 effects set value

On Jul 1, 2008, at 3:39 AM, Fredrik Olofsson wrote:

if you study the many bbcut examples more carefully, you'll see how a function often is used as an argument.  the cutbit1 class is no exception.

so then instead of function {x} below, you can do {slider.value} (and probably you also need a {}.defer around it)

Once you defer the function, its execution becomes asynchronous so the slider value will not be available to the CutBit.

Better to set the slider's action to set an external variable to the new slider value (and probably map the value onto a range other than 0..1 using a ControlSpec), and then refer to the variable instead.

hjh