We would get different opinions about if a parameter must be local or global (unless we decide Salomonically to define all of them as global).
For sure it's an interesting issue to discuss.
Of course global. For me RC is ruined as the productivity tool. Now it just a tool.
By the way, RC 2.7.1 beta is already available. If you want to check what parameters are modified, these are stored in "$.pamodifed" (array of booleans, one for parameter).
ok, that is helpfull I can stop whining and get back to work having maxscript ready:
for obj in selection do obj.pamodified = #(false,false,false)
I will find my way around using scripting, but if my experience and opinion maters anything, now it worse and less intuitive and clear what it is doing then old school way- overwriting everything.
IMO if a parameter is global then it should be a constant in the profile, not a parameter.
It should be global per scene, not per style, don`t confuse the two. In some scenes You want wall height to be 1 meter but other times 2 meters tall. And you want all walls to be the same defined Height.
So no, user should not hardcode that parameter, don't get me started.
My typical workflow:
I create one RC object,- most often put that to my custom library for future use. I make tons of variables to tweak the style.
Later, when I have to use the style (Hundreds of RC objects for hundreds of splines) I load it on one spline and tweak parameters to my liking.
Then I copy style to rest of the splines. And do further adjustments and again copying to all the splines to take effect . But now I cant! (well I can with script mentioned above)