the order is declared to be *undefined*, not ``as created''.
Thanks Krzysztof for saying this clearly, I had a hard time reading through this thread of misinformation and confusion.
As to the inlet number argument: -) AFAIK there is already an argument for inlets, which is used for resampling, hence the implementation would cause a change in functionality and all the patches that use resampling would probably be broken.
-) Personally I would prefer the unnumbered inlets, I think the "one object that creates several inlets" idea would be a nice alternative to Mathieu's proposal.
-) trigger is not a kludge, if it has a bug, you are free to send a patch.
Greetings,
Guenter
On Wed, 7 May 2003, Krzysztof Czaja wrote:
hi Thomas, marius...
The ``as created'' order should be regarded as a mere implementation detail, which may be changed in any future Pd release (as already had been once in the past, afaik).
I would not agree that the original (i.e. the max) way is any 'better'. Max patch may be broken just by someone moving an object (a sink) on screen.
rsKzytfzo
Thomas Grill wrote:
(and please no change to the order of messages from "in_the
_order_created"
...
To my mind it's extremely important to see (in which way ever) instantly how the order is. In this sense i would really like to have the Max style also for PD.
PD-list mailing list PD-list@iem.kug.ac.at http://iem.kug.ac.at/cgi-bin/mailman/listinfo/pd-list