the methodology you use is the same as you describe as being 'kludgy' only difference is that the game environment will do it for you :)
That would add just an extra layer ontop of the Type/Class system that Bmax uses. B3D/B+ did this, but bmax allows you more intimate control over this by handling it yourself.
As far as accessing an individual objects methods/properties directly, ofcourse thats still possible, but youll have to make a reference to that specific object in the form of a variable.
this is still possible ofcourse.
The List in my example merely exists to make sure that these created objects do not get deleted at random.
The fact that you can loop through it to access all of the objects individually is merely an added bonus.
As far as responding to messages and events, im not sure what you mean. You can create a nice EventHandling system using Function pointers, but thats out of the scope of this thread and generally a very different subject.
That would add just an extra layer ontop of the Type/Class system that Bmax uses. B3D/B+ did this, but bmax allows you more intimate control over this by handling it yourself.
As far as accessing an individual objects methods/properties directly, ofcourse thats still possible, but youll have to make a reference to that specific object in the form of a variable.
Global MyObj:SomeType = new SomeType; '// create the object ... some code MyObj.DoSomething(); ... MyObj.DoSomethingElse();
this is still possible ofcourse.
The List in my example merely exists to make sure that these created objects do not get deleted at random.
The fact that you can loop through it to access all of the objects individually is merely an added bonus.
As far as responding to messages and events, im not sure what you mean. You can create a nice EventHandling system using Function pointers, but thats out of the scope of this thread and generally a very different subject.