Then perhaps it could just be for multiple outlets, and not multiple inlets.<br>
I'm thinking of instances where only one of those messages is going to
be sent on any pass. I do it all the time, often with a [route]
object determining which message is to be sent.<br>
A trigger object wouldn't make much difference with several messages
going to one inlet: the place for the trigger would be before those
several messages. They could still all connect directly from
their outlets.<br>
<br>
-Chuckk<br>
<br>
<br>
Subject: Re: [Pd] Feature request: simultaneous connections<br>
To: <a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:pd-list@iem.at">pd-list@iem.at</a><br>
Message-ID: <<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:20060314170811.GI6454@fliwatut.scifi">20060314170811.GI6454@fliwatut.scifi</a>><br>
Content-Type: text/plain; charset=iso-8859-15<br>
<br>
Hallo,<br>
Joćo Miguel Pais hat gesagt: // Joćo Miguel Pais wrote:<br>
<br>
> >or one outlet to several receivers, or what not.<br>
><br>
> actually max has a nice sollution for that: pressing shift while making a<br>
> connection automatically brings up another cable from the same output. It<br>
> would be good to have something like that on pd as well.<br>
<br>
... and then people will complain that their patches do strange things<br>
because they created fanning-connections with undefined execution<br>
order instead of properly using the trigger-object.<br>
<br>
I don't think it's a good idea to encourage outlet-fanning with a<br>
keyboard shortcut.<br>
<br>
Ciao<br>
--<br>
Frank Barknecht _ ______footils.org_ __goto10.org__<br>