you mean there is no way in BMax to send or respond to events or messages...
i could see having to loop through instances to 'update' objects in B3D, but surely BMax must have progressed past this...
ok... hear me out on this please...
the whole idea of creating a class from which objects can be instantiated is so that these objects can be self contained entities... once one comes into being, being capable taking care of itself... allowing external access to its exposed functionality to maintain a symbiance with the 'world' it exists in... denying access to private data and functions...
create an object, and the constructor does all the initial stuff... delete it, and the destructor cleans up...
while it is 'alive' shouldn't the 'game' environment that this object exists in send constant update messages from which the objects update method could automatically keep it current... and thus eliminating this kludgey type methodology of maintaining a LIST to track these objects...
--Mike
i could see having to loop through instances to 'update' objects in B3D, but surely BMax must have progressed past this...
ok... hear me out on this please...
the whole idea of creating a class from which objects can be instantiated is so that these objects can be self contained entities... once one comes into being, being capable taking care of itself... allowing external access to its exposed functionality to maintain a symbiance with the 'world' it exists in... denying access to private data and functions...
create an object, and the constructor does all the initial stuff... delete it, and the destructor cleans up...
while it is 'alive' shouldn't the 'game' environment that this object exists in send constant update messages from which the objects update method could automatically keep it current... and thus eliminating this kludgey type methodology of maintaining a LIST to track these objects...
--Mike