Re: [PD-dev] timing of a clock_delay(x->x_clock, 0);

2006-12-30 Thread Miller Puckette
That would be an error (silently 'corrected' to delay zero). On Sat, Dec 30, 2006 at 03:12:19PM -0500, Mathieu Bouchard wrote: > On Thu, 28 Dec 2006, Miller Puckette wrote: > > >It's indeed "as soon as possible", except that if someone else has > >previously > >scheduled something ASAP that ASAP

Re: [PD-dev] timing of a clock_delay(x->x_clock, 0);

2006-12-30 Thread Mathieu Bouchard
On Thu, 28 Dec 2006, Miller Puckette wrote: It's indeed "as soon as possible", except that if someone else has previously scheduled something ASAP that ASAP will get in earlier than yours. You can chain arbitrarily many clock_delay(..., 0) calls without DSP or event polling getting in between.

Re: [PD-dev] show-stopping bug for Windows release

2006-12-30 Thread Mathieu Bouchard
On Sat, 30 Dec 2006, Hans-Christoph Steiner wrote: http://sourceforge.net/tracker/index.php?func=detail&aid=1595028&group_id=55736&atid=478070 This cyclone bug is still outstanding, its very strange. The object boxes change to message and number boxes. I would really like to have it resolved

[PD-dev] show-stopping bug for Windows release

2006-12-30 Thread Hans-Christoph Steiner
http://sourceforge.net/tracker/index.php? func=detail&aid=1595028&group_id=55736&atid=478070 This cyclone bug is still outstanding, its very strange. The object boxes change to message and number boxes. I would really like to have it resolved for the release. Can any windows people shed