Be clearer about showStartAttributes.

[HansOlsson]

Closes #3406

[d-hedberg]

Give tools more freedom to show what makes most sense when showStartAttribute is not specified.

[HansOlsson]

To me this:

• Gives tools the freedom to show start-values when appropriate
• Gives model developers the possibility to override that

The only part that seem controversial is the interaction between values of connectorSizing and showStartAttributes and showing the variable in the parameter-dialog, but I don't see any practical issues with it, only that it looks a bit impure.

As an example consider:

   Real x1 annotation(Dialog(showStartAttribute=false));
   Real x2 annotation(Dialog(showStartAttribute=false,group="Start"));
   Real x3 annotation(Dialog(showStartAttribute=true));
   Real x4 annotation(Dialog(showStartAttribute=true,group="Start"));

giving something like:

[henrikt-ma]

It is precisely the difference between the visibility of x1 and x3 that bothers me. The showStartAttribute should not have anything to do with whether the variable is visible or not, just tell whether it is the value or the start/fixed which is exposed in case the variable is visible.

[HansOlsson]

It is precisely the difference between the visibility of x1 and x3 that bothers me. The showStartAttribute should not have anything to do with whether the variable is visible or not, just tell whether it is the value or the start/fixed which is exposed in case the variable is visible.

The logical and strict case would be that x3 wouldn't be visible either (so one would have to write Real x3 annotation(Dialog(showStartAttribute=true, group="Initialization")); to ensure that it is shown as in the picture above).

The proposed text allows that; it's just that it will be seen as cumbersome for some.

[henrikt-ma]

The proposed text allows that; it's just that it will be seen as cumbersome for some.

Of course it is allowed, and yes, some will perceive it as cumbersome. Others will appreciate a separation of concerns.