On Dec 29, 2009, at 9:13 AM, Julian Rohrhuber wrote:
I don't know why this is happening, but this illuminates: ( [TempoClock.beats, TempoClock.seconds].postln; r = Routine { 2.do { [thisThread.clock.beats, thisThread.clock.seconds].postln; 1.0.wait; }; }.play; ) [ 349.801915797, 1142.84573005 ] a Routine [ 1142.84573005, 1142.84573005 ] [ 350.801915797, 1143.84573005 ] (correct) (fail) So it seems, the first thing to happen in a routine receives the clock's seconds, when it should get beats. After that, it gets the proper thread time. I think this must be screwed up in c++ somewhere. I haven't the foggiest where to look. hjh : H. James Harkins .::!:.:.......:.::........:..!.::.::...:..:...:.:.:.:..: "Come said the Muse, Sing me a song no poet has yet chanted, Sing me the universal." -- Whitman |