Properties

Name of the Data Model. Must be unique.

The class generated will be CigiData.

 

Name of the Container the Data Model belongs.

 

Choice between:

 

When External, the object can be specified or changed using button:

From the selection window, header file and library (including the Data Model) will be listed (read only).

These information are part of the Model Definition files. See here for more info.

 

List all the entities in different scenarios, using this Data Model.

Format: Scenario - Type (Entity, Player or Catalog) - Name

 

Specify the Data Model (external or local) the current one inherit from, to specialize it.

Plain arrow is use to translate this inheritance.

Select the Data Model in the Available Items list (8) then use the button to set.

Use the button to remove the inheritance.

Specify all the Data Models (externals or locals) the current one are using internally as variables.

This setting is used for the code generation to create correct makefile and add necessary #include into the header file.

Dashed arrows are use to translate this usage.

Select the Data Model in the Available Items list (8) then use the button to add.

Select the Data Model in the list and use the button to remove.

List all the Data Models (or Components) that inherit from the current one.

 

List all the Data Models loaded into the database (externals or locals).

 

Exclude the Data Model from the code generation.
Disabled Data Model will not be included into the items using it (entities but not only) without the need to remove it from all users.

Disabling is error prone while removing might leave dangled pointers.

 

When checked, the Data Model will not be available into the entity model list.

 

If checked, the Data Model class, when attached to an owner (Entity, Player, etc.) will create an object with new.

If unchecked, the attachment will be seen as a reference without object (NULL pointer). This can be useful when different Entities (for example) must share a same and unique Data Model. It is then the responsibility of the user code (wherever it is) to create the Data Model, reference it whenever it is needed and delete it at simulation stop.

 

When checked, the Data Model cannot be modified. All changes will be lost at Ok or Apply.

 

Use this button to replace the current Data Model with a previously exported Data Model in /Data/Shared/Models.

All current content will be lost.

 

Use this button to save the current Data Model for later import. Default location is /Data/Shared/Models.

 

Use this button to automatically translate the current local Data Model into a C++ class with a header and a source file, in order to include it into a dedicated library.

The Data Model will then become External.

See here for more information.

 

Specify the color to be used for drawing the Data Model symbol into the Diagram panel.

Default is white.

 

This content is put as is, without any preprocessing, at the beginning of the database header file and outside of any class definition.

 

See Inlines: show the automatic inlines as they will be generated for the Dyn-UI variables.

 

 

This part is used to process EVENT or PACKET events when selected.

case Event received from raiseEvent(...) method in the code.

case Packet received from send(...) method in the code.

 

If Accept Events is checked, the case..break code block will be called whenever an Event is raised towards the Entity holding the Data Model.

If Accept Packets is checked, the case..break code block will be called whenever a Packet is received in a Channel used by the Entity holding the Data Model.

 

Any description of the Data Model can be put here and will be used for the automatic document generation (see Make Documents)