[PD-dev] preserving connections of 'bogus' objects

[pix]

this reminds me of a feature which i have long thought would be useful,
and that fits well with the (not so) new connection-selecting behaviour.

it would be nice if there was a key which would "intersect" an existing
connection, and replace it with a pass-through object (either
[inlet~]->[outlet~] or [inlet]->[outlet]). this object could be later
edited into something else, in order to live-edit a patch without having
to disconnect/reconnect objects. 

for example:

[osc~ 100] -> [dac~]

select, the connection, hit the intersect button, and it becomes

[osc~ 100] -> [nop~] -> [dac~]

then the nop object could be edited into something useful, potentially
with no interruption to audio:

[osc~ 100] -> [*~ 1] -> [dac~]

then a number box could be patched into the second inlet of the *~ object,
and you have added volume control without having to stop the patch.

is this too wacky?

pix. 

On Tue, 16 Sep 2003 09:11:26 -0700
Miller Puckette <mpuckett at man104-1.ucsd.edu> wrote:

> I agree... I'll do this for 0.38... I actually write that feature of
> jMax but haven't got around to re-introducing it.
> 
> cheers
> Miller
> 
> On Tue, Sep 16, 2003 at 11:45:04AM -0400, Mathieu Bouchard wrote:
> > 
> > On Tue, 16 Sep 2003, Krzysztof Czaja wrote:
> > 
> > > What I have in mind, is that during object creation, when the
> > > requested class is not known, and there is no matching abstraction,
> > > a`failsafe' replacement object is used.  Currently in Pd, it has
> > > never any inlets nor outlets, even if loaded from a patch with the
> > > original object connected.  (A slightly different case, and
> > > apparently easier to deal with, is an already patched up object,
> > > edited into a``couldn't create'' nop by the user.)
> > > 
> > > Currently in Max, such creatures, called `bogus' objects, do
> > > preserve connections.
> > 
> > This is also a feature of jMax, which draws such objects in lightgray
> > instead of white. That this feature is not present is a bit of an
> > annoyance. It makes it not very much possible to look at a patch just
> > for looking at it, without having the external.
> > 
> > This would be important to look at example patches for an external
> > that is not installed yet, as a preview of what the external would be
> > used and such. Well I don't know if many people do that, but sometimes
> > I happen to.
> > 
> > Another possibly more important problem is when you change an object
> > at runtime and make a mistake and then the object loses all its
> > inlets/outlets and all associated connections (!). At least now
> > there's Ctrl+Z that makes it less of a problem.
> > 
> > ________________________________________________________________
> > Mathieu Bouchard                       http://artengine.ca/matju
> > 
> > 
> > _______________________________________________
> > PD-dev mailing list
> > PD-dev at iem.at
> > http://iem.at/cgi-bin/mailman/listinfo/pd-dev
> 
> _______________________________________________
> PD-dev mailing list
> PD-dev at iem.at
> http://iem.at/cgi-bin/mailman/listinfo/pd-dev