vrecko
virtual reality framework
 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Friends Macros Pages
vrecko::VreckoMessage Class Reference

#include <Message.h>

Inheritance diagram for vrecko::VreckoMessage:
APEditorController::AbilityMapper::MessageMapping base::SystemInfo::MessageSIThreadCreated CarSim::MessageCarEdge CarSim::MessageCarEdgeData CarSim::MessageCarEnvirons CarSim::MessageCarSimParameters CarSim::MessageCarStatePtr CarSim::MessageEdgeOffset CarSim::MessageFirst3Juncs CarSim::MessageRoadAndDir CarSim::MessageStartStopDestination CarSim::MessageVectorUnsignedInt ode::DynamicScene::MessageODERequest PhysXPlugin::MessageNxActorWithName vrecko::ControllableAbility::MessageCAINFO vrecko::MessageCAButtonEvent vrecko::MessageSensorTransformation vrecko::MessageVoid

Public Member Functions

 VreckoMessage ()
 
virtual ~VreckoMessage ()
 
virtual const char * getMessageId ()
 
virtual bool setValueFromString (const char *valueAsString)
 
virtual bool isEqualTo (VreckoMessage *otherMsg)
 

Constructor & Destructor Documentation

vrecko::VreckoMessage::VreckoMessage ( )
inline
virtual vrecko::VreckoMessage::~VreckoMessage ( )
inlinevirtual

Member Function Documentation

virtual bool vrecko::VreckoMessage::isEqualTo ( VreckoMessage otherMsg)
inlinevirtual

Is the contents of this message same as of the other one (of the same kind)?

Again, OVERRIDING IS REQUIRED for ACTIVATE_INPUT message sending, i.e. "if ability A output pin O outputs message with <em>content</em> M, then create a message M2 (might be different type), send it to ability A2 input pin I". If the respective message is only used simply for direct (much more common) message sending, you DO NOT NEED TO OVERRIDE this method.

Reimplemented in vrecko::MessageVoid.

virtual bool vrecko::VreckoMessage::setValueFromString ( const char *  valueAsString)
inlinevirtual

Parses the given string to get the data for this message.

OVERRIDING IS REQUIRED for ACTIVATE_INPUT message sending, i.e. "if ability A output pin O outputs message with <em>content</em> M, then create a message M2 (might be different type), send it to ability A2 input pin I". If the respective message is only used simply for direct (much more common) message sending, you DO NOT NEED TO OVERRIDE this method.

Reimplemented in vrecko::MessageVoid, and base::SystemInfo::MessageSIThreadCreated.


The documentation for this class was generated from the following file: