<div dir="ltr">If it's possible to figure out programmatically what parameters are in their default settings and what have been modified, then upon updating a node type definition you could leave any modified parameters as-is and update parameters that were previously at the default, to the new default. Houdini acts like this, and it works pretty well.<br>
<div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 11, 2013 at 11:26 PM, Lukas Tönne <span dir="ltr"><<a href="mailto:lukas.toenne@gmail.com" target="_blank">lukas.toenne@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> But how about adding an explicit "reset to defaults" button? That way<br>
> one could quickly test the OSL parameter defaults without destroying a<br>
> carefully set up scene.<br>
<br>
</div>One more thought: In the long run the OSL parameter defaults should be<br>
translated to RNA property defaults (that currently does not work due<br>
to the generic socket properties). When that is implemented the "reset<br>
to defaults" button could be a general feature for all nodes, just as<br>
a shortcut so users don't have to reset each socket value<br>
individually.</blockquote></div></div></div>