Allows to create the RenderRequest object of the fileds type with the value below :
- {l Code}: {l Select All Code}
enum RequestType
{
createTile,
refreshTile,
destroyTile,
deleteTile,
colorTile,
temporalMarkTile,
attachTile,
detachTile,
attachCreature,
detachCreature,
toggleCreatureVisibility,
showSquareSelector,
createCreature,
destroyCreature,
deleteCreature,
setObjectAnimationState,
createCreatureVisualDebug,
destroyCreatureVisualDebug,
createWeapon,
destroyWeapon,
deleteWeapon,
pickUpCreature,
dropCreature,
rotateCreaturesInHand,
createRoom,
destroyRoom,
deleteRoom,
createRoomObject,
destroyRoomObject,
deleteRoomObject,
createTrap,
destroyTrap,
deleteTrap,
createTreasuryIndicator,
destroyTreasuryIndicator,
createMapLight,
updateMapLight,
destroyMapLight,
destroyMapLightVisualIndicator,
deleteMapLight,
createField,
refreshField,
destroyField,
moveSceneNode,
orientSceneNodeToward,
reorientSceneNode,
scaleSceneNode,
createMissileObject,
destroyMissileObject,
deleteMissileObject, //setMissileObjectAnimationState,
noRequest
};
The goal is to have separate class for each of them ... Than we are protected by C++ type system , and each of it has it's own constructor and it's safer from crashes ... Should I start splitting that , shouldn't be too though with some bash tools magic ...
( BTW: the same regards the subfunctions for each user command in bool Console::executePromptCommand(const std::string& command, std::string arguments) as it grows too large ! Don;'t know whether that is equally simple as dividing to separate classes or functions ... ) .
Bertram say something !