Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
what_is_new_3 [2015/09/16 18:41] admin [Submodels] |
what_is_new_3 [2015/09/16 18:51] admin |
||
|---|---|---|---|
| Line 85: | Line 85: | ||
| * Expressions used by CalculateMap, CalculateLookupTable, CalculateValue etc are rejected when identifiers not bound to any corresponding NumberMap, NumberTable or NumberValue are used. | * Expressions used by CalculateMap, CalculateLookupTable, CalculateValue etc are rejected when identifiers not bound to any corresponding NumberMap, NumberTable or NumberValue are used. | ||
| * The expression editor shows which identifiers [iX, tX and vX] area available to be used. | * The expression editor shows which identifiers [iX, tX and vX] area available to be used. | ||
| - | * When editing a carrier, the comment and alias from the carrier itself are used as the port description and name by the functor editor dialog. | + | * When editing a carrier, the comment and alias from the carrier itself are used as the port description and port name by the functor editor dialog. |
| * Editing hooks now fills the index automatically using the most appropriate value to avoid repetitions. | * Editing hooks now fills the index automatically using the most appropriate value to avoid repetitions. | ||
| Line 100: | Line 100: | ||
| * Issues from the list can be searched by their corresponding functor names, alias and error messages. | * Issues from the list can be searched by their corresponding functor names, alias and error messages. | ||
| * Issues can be searched using special filters is:container, is:loop, is:carrier, is:hook, is:mux, is:junction, is:loader, is:saver, is:submodel, is:systemsubmodel, is:usersubmodel, is:localsubmodel. These filters operates over the corresponding functor. | * Issues can be searched using special filters is:container, is:loop, is:carrier, is:hook, is:mux, is:junction, is:loader, is:saver, is:submodel, is:systemsubmodel, is:usersubmodel, is:localsubmodel. These filters operates over the corresponding functor. | ||
| - | * It is possible to locate the functor from the corresponding issue in the issue list and to find the issue from the corresponding functor in the model view. | + | * It is possible to locate the functor from the corresponding issue in the issue list and find the issue from the corresponding functor in the model view. |
| * The issue pane of a model is visible only when the corresponding model is visible on the interface. | * The issue pane of a model is visible only when the corresponding model is visible on the interface. | ||
| * The total issues of a functor is visible according to the current search criteria. | * The total issues of a functor is visible according to the current search criteria. | ||
| Line 132: | Line 132: | ||
| * The functors are presented in a hierarchical view. | * The functors are presented in a hierarchical view. | ||
| * It is possible to collapsed and expand elements of the hierarchical view. | * It is possible to collapsed and expand elements of the hierarchical view. | ||
| - | * It is possible to search functors by their names, alias and descriptions. The containers of the functors found during the search are always visible to clearly indicate where that functor is located. The accumulated time presented is updated to refer to the time of the visible functors only. | + | * It is possible to search functors by their names, alias and descriptions. The containers of the functors found during the search are always visible to clearly indicate where that functor is located. The accumulated time presented is updated to refer to the accumulated time spent by the visible functors only. |
| ==== Submodels ==== | ==== Submodels ==== | ||
| - | * Local submodels are contained in a folder named after the main model filename, but replacing dots by "_" and followed by "_Submodels". For example, the main model "test.egoml" should place its local submodels in a folder "test_egoml_Submodels". The old folder "Submodels" is read for compatibility with the previous versions of the software. | + | * Local submodels are contained in a folder named after the main model filename, but replacing dots with "_" and followed by "_Submodels". For example, the main model "test.egoml" should place its local submodels in a folder "test_egoml_Submodels". The old folder "Submodels" is processed for compatibility with the previous versions of the software. |
| * Submodels can also define local submodels [Nested submodels can not be edited yet using the graphical interface, but they can be read and written as any other submodel. The definition can also include other nested local submodels]. | * Submodels can also define local submodels [Nested submodels can not be edited yet using the graphical interface, but they can be read and written as any other submodel. The definition can also include other nested local submodels]. | ||
| * It is possible to select a group and functors and transform the selection into a local submodel. The selection will be replaced by the corresponding submodel. The inputs and outputs connecting the functor selection to the other functors are used as inputs and outputs of the submodel itself. A unique name is also suggested to the submodel. | * It is possible to select a group and functors and transform the selection into a local submodel. The selection will be replaced by the corresponding submodel. The inputs and outputs connecting the functor selection to the other functors are used as inputs and outputs of the submodel itself. A unique name is also suggested to the submodel. | ||