Is there a way to create a closed subpatcher using javascript?

I have managed to create a subpatcher and put some stuff inside. Great. But when I run my javascript what I get is an open patcher with a bunch of stuff inside. I don't want to see any of this stuff (which is why I decided to stick it in a subpatcher in the first place) and would like the patcher to be created in a closed state.

I've spent some time scouring the forum but not found an answer to this yet.

As a workaround I am using javascript to create a dummy inlet in the subpatcher, a pcontrol in the parent and sending a close message to the subpatcher via pcontrol just after it is created. It works ok but the subpatcher window flashes on screen for a moment then disappears - a bit of a messy solution - and not ideal.

My workaround code goes something like this:

pcontrol = p.newdefault(100,50, "pcontrol");

subp = p.newdefault(100,100, "p", "patcherName"); 

var pp = p.getnamed("subp1").subpatcher();

dummyinlet = pp.newdefault(50,50,"inlet");

Any ideas/suggestions greatfully received!

Is there a way to create a closed subpatcher using javascript?  

I have managed to create a subpatcher and put some stuff inside. Great. But when I run my javascript what I get is an open patcher with a bunch of stuff inside.  I don't want to see any of this stuff (which is why I decided to stick it in a subpatcher in the first place) and would like the patcher to be created in a closed state.

I've spent some time scouring the forum but not found an answer to this yet.  

As a workaround I am using javascript to create a dummy inlet in the subpatcher, a pcontrol in the parent and sending a close message to the subpatcher via pcontrol just after it is created.  It works ok but the subpatcher window flashes on screen for a moment then disappears - a bit of a messy solution - and not ideal.

p=this.patcher;
pcontrol = p.newdefault(100,50, "pcontrol");
subp = p.newdefault(100,100, "p", "patcherName"); 
subp.varname = "subp1";
var pp = p.getnamed("subp1").subpatcher();

//Now do stuff within sub-patcher...
dummyinlet = pp.newdefault(50,50,"inlet");                      

p.connect(pcontrol,0,subp,0);
pcontrol.close(1);

any-way-to-create-a-closed-subpatcher

On 3 juin 08, at 17:39, David Skulina wrote:

> Is there a way to create a closed subpatcher using javascript?

> I have managed to create a subpatcher and put some stuff inside. 

> Great. But when I run my javascript what I get is an open patcher 

> with a bunch of stuff inside. I don't want to see any of this stuff 

> (which is why I decided to stick it in a subpatcher in the first 

> place) and would like the patcher to be created in a closed state.

> I've spent some time scouring the forum but not found an answer to 

> As a workaround I am using javascript to create a dummy inlet in the 

> subpatcher, a pcontrol in the parent and sending a close message to 

> the subpatcher via pcontrol just after it is created. It works ok 

> but the subpatcher window flashes on screen for a moment then 

> disappears - a bit of a messy solution - and not ideal.

You can send the wclose message to thispatcher directly:

    subp = p.newdefault(100,100, "p", "patcherName");

    var pp = p.getnamed("subp1").subpatcher();

    pp.message("wclose");    // send the command to close the subpatcher

> Hi,
>
> Is there a way to create a closed subpatcher using javascript?
>
> I have managed to create a subpatcher and put some stuff inside.  
> Great. But when I run my javascript what I get is an open patcher  
> with a bunch of stuff inside.  I don't want to see any of this stuff  
> (which is why I decided to stick it in a subpatcher in the first  
> place) and would like the patcher to be created in a closed state.
>
> I've spent some time scouring the forum but not found an answer to  
> this yet.
>
> As a workaround I am using javascript to create a dummy inlet in the  
> subpatcher, a pcontrol in the parent and sending a close message to  
> the subpatcher via pcontrol just after it is created.  It works ok  
> but the subpatcher window flashes on screen for a moment then  
> disappears - a bit of a messy solution - and not ideal.

	p=this.patcher;
	subp = p.newdefault(100,100, "p", "patcherName");
	subp.varname = "subp1";
	var pp = p.getnamed("subp1").subpatcher();
	pp.message("wclose");	// send the command to close the subpatcher

Centre de Recherches et de Formation Musicales de Wallonie asbl

>
> Hi,
>
> Is there a way to create a closed subpatcher using javascript?

can't you set to 0
this.patcher.wind.visible
or use
this.patcher.wind.sendtoback()  ?

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl
http://www.crfmw.be/max


Considerably more concise than my workaround!

However - the subpatcher still flashes on screen, but it runs faster, and with less code - altogether a better solution.

Considerably more concise than my workaround!  

I can't seem to get this to work - I get error messages such as "pp.wind.visible is not a function" when I try to apply it to the subpatcher.

- to the code after the p.getnamed bit, instead of all the pcontrol stuff.

I can't seem to get this to work - I get error messages such as "pp.wind.visible is not a function" when I try to apply it to the subpatcher.  

On 03-juin-08, at 18:37, David Skulina wrote:

> I can't seem to get this to work - I get error messages such as 

> "pp.wind.visible is not a function" when I try to apply it to the 

still can't test myself, but can't you just do this:

>
> Thanks for the response.
>
> I can't seem to get this to work - I get error messages such as 
> "pp.wind.visible is not a function" when I try to apply it to the 
> subpatcher.

any way to create a closed subpatcher?