Better preset scope handling

[woodslanding]

As mentioned in the patching forum:

If you set a patch's 'saved in preset' OFF, Patch Mangers modules inside the patch stop recalling presets, even from their own numerical input.

This seems needlessly heavy handed. If you don't want the PM to change presets, just don't plug anything into the NUM input! 'Saved in patch' should affect whether PMs of larger scope outside the patch can cause it's data to recall. But the patch should still be able to recall its data internally.

As I mentioned elsewhere, this means that in a global patch change, information will come both from the global PM AND from the local PM, leading to duplicate triggering of VST patch data loading....

This is true even if the PM itself is in a subpatch inside the patch with 'save in preset' enabled, if its scope is set to 'parent patch'.

There is a workaround involving nesting the entire patch in a subpatch, but then you lose the 'loading patch' output from the patch module, which is very helpful for updating gui elements after a patch change.

[senso]

interesting, I'll think about that but I'm not sure to find a real solution.