Hey guys,
Not shure where to start on this.
But I need to make an object which is essentially a group of instanced objects, not geometry(but can be displayed as geometry).
So for example i have a object called “Trees”
when i select this helper.object it has multiple sub-objects. Each subobject has their own matrix, color etc…
Would the best way to do this be to extend a helper object(ie the dummy or point), or to somehow make my own object?
Sounds like a system object to me. That’s an object controls the creation and instancing of other types of objects.
The “Sun” system in Max is such an example. It’s creating other lights, but controls them too.
“System objects are not creatable by MAXScript.” from the maxscript help… DOH!.
My approach:
Either create a dummy/dummy geometry with custom attributes or just create a rollout/floater.
Dummy with CA:
The CA gives you Buttons, Lists, Dropdowns to manage the members of your system, their behaviour. The Dummy can sync with the scene with its onOpen handlers and/or callbacks.
It stores all relevant informations and exposes usefull methods.
RollOut/Floater:
Same same but different. Information will likely be stored just in textfiles. Callback or “sync now” button is needed.
Both ways don’t need a maxscript (simple) plugin and are easily shareable.
Maybe we should think about some “maxScript Pattern Library”, where patterns for common problems are layout in an abstract way, and some code samples and skeletons.
[1] http://en.wikipedia.org/wiki/Pattern_language
Georg