mzed

My collegue is making an abstraction that dynamically generates its inlets and outlet via scripting. The problem with this approach is that connections to this abstraction are not preserved when you save and reopen.

Our two workarounds are either to use javascript or to have the maximum number of inlets saved as part of the abstractions, script the connections needed and then use script to delete the unnecessary inlets.

Is there a cleaner way to do this? Abstraction and help patch below.

My collegue is making an abstraction that dynamically generates its inlets and outlet via scripting.  The problem with this approach is  that connections to this abstraction are not preserved when you save and reopen.

Is there a cleaner way to do this?  Abstraction and help patch below.

scripting-inlets-and-outlets

i forgot all my previous ideas and patches relying on a dynamic 

inlets/outlets creation via scripting. As you see, too slow 

instanciation to build & connect the inlets/outlets.

And no, there's no cleaner way i know but this workaround about having 

f.e chanfrault | aka | personal computer music

> >>>>>> |sublime music for a desperate people|

i forgot all my previous ideas and patches relying on a dynamic 
inlets/outlets creation via scripting. As you see, too slow 
instanciation to build & connect the inlets/outlets.
And no, there's no cleaner way i know but this workaround about having 
hundred inlets to delete.

f.e chanfrault | aka | personal computer music
> >>>>>> http://www.personal-computer-music.com
> >>>>>> |sublime music for a desperate people|


What about dynamically deleting, creating an connecting your dynamic

What about dynamically deleting, creating an connecting your dynamic
abstraction.

> Our two workarounds are either to use javascript or to have the

> maximum number of inlets saved as part of the abstractions, script

> the connections needed and then use script to delete the unnecessary

Deleting unused ins and outs is what I do with all of my abstractions 

which have varying numbers of them. Ugly, but works...

The only solution would be a change in the behaviour of Max itself by 

creating bogus ins and outs instead of the known error message of 

missing blahblah and cutting the connections.

Yes cycling, if your listening, this would be a feature request which 

would help around some other nasties as well...

(Ever misstyped an object which had been connected before?...)

mzed wrote:
> Our two workarounds are either to use javascript or to have the
> maximum number of inlets saved as part of the abstractions, script
> the connections needed and then use script to delete the unnecessary
> inlets.

Deleting unused ins and outs is what I do with all of my abstractions 
which have varying numbers of them. Ugly, but works...

The only solution would be a change in the behaviour of Max itself by 
creating bogus ins and outs instead of the known error message of 
missing blahblah and cutting the connections.

Yes cycling, if your listening, this would be a feature request which 
would help around some other nasties as well...
(Ever misstyped an object which had been connected before?...)

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


scripting inlets and outlets