Re: [sc-users] Weird behavior of Clock

[James Harkins <jamshark70@xxxxxx>]

A common solution is just to add nil as the last expression:

SystemClock.sched (1, {
   ... Do stuff that might end with a number...;
   nil
});

One way to help yourself remember to do this is to think that the form of 
every scheduled function is:

{
   The stuff I want to do
   How far in the future should the clock do it again
}

If you don't want it to run again, then a safe answer for the second item 
is 'nil'.

hjh

Sent with AquaMail for Android
http://www.aqua-mail.com





_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/