Has there been a change to how the parameters related to external toxes on COMPs are handled?
I have a case where all of those parameters are disabled. It’s inside a component that’s a clone which is inside one that’s an external tox.
The structure is: /demo/rendering[tox]/sceneEditor[clone]/sceneLoader[clone]/container/THIS_ONE
I can still save the component to a tox manually or with Python, but I can’t get that parameter set so when it gets loaded back in elsewhere it isn’t populated by default.
Or has it been like this for a while and I just didn’t notice?
I think the issue here is that a component can’t be both a clone and an external since that is essentially giving it two competing masters. We’ve tried to make this clearer in more recent versions by disabling those parameters on clones.
You can still access those parameters on the version inside the master if you want to make the child master an external as well.
Hope that makes sense. If you’re still having trouble and you want to send us a copy of your project I can double check things are working as planned.
That makes sense.
The context is a tool that loads, edits, and saves scenes where each scene is a tox. There’s some infrastructure around the loading and saving process that I’d like to have as a cloneable component. Currently that loader component puts the scene comp inside the loader itself. But maybe it could put it in a separate container next to the loader that’s not cloned.
Another possibility would be to have things marked as clone immune able to link to tox files even if they’re inside a clone.
If I am understanding your setup correctly, I agree it would probably be better for the loader to put the loaded components outside of the clone.
In theory I think you’re right about the idea of making those loaded comps clone immune which would allow them to exist as externals inside a clone, but I don’t know if that is possible right now. We are in the middle of a major cloning overhaul at the moment so some of those features are still in progress.