Any way through ruby to create a component collection
-
I have a component that needs a number of dynamic components. As it is now I just load those components when the script starts. But then it just gets cluttered in with all of these new definitions that get made as I change attributes. So I thought, maybe it is better that I just have this as a component collection. If necessary I can just make this collection as part of the install process for the plugin, but I was wondering if there is a way via the API to create this collection on the fly. I didn't see any API references for this, but I thought I would check.
David
-
Hi david
I've been looking into using chrisglaseiersSceneMachineMac.rb or nSet.rb (if I can get it Mac'ified) or martins alternate API
to manipulate different options within a single object, early days for me,
I'm trying to bypass DC'c, but still might be worth a look for your needs....
john
-
@driven said:
Hi david
I've been looking into using chrisglaseiersSceneMachineMac.rb or nSet.rb (if I can get it Mac'ified) or martins alternate API
to manipulate different options within a single object, early days for me,
I'm trying to bypass DC'c, but still might be worth a look for your needs....
john
If you are going to try that you might as well have a go at the latest attempt to amalgamate and expand all of these. The expansion includes the ability to import names of components, layers and scenes from a model or make new for grouping into hierarchical sets going back up to the project itself. I am currently working on animation, but first I need to finish how to plug in new nsets into the main root nset (manifold). All is very much a work in progress. I leave odd explanations and notes in the notebook linked below.
It would be best if you open it in a PC first, as although I have tried to follow the Mac compatibility guidelines as you know it has failed before. Anyway it's a possible grope forward!
I agree about bypassing dc's ...
Chris
Extract into plugins folder WIP
-
And, John, I think you said you have Macified cgScenes. I wonder if that version also works on PCs. Or do you think it should released as a Mac version?
Oh and also you should note that cgScene start button was introduced because Macs run the script before loading the model. However nset doesn't rely on model data at the start but it is something you might like to add to the "no js after window.location" for callbacks I pointed to before.
Advertisement