Perhaps you could add some code in the init callback of the property to auto-generate the new property? I've done something sort of similar for making custom properties that can "upgrade" themselves to the latest definitions by checking a "version" parameter's value and seeing if it's out of date. Of course, in that case I'm just storing all the parameter values in a dictionary, deleting them, recreating the params, and setting all the values. A little different than creating a whole new property.
It's not that different from just doing it with a standalone script I suppose, but maybe it's somehow helpful for you? On Tue, Jun 18, 2013 at 7:00 AM, Stephen Blair <stephenrbl...@gmail.com> wrote: > On 18/06/2013 9:29 AM, Alan Fregtman wrote: >> >> >> What I was after was if there was some secret way of changing a >> customproperty type since fundamentally they're just parameters, but no, I >> have to mass-copy parameters (via scripting, yes) to a new property. >> >> > Nope, no secret way to change the type [that I could find]. > > Scavenge the addparameter code from the original plugin and use that to > create the non-self-installed version of the property, and then use > BinaryData to copy over the parameter values?
