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…

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
>