For Publishers, the selected Objects or Interaction [Code] can be processed at requested frequency. If On_Event is selected, only the specified Event will trigger the Federate Code.
The FedItem can be exported as a file or can be imported from another (exported) file.
If imported, all current definitions will be replaced.
Exporting a FedItem can be useful to build a library or to exchange a FedItem from one database to one another.
It can be a good idea to create a subdirectory into the data/shared directory. One directory per FOM to avoid mixing FedItems from different FOM that would not work.
Exported FedItems can be imported from the contextual menu. Four kind of files are automatically selected:
1- Publishing Object (extension fpo)
2- Publishing Interaction (extension fpi)
3- Subscribing Object (extension fso)
4- Subscribing Interaction (extension fsi)
You can import any of them from the Import popup menu:
List here all entities (of any scenario) using this FedObject at runtime. This can be useful when combined with a Modeling Object as vsTASKER automatically generates some code to facilitate the data processing.
Useto select which entity of the current scenario to add.
Useto remove from the list the selected entity.
Uncheck entities that must not be processed at runtime.
When switched ON on a Publisher, any runtime entity on vsTASKER will be added to the FedItem and be ready to publish, unless discarded from the Register panel of the FedItem by setting the entity variable to NULL. If OFF, runtime entities will be ignored by the FedItem.
When switched ON on a Subscriber, the discover part (see the discover pane) will automatically create a "default" entity and will try to set the local pointer to the attached component (if found) for the next focus.
