Graphical User Interface
When MLDesigner opens you will see the MLDesigner’s graphical user interface (GUI) containing the following elements:
- Menu Bar - with entries for the File, Edit, View, Window, Extras and Help menu
- Toolbars - The lower group of toolbars is extended when a model is opened in the Model Editor. Active toolbar icons depend on the type of model selected in the Model Editor and whether MLDesigner is in simulation mode or edit mode. In simulation mode run control icons are visible on the toolbar.
- Tree View History - A combo-box containing a list of models last opened or used as instances in other models. The number of models displayed in the list is determined in the Settings Dialog under the History item of the Tree View category.
- Tree Filter - A toolbar containing buttons which allow you to constrain the model or file types displayed in the Tree View
- Tree View - The window with tabs to select the three views Library (structure of model base), Model, and Search (use the right mouse button to activate the context menu). The Tree View is used to create, open, and maintain your libraries, primitives, ﬁles, etc. To see the physical location of the respective model, hold the cursor over the entry in the Library tab and wait a second or so for the tool tip text to display. The Library tab of the Tree View is also called Library View.
- Parameter Set Window - Here you can create a new parameter set. You can run simulations using preset values from more than one parameter set. An example is described in the Modeling Guide of MLDesigner Manual.
- Property Editor - This is where you change or deﬁne the default properties of models and ports. [P]arameters and [T]argets are given values, and information about the model or model instance can be entered such as description and short description. The active tab depends on the type of model instance selected in the Model Editor. When in Simulation Mode with no system elements selected in the Model Editor, the Simulation Properties tab is active.
- Model Editor - That is your main work area where you build primitives, modules and
systems. Model Editor windows are arranged within the so-called modeling workspace area. You can maximize your Model Editor windows so that the whole modeling workspace area is occupied by exactly one Model Editor window.
- Data Structure Editor - Here you can edit user deﬁned data structures. Editable data structures have a green icon exactly the same shape as the red icon. You must open a system, module, primitive or library with write access before you can create a new data structure or edit members of a data structure.
- Data Structure Member Editor - It is part of the Data Structure Editor for creating, deleting and modifying members of existing data structures.
- Console Window - The Console Window has two tabs when you are in edit mode:
Further tabs appear when you are in simulation mode:
- The Command tab where Tcl commands can be entered.
- The Log tab where a record of your actions is displayed and error messages or warnings are printed. You can save the contents of the Console to a ﬁle or clear the Console by selecting the appropriate menu option from the context menu.
Two additional tabs can be turned on when you are in simulation mode:
- The Simulation tab where Tcl and PTcL commands can be entered and the standard output channels of the simulation process are routed to.
- The Progress tab where you can monitor the compile process and the progress of the simulation measured as a percentage value.
- The Probes tab where you see a list of all probes. Probes are useful for debugging systems and the list of probes makes it easier for you to find and edit them. While in simulation mode you can add probes via a context menu in the model editor. Right-click on a port and choose Add Probe.
- The Breakpoints tab where you see a list of all breakpoints. Breakpoints are useful for debugging systems and the list of breakpoints makes it easier for you to ﬁnd and edit them. You can add and remove breakpoints while in simulation mode. To do so select Add Breakpoint or Remove Breakpoint from the context menu over the relevant entry in the Breakpoints Console. The breakpoints tab is can be activated by a toolbar button in the modeling toolbar.
- The Animation tab, appears if the Textual Animation icon on the modeling toolbar is checked. The port and model instance ﬁrings are printed to the console in this mode and simulation is a lot slower.