vade

say I have an object in a patcher name "thing". I do know necessarily know how many inlets and outlets "thing" has because "thing" is a patcher module loaded off of disk and could be CRAZY and have like, lots and lots of inlets and outlets.

I would like to query "thing" to know how many inlets and outlets "thing" has.

var thing=this.patcher.getnamed("thing");

what method to thing can I now call to return the number of inlets and outlets?

I checked the docs, so forgive me if ive missed this one.

procedurally-counting-named-objects-inlets-and-outlets

> say I have an object in a patcher name "thing". I do know 

> necessarily know how many inlets and outlets "thing" has because 

> "thing" is a patcher module loaded off of disk and could be CRAZY 

> and have like, lots and lots of inlets and outlets.

> I would like to query "thing" to know how many inlets and outlets 

> var thing=this.patcher.getnamed("thing");

> what method to thing can I now call to return the number of inlets 

> I checked the docs, so forgive me if ive missed this one.

>
> Hello
>
> say I have an object in a patcher name "thing". I do know  
> necessarily know how many inlets and outlets "thing" has because  
> "thing" is a patcher module loaded off of disk and could be CRAZY  
> and have like, lots and lots of inlets and outlets.
>
> I would like to query "thing" to know how many inlets and outlets  
> "thing" has.
>
> How does one do that?
>
> var thing=this.patcher.getnamed("thing");
>
> what method to thing can I now call to return the number of inlets  
> and outlets?
>
> I checked the docs, so forgive me if ive missed this one.


Inlets and Outlets make max go! How can javascript not know about them!

Does javascript in Max 5 know about them? if not, PLEASE !

Oh man, really? Id never in a thousand years think that would be the case.

> Inlets and Outlets make max go! How can javascript not know about 

It's not a that simple problem. For some object, that's *easy* 

because it doesn't change but for some objects it changes on 

instantiation. The worst example is JS, because you have to execute 

the global code of the javascript file before you can know what's the 

> Inlets and Outlets make max go! How can javascript not know about  
> them!

It's not a that simple problem. For some object, that's *easy*  
because it doesn't change but for some objects it changes on  
instantiation. The worst example is JS, because you have to execute  
the global code of the javascript file before you can know what's the  
number of inlet/outlet.

But the js can query itself with the jsthis object and return the number of inlets/outlets.

I only need to poll objects. Jeremy gave me a possible workaround over IM, which I will try to get working and post.

not really a workaround, but a design consideration, which may or may not be useful...instead of lots of inlets/outlets in abstractions/patcher, can you rely on route and label (an Lobject from peter elsea)?

procedurally counting named objects inlets and outlets