Link Editor Dialog Box

The Link Editor supports the definition of reusable link models that are used to create link objects in the Project Editor. Each link object’s attribute interfaces, presentation, and behavior, are determined by the link model that it relies upon.

For more information about the relationship between link objects and link models, see "Communication Mechanisms" on page 331.

You define the link model specifications described in this section in the Link Editor dialog box, shown in the following figure.

Figure 209: Link Editor Dialog Box

Link Editor dialog box

A link model specifies the following information:

  • Supported Link Type – Each link model can support one or more of the four fundamental types of links. These are point-to-point duplex, point-to-point simplex, bus, and tap links.

  • Keywords – The keywords of a link model allow it to be selectively displayed in the Project Editor object palette. A model may declare any number of keywords that represent characteristics that it has. These keywords are compared to those requested when configuring the object palette, to determine whether to offer the model as a choice. The objective of this mechanism is to allow the user to reduce the number of models presented in the object palette while presenting only those models that are of interest for the current application.

  • Model Comments – Each link model contains a set of comments that describe its characteristics, potential applications, and any information that may be of interest to a user of the model. Because users of other OPNET solutions do not have access to link model internals, the comments may provide the primary available information about the model’s capabilities and interfaces. Embedding documentation on the model’s interfaces as an intrinsic part of the model itself provides convenient access to information for model users and helps to ensure that model documentation remains consistent with a model as it evolves through different phases of development.

  • Attribute Interfaces – In the same manner that node and process models can affect the presentation and usage of attributes of nodes and modules, respectively, link models can provide specifications for the attributes of link objects in the Project Editor. The relationship between link models and links most closely resembles the interaction between process models and modules, because, similarly to process models, link models contain no objects that can promote attributes. Therefore the only attributes that a link can promote are the “link model attributes” described in a later section. Like a process model, a link model can specify configuration information for built-in attributes of the link object. Specifically, operations that are possible are attribute pre-assignment, attribute hiding, attribute renaming, and changing of attribute properties.

    For more information about these mechanisms, see Chapter 4 “Modeling Framework” on page 80.

  • Attribute Specification – Allows you to change the default behavior when a user changes a link’s attribute settings. You can specify a custom ETS library and event handlers by clicking the ETS Handlers button.