wippen

I think I've checked everything, but can't find the solution:

How can I stop subpatcher windows from opening automatically when the main patch is opened? 

This is particularly hassling when working with polys which contain subpatchers. I assume that there must be an option covering this, but I can't find it. Thanks for any advice.

How can I stop subpatcher windows from opening automatically when the main patch is opened?  
This is particularly hassling when working with polys which contain subpatchers.  I assume that there must be an option covering this, but I can't find it.  Thanks for any advice.


suppressing-subpatcher-windows

I've experienced this before too. Closing all subpatches and resaving the patch usually fixes this.

---------- Original Message ----------------------------------

>I think I've checked everything, but can't find the solution:

>How can I stop subpatcher windows from opening automatically when the main patch is opened? 

>This is particularly hassling when working with polys which contain subpatchers. I assume that there must be an option covering this, but I can't find it. Thanks for any advice.

Need personalized email and website? Look no further. It's easy

with Doteasy $0 Web Hosting! Learn more at www.doteasy.com

---------- Original Message ----------------------------------
From: Dayton 
Date:  Mon, 30 Apr 2007 09:29:37 -0600

>
>I think I've checked everything, but can't find the solution:
>
>How can I stop subpatcher windows from opening automatically when the main patch is opened?  
>This is particularly hassling when working with polys which contain subpatchers.  I assume that there must be an option covering this, but I can't find it.  Thanks for any advice.
>

Need personalized email and website? Look no further. It's easy
with Doteasy $0 Web Hosting! Learn more at www.doteasy.com


[sorry for the two threads; the result of the famous "error: please press refresh" page]

Yes, closing all subpatchers beforehand will solve the problem, although I had expected that there is an option to do this for us. Every once in a while, I have a patcher open which contains a poly with many instances, I edit the original, save it, and spend the next twenty seconds closing subpatcher windows.

Just for the record, here is one example of the problem:

Yes, closing all subpatchers beforehand will solve the problem, although I had expected that there is an option to do this for us. Every once in a while, I have a patcher open which contains a poly with many instances, I edit the original, save it, and spend the next twenty seconds closing subpatcher windows. 

Amen to that, it seems not always rock solid with the automatic opening of multiple subpatchers, though *usually* the resave seems to be OK.

Along those lines, wondering why some kind of pcontrol-style solution for open/close isn't available for subpatchers (unless there is that I don't know about, please enlighten)... not that double-clicking is so bad, but assigning the open/close to keystrokes would be nice.

I don't think it's bad that which windows an abstraction opens depends on how you save the patch. An option would be nice though.. Maybe an argument to poly~?

I have this too, often. But instead of closing all windows of all instances, you can also re-open the original, close all windows and save.

Quote: Dayton wrote on Mon, 30 April 2007 18:31

----------------------------------------------------

> [sorry for the two threads; the result of the famous "error: please press refresh" page]

> Yes, closing all subpatchers beforehand will solve the problem, although I had expected that there is an option to do this for us. Every once in a while, I have a patcher open which contains a poly with many instances, I edit the original, save it, and spend the next twenty seconds closing subpatcher windows. 

> Just for the record, here is one example of the problem:

> #P number 31 182 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 97 108 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 31 108 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P newex 31 137 76 9109513 poly~ testpoly 2;

> #P comment 166 54 382 9109513 I can't give a complete description of the problem , but here is one example: If I have this patcher open , and then open "testpoly" to edit it , each subpatcher in each instance of the poly opens automatically when 1. it contains an [outlet] 2. is left open in the parent (original) patcher used in the [poly];

> #P comment 66 43 367 9109513 If the parent patcher for this subpatch is the patcher contained in a [Poly] , then every time I save the parent patcher at the same time as having a patcher open which contains a [poly] with the parent patcher , all instances of the subpatcher open as well. This only occurs when there is an outlet within the subpatcher , and the subpatcher window is open.;

> #P newobj 161 95 67 9109513 p subpatcher1;

> #P number 64 178 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 81 96 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

> #P number 45 96 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;

I don't think it's bad that which windows an abstraction opens depends on how you save the patch. An option would be nice though.. Maybe an argument to poly~? 

Quote: Dayton wrote on Mon, 30 April 2007 18:31
----------------------------------------------------
> [sorry for the two threads; the result of the famous "error: please press refresh" page]
>
> Yes, closing all subpatchers beforehand will solve the problem, although I had expected that there is an option to do this for us. Every once in a while, I have a patcher open which contains a poly with many instances, I edit the original, save it, and spend the next twenty seconds closing subpatcher windows. 
>
>
>
> Just for the record, here is one example of the problem:
>
> (the patch containing the poly)
>
> #P window setfont "Sans Serif" 9.;
> #P number 31 182 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P number 97 108 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P number 31 108 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P window linecount 1;
> #P newex 31 137 76 9109513 poly~ testpoly 2;
> #P window linecount 6;
> #P comment 166 54 382 9109513 I can't give a complete description of the problem , but here is one example: If I have this patcher open , and then open "testpoly" to edit it , each subpatcher in each instance of the poly opens automatically when 1. it contains an [outlet] 2. is left open in the parent (original) patcher used in the [poly];
> #P connect 2 0 1 0;
> #P connect 1 0 4 0;
> #P connect 3 0 1 1;
> #P window clipboard copycount 5;
>
>
>
> (the poly)
> #P window setfont "Sans Serif" 9.;
> #P window linecount 1;
> #N vpatcher -40 89 560 489;
> #P outlet 19 145 15 0;
> #P window setfont "Sans Serif" 9.;
> #P comment 66 43 367 9109513 If the parent patcher for this subpatch is the patcher contained in a [Poly] , then every time I save the parent patcher at the same time as having a patcher open which contains a [poly] with the parent patcher , all instances of the subpatcher open as well. This only occurs when there is an outlet within the subpatcher , and the subpatcher window is open.;
> #P pop;
> #P newobj 161 95 67 9109513 p subpatcher1;
> #N out 1;
> #P newobj 64 259 29 9109513 out 1;
> #N in 2;
> #P newobj 81 49 23 9109513 in 2;
> #N in 1;
> #P newobj 45 49 23 9109513 in 1;
> #P number 64 178 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P number 81 96 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P number 45 96 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
> #P newex 64 139 27 9109513 + 1;
> #P connect 2 0 0 1;
> #P fasten 5 0 2 0 86 74 86 74;
> #P connect 3 0 6 0;
> #P connect 0 0 3 0;
> #P fasten 1 0 0 0 50 127 69 127;
> #P fasten 4 0 1 0 50 76 50 76;
> #P window clipboard copycount 8;
>
----------------------------------------------------


yes, I am truly a moron sometimes. didn't see it in the subpatch help file so I thought it was only doable with abstractions.

suppressing subpatcher windows