Hi, Joco Miguel Pais hat gesagt: // Joco Miguel Pais wrote:
Is it possible to eliminate the feature by which the order of the output messages (when one point has several outputs) are sent? This can be useful in the beggining, but in the next day (or hour) one does not remember already the output order, and can lead to some very annoying problems. Maybe it is preferible to use trigger and everything is clear the next time the patch is opened, as to the current situation. (or in other words, to work as in max) (if this is not clear, it is the feature explained in file 03.connections.pd)
Actually, even looking at this patch again didn't make it clear to me, what you mean. Currently, the order of messages, when one outlet is connected to more than one inlet, is not defined. One can not know or be sure of this order. If you need to be sure, you need a trigger object.
Another question: is there any kind of multi-line object - a line that accepts more than one segment? (like csound's linseg) In the libraries I have here (the main ones) couldn't find any.
I like the t3_line~ object from IEM's t3_lib. It has the advantage, that you can make line segments faster that the 64-sample max message speed.
I used it in my angriff~ drummer, and I'm working on a PD-Howto, where this is explained in detail. I could post the relevant part, if you're interested.
question 3: is there any kind of dial object, but which allows more than one square to be active? Or the choice is to put several toggles in pilled up?
I think, you will have to use lots of toggles. But you could put them in graph on parent abstractions, so they can be reused. With a little pd-internal-messages-magic, they might even be resizable. Would be an interesting project...
ciao
Frank Barknecht _ ______footils.org__