I’m not sure I follow you…
I have a patch of objects that are connected to a couple of inlets
and outlets
I want to make this into a subpatch
I select all and choose ‘encapsulate’ from the menu
I am expecting that this will wrap all the selected objects and
inlets outlets into a subpatch and allow me to close the window
so that I’m looking at a subpatch on the parent level
is this not what encapsulate means?

ah I think I follow now: in other words, I select a part of a patch
which is a part of a more complex patch and ‘encapsulate’
then it provides the inlets and outlets to reconnect to where it was
in the parent patch…
not sure this is any clearer than your explanation but I think I got
it…
thanks!
:)

Kim Cascone wrote:
> the patch is encapsulated but the subpatch is connected to
> inlets/outlets on the parent level
> is this a known issue?

Depends what you think the issue is. That it creates annoyingly more
outlets than asked for is a known, but as far as I know ignored issue…
(Still a strong request from my side, along with better placement of ins
and outs within the subpatcher…)

That it doesn’t include the ins and outs is welcome…

If you want it exact, you can cut all, create a new [p mysubpatch] and
paste it…