Ploki

So, you can use a patcher as an abstraction if its in your root folder of the parent project.

However, if you want to use it in a sub patcher of the parent patcher, it won't work.

Technically, it just works if its on the top of the root patcher.

Is that a bug or is it suppose to work like that?

I personally find it easier to just use patcher specific abstractions as a part of main patcher projects rather than something permanently in max path (i like to keep my max paths fairly free of clutter)

So, you can use a patcher as an abstraction if its in your root folder of the parent project.
However, if you want to use it in a sub patcher of the parent patcher, it won't work.
Technically, it just works if its on the top of the root patcher.

I personally find it easier to just use patcher specific abstractions as a part of main patcher projects rather than something permanently in max path (i like to keep my max paths fairly free of clutter)


patcher-as-abstraction-in-root-folder-of-parent-patcher

The abstraction-must-be-in-top-level-folder-of-the-main-patch is something that has been plaguing us almost as long as Max has been in existence.

The principal way to avoid this is to include the folder with your abstractions in the search path. Or include the folder with your top-level patch in your search path. Search path folders are searched recursively. The folder with your main patch is not searched recursively (unless it's explicitly included in the search path).

This idiosyncrasy has driven many a grown Max/MSP programmer to tears. But that's the way it is.

patcher as abstraction (in root folder of parent patcher)