Re: [sc-users] SystemClock-schedAbs explodes when time arg not used?

[James Harkins <jamshark70@xxxxxxxxx>]

On Sep 22, 2005, at 11:37 AM, Charlls Quarra wrote:

> wow, this is definitely interesting and IMO
> non-trivial to find out, thanks James. This definitely
> should be a candidate for insertion in a
> quirks-and-mirks-in-SC3 help file

Note that this is amply documented in the SystemClock helpfile:

*sched(delta,task)
	the float you return specifies the delta to resched the function for
<x-tad-smaller>
</x-tad-smaller><x-tad-smaller>		SystemClock</x-tad-smaller><x-tad-smaller>.sched(0.0,{ arg time;  
time.postln; 
rrand(0.1,0.9) 
});

</x-tad-smaller>	returning nil will stop the task from being rescheduled
<x-tad-smaller>
</x-tad-smaller><x-tad-smaller>		SystemClock</x-tad-smaller><x-tad-smaller>.sched(2.0,{ 
</x-tad-smaller><x-tad-smaller>"2.0 seconds later"</x-tad-smaller><x-tad-smaller>.postln; 
</x-tad-smaller><x-tad-smaller>nil</x-tad-smaller><x-tad-smaller> 
});
</x-tad-smaller>
hjh

: H. James Harkins
: jamshark70@xxxxxxxxxxxxxxxxx
: http://www.dewdrop-world.net
.::!:.:.......:.::........:..!.::.::...:..:...:.:.:.:..:

"Come said the Muse,
Sing me a song no poet has yet chanted,
Sing me the universal."  -- Whitman