I'm not sure what you're talking about. Something like 95% of the UI objects already store their attributes (so there's no need of freezing them). Non-UI object works differently because you can also type the name of the attributes as argument which therefore might conflict with what you freeze in the inspector. So if you have an example feel free to post it.
Okay ej. There is no patch to provide, but imagine I change the camera position for the render, in my scene.
Now I close my patch ... OOoops my settings are lost because I did not freeze the param.
An easy way would be:
[closebang] -> "; max freezeallattr"
this example is with one param, but as you know we deal with tens.
It is really boring to reach each @ one by one in the inspector, and there is no more shortcut to freeze a selected one (would be another feature: select in the inspector then freeze without mouse).
I don't make a confusion between typing the attr inside the object and reach it in the inspector, I'm only speaking here about working with the inspector exclusively.
"OOoops my settings are lost because I did not freeze the param."
In this case you would better store it in the patch. If you change it with a named number box, throw an autopattr into the patch and all is saved...
Its a different way of thinking. It is way easier to think in parameters to a patch than in attributes to objects in a patch...
It might be time to think about easy preset handling in general...