Changes between Version 2 and Version 3 of Ticket #5628, comment 2
- Timestamp:
- 2019-09-09T17:31:54Z (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #5628, comment 2
v2 v3 7 7 a tool may set the parameter value in a modifier automatically, if used as dimension size of a vector of connectors 8 8 9 So, in the case 2. described above, I would say that the wanted behaviour is that one first drags the {{{And}}} component (which has default {{{nu = 0}}}), then, when graphically connecting the input {{{and .u}}} to the output of {{{booleanExpression.y}}}, one should first be asked if the two entire arrays should be connected, or rather some of their individual components.9 So, in the case 2. described above, I would say that the wanted behaviour is that one first drags the {{{And}}} component (which has default {{{nu = 0}}}), then, when graphically connecting the input {{{and1.u}}} to the output of {{{booleanExpression1.y}}}, one should first be asked if the two entire arrays should be connected, or rather some of their individual components. 10 10 11 11 In the first case, {{{nu}}} should automatically be set to {{{3}}}, which is the size of the other connector, and a {{{connect(booleanExpression1.y, and1.u)}}} statement should be added. 12 12 13 In the second case, one should select which individual array element to pick on the non-connectorSize'd connector, while the standard connectorSizing mechanism should be used on {{{and .u}}}.13 In the second case, one should select which individual array element to pick on the non-connectorSize'd connector, while the standard connectorSizing mechanism should be used on {{{and1.u}}}. 14 14 15 15 When connecting {{{m.c}}} to an expandable connector, OMEdit doesn't know the type of the other connector, because the other connector is implicitly defined by the connect statement. This may be a problem, because there is not enough information available to infer the size of the parameter with {{{connectorSizing = true}}} ({{{and.nu}}}, in this case). 16 16 17 In this case, I would also suggest to ask first if one wants to connect a scalar element or the entire array connector {{{and .u}}} to a connector on the expandable connector. In the first case, the standard {{{connectorSizing}}} mechanism is applied. In the other case, the pop-up window should probably also ask for the value of the {{{connectorSizing=true}}} parameter ({{{nu}}}), because the size of the other connector is not available locally when using an expandable connector.17 In this case, I would also suggest to ask first if one wants to connect a scalar element or the entire array connector {{{and1.u}}} to a connector on the expandable connector. In the first case, the standard {{{connectorSizing}}} mechanism is applied. In the other case, the pop-up window should probably also ask for the value of the {{{connectorSizing=true}}} parameter ({{{nu}}}), because the size of the other connector is not available locally when using an expandable connector. 18 18 19 19 It would be nice to get this for 1.14.0, so that the newly introduced feature is correct.
