Thread: I believe I've found an official Answer to my Problem (Object Factories)

Would inheriting from MessageSystem solve the problem to have them use the default handler unless defined? might be kind of illogical though.

Scratch that. It's really stupid and illogical to do that for every class just to use the default handler. Lemme know if you figure out a way without macro magic.

but I found if I was retrieving Object's from an ObjectSystem then there would be no use for a functor

Scratch that. I see why the functor was necessary, since it might not always be Object's you're working with. I just missed that because you went off talking about Object's.


I'm still unclear on the handler using a switch or not, and how to pass MSG_FIRE instead of a number - that require either a macro, global const, or global enum?

EDIT: I guess if the message system was that robust there would be a global enum or enum in the handler class or something.

EDIT: Found a nice powerpoint on scripting: http://www.cmpevents.com/sessions/GD...sy_UPDATED.ppt

Use script handlers
- For flexibility and prototyping
- To avoid C++ dependencies
- Reduce C++ subclasses

Use C++ handlers
- For special arg handling
- Performance, maintainance

It answered my question on how to handle a special amount of arguments and a few other things. Still though, I have a lot to learn before I can impliment this message system or scripting system.