I’m having trouble with Max5 as it differs from Max4 wrt pcontrol closing
I’d been using this method to tidy up these patchers at open time
[loadmess close] into [pcontrol] worked just fine
Since migrating same patch to Max5 i’ve been getting a ‘wclose error… invalid object’
however, this can be established simply by looking at the pcontrol help file – (compare max5.05 with max4.6 !)
create an empty patch – place pcontrol object – look at the help file
now, click close (before you click open!!!)
this worked without error in max 4
but in Max5 gives an error/warning
it won’t give an error after you click open, even after repeated close clicks – however, at launch when you want to ensure that the patcher is not opened irrespective of the state at save – it gives this annoying error
sure i can ignore it, but is this difference between 4 and 5 intentional ???
You are right that the files/subpatchers open up because they were open when I saved the file at some stage.
Problem is that closing the subpatchers before saving the main patch the next time doesn’t work (tried on pc and mac). Which results in more and more clutter as the number of subpatchers being opened automatically is increasing but never going down.
I looked into pcontrol, but as one has to link pcontrol to all subpatchers to be controlled, that seems to be quite an effort. There is no inheritance, that means closing a subpatcher on level 2 doesn’t mean that included subpatchers in level 3 are closed automatically.
if my structure is like this (main patch –> L2 subpatch –> L3 subpatch), then in my case, opening the main patch opens a lot of L3 and L4 subpatches. Now, sending "pcontrol close" to the L2 subpatch doesn’t close the L3 subpatchers.