I am quite fond of the @autorestore 1 feature of [autopattr] (enabled by default). With patches that don't require multiple presets, I typically just drop in an [autopattr @autoname 1] so that my recent parameters are automatically saved without dealing with writing/read files and recalling presets.
I've found that this functionality does not work with abstractions in a patch. If I have a patch with abstractions or bpatchers (containing their own autopattrs), autopattr will only autorestore the values of the objects in the main patch, ignoring the objects in the abstractions. Adding @greedy 1 or @dirty 1 does not help. Adding @autorestore 0 to the autopattrs in the abstractions does not help.
When I create a named autopattr and look at the storagewindow with a likewise named pattrstorage object, I can see the values of the objects in the abstractions...
...how can I make autopattr reach into abstractions and change their values like pattrstorage does when you recall a preset? I know it's 'seeing' them, but it doesn't effect them.
One particular application for this is the following: I have a bpatcher which is a GUI frontend to pattrstorage, exposing all of its messages in a nice way. I would like for some of the parameters of this bpatcher to be automatically set to their last values when I open a patch. There seems to be no way to do this except for to create yet another pattrstorage to recall the parameters of the pattrstorage GUI object!