This app is great! Now that I'm using it a lot I've noticed if you have spare parms on a subnet and then create the hda all those spare parms don't get carried into the hda, compared to the standard create digital asset dialog which preserves any subnet spare parmaters and any callback expressions on them. It would be great to have this in there when blocking what eventually becomes an hda from a subnet with spare parms.

I've been bit by this a couple of times where the parms are there when creating it in place, but dropping a new instance has no parms and the hda breaks functionality. I have to then 'Export Parameter to Type Properties' on each spare parm and have to go back and insert any callback expressions which is a pain and can be avoided.

Not sure if this would be a sesi rfe or if there is a different place to submit labs rfes.. can't seem to find this in the Labs source to try and modify.

Hmm, one other thing comes to mind.

I really like how when I major/minor version up, the versioned up hda becomes the current definition.

This is usually what you want to happen when deploying (say updating your environment) so new instances that are dropped in use the newer version.

Is there a way that this can be managed? say if I have a 3.5 and I want to do a major version up, but not have 4.0 become the current definition. Can a toggle be added to do that?

Is there a way to do that now? ie Digital Asset > Save As.. with dev toggle?
then save as again without the dev toggle, and specifying the specific version?

sdugaro
Not sure if this would be a sesi rfe or if there is a different place to submit labs rfes.. can't seem to find this in the Labs source to try and modify.

I'm pretty sure you can submit this one the usual way since tools for managing versioned assets are part of Houdini since 19