<<Contents
Issue: You receive a message with the text "Update all references to this node in the model to point to the new name?" (English version of Model Editor only) and you are wondering what it means.
Resolution: In HLA, nodes may reference each other by name. For example, an interaction contains a property named "Transportation" which is expected to have as its value the name of one of the transportations declared elsewhere in the model.
When the name of such a node, such as a transportation node, is altered, Model Editor can update all such references to keep the two in synch. However, this can introduce problems in certain cases if a node is given the same name as another node in the model. For instance, having two transportation nodes with the same name will confuse the model, as it will be impossible to determine to which of the two transportation nodes any particular reference was originally pointing.
As an example, presume three interactions are referencing Transportation1, and two other interactions are referencing Transportation2. Should Transportation1 be renamed to Transportation2, and the references are updated, all references will be pointing to a Transportation2. If either of the transportation nodes are then renamed, all five of the references will be altered, rather than simply the original two.
This problem does not occur with valid models (as having such ambiguity is considered an error) but may crop up during renaming operations.
Note: If you are receiving this message and you cannot find the corresponding reference node, it is probably in the Metanode tree.
Model Editor handles load and save operations via a customizable and extensible method of plug-in modules. These modules are stored in the "Translators" directory underneath the root Model Editor directory.
When Model Editor launches, it checks the Translators directory for valid load/save modules. These modules must have the ".xslt" file extension to be recognized. Files which are invalid and cannot be parsed by the XML parser are skipped.
If you know you have a particular translator, but it is not showing up in the open or save dialogs, it is possible there are errors in the translator file itself.
Model Editor has one format ("Raw XML") which is built-in to the editor itself. Therefore this file format will always be available, regardless of the state of the translators. The raw XML format can be used as a fail-safe way of saving a model if changes have been made before discovering that the desired output module is not available. (It is important, however, to remember to load the resulting file as "Raw XML" and not using one of the other translators that happens to operate on *.xml files.)