[PD] [inlet], [outlet].

Josh Steiner joschi at eds.org
Wed May 7 23:16:12 CEST 2003


pix wrote:

>On Tue, 6 May 2003 20:57:09 -0400 (EDT)
>Mathieu Bouchard <matju at sympatico.ca> wrote:
>
>  
>
>>However the big problem with the current [inlet] is that if you have
>>several of them inside a patcher or abstraction, then you cannot
>>position them in a way that the first inlet is to the right of the
>>second inlet, because then both inlets swap roles, which leads to
>>messages coming into and out of the wrong objects.
>>    
>>
> 
>...and you don't think readability would suffer if this was possible?
>after all, the visual order of the [inlet] objects inside the patch
>corresponds to the ordering of the connection points of the object when it
>appears in another patch.
>
>if it were possible to have out-of-order inlets, then for readability they
>should probably be reserved for special cases where it doesn't make sense
>to the the processing in the area of the patch where the inlet object will
>lie. in which case, you could achieve the same thing easily by just
>draping a long patch cable across your patch, or using a send/receive
>pair, to get the data to where the processing will happen.
>
i dont think it would negatively effect readability since if you have an out of order inlet it would have a number specifying which inlet it is:

[inlet 2]  [inlet 1]

-- 
____________________________________________________
independent u.s. drum'n'bass -- http://vitriolix.com








More information about the Pd-list mailing list