bugreport: pv is still connected after encapsulating

Oct 8, 2006 at 4:05pm

bugreport: pv is still connected after encapsulating

Hi, only a minor thing.

Steps to reproduce are in the patch.

Expected behaviour: after encapsulating the pv, it should no longer be available to the subpatcher.

Max 4.5.7, Windows XP

#P window setfont “Sans Serif” 9.;
#P window linecount 3;
#P comment 98 134 198 9109513 3) change the numbox in your new patcher and press the bang in patcher sub. The changed number will still be printed.;
#P window linecount 2;
#P comment 98 93 198 9109513 2) encapsulate the objects within the grey panel;
#P window linecount 1;
#N vpatcher 27 447 131 569;
#P window setfont “Sans Serif” 9.;
#P newex 11 72 26 9109513 print;
#P button 11 31 15 0;
#P newex 11 50 42 9109513 pv thing;
#P connect 1 0 0 0;
#P connect 0 0 2 0;
#P pop 1;
#P newobj 30 147 31 9109513 p sub;
#P window linecount 3;
#P comment 98 40 198 9109513 1) change the numbox and press the bang in patcher sub. The changed number will be printed.;
#P number 24 39 35 9 0 0 0 139 0 0 0 221 221 221 222 222 222 0 0 0;
#P window linecount 1;
#P newex 24 57 42 9109513 pv thing;
#P window linecount 2;
#P comment 19 82 55 9109513 encapsulate this;
#P user panel 17 31 59 82;
#X brgb 191 191 191;
#X frgb 0 0 0;
#X border 1;
#X rounded 0;
#X shadow 0;
#X done;
#P connect 3 0 2 0;
#P window clipboard copycount 8;

Cheers,
Mattijs

#28037
Oct 8, 2006 at 4:46pm

#85653
Oct 8, 2006 at 10:47pm

Nice one ;P

#85654
Oct 9, 2006 at 7:47am

Mattijs Kneppers wrote:
> Hi, only a minor thing.
>
> Steps to reproduce are in the patch.
>
> Expected behaviour: after encapsulating the pv, it should no longer
> be available to the subpatcher.

No bug, the [patcher] does only encapsulate visually, all the contents
of [p sub] are still belonging to the local patch. This has been around
since the beginning of Max and is intentional. (#x arguments can be
encapsulated that way…)

If you want it seperated, you need to save the subpatcher as a seperate
file…

Stefan


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

#85655
Oct 9, 2006 at 9:02am

Looks like a bug to me. Try opening his patch once more, encapsulate,
and confirm that the objects are still linked. Now copy all of the patch
(post encapsulation), past into a new empty window and test there. Now
you will see that the two pvars are no longer linked.

I suppose that this is a bug that shows up when encapsulating. If you
sare the patch, close it and open again, the two pvar instances will
behave properly again, no longer being linked.

Best,
Trond

Stefan Tiedje wrote:
> Mattijs Kneppers wrote:
>> Hi, only a minor thing.
>>
>> Steps to reproduce are in the patch.
>>
>> Expected behaviour: after encapsulating the pv, it should no longer
>> be available to the subpatcher.
>
> No bug, the [patcher] does only encapsulate visually, all the contents
> of [p sub] are still belonging to the local patch. This has been
> around since the beginning of Max and is intentional. (#x arguments
> can be encapsulated that way…)
>
> If you want it seperated, you need to save the subpatcher as a
> seperate file…
>
> Stefan
>

#85656
Oct 9, 2006 at 9:18am

Me too.

jb

Am 09.10.2006 um 11:02 schrieb Trond Lossius:

> Looks like a bug to me.

#85657

You must be logged in to reply to this topic.