clarify meaning of nested hideResult annotation

[gkurzbach]

It is possible to set the hideResult annotation on composite components, e.g. complete submodels or data sets. It then has an effect on the contained variables.
But then it is unclear who wins if there is a hideResult annotation for both the composite component and an inner variable and they contradict each other. See following (incomplete) truth table

hideResult on

Component	Variable	Result
true	none	true
false	none	false
none	true	true
none	false	false
true	false	??
false	true	??

Please clarify.

[HansOlsson]

Dymola gives precedence for the lowest level (variable), but I'm not sure that is ideal.

For Evaluate the highest level is currently given precedence in the specification - but Dymola as default only give precedence for Evaluate=true on the highest level (so basically Evaluate=true if set for least one of them) due to customer models.

[gkurzbach]

An example: 'hideResult=true' is used in one of our customer's libraries to reduce the number of results on a composit component. He does not want any results from the sub-component.
In this case, it seems to make sense for annotations on higher level (composite) to overwrite lower level annotations.

[HansOlsson]

An example: 'hideResult=true' is used in one of our customer's libraries to reduce the number of results on a composit component. He does not want any results from the sub-component. In this case, it seems to make sense for annotations on higher level (composite) to overwrite lower level annotations.

Another interpretation is that it would be an or of the different ones. It would work for that case. The question is whether we have the case where someone has a component where they need hideResult=false to unhide a component - including ones having hideResult=true?

[gkurzbach]

Another interpretation is that it would be an or of the different ones. It would work for that case. The question is whether we have the case where someone has a component where they need hideResult=false to unhide a component - including ones having hideResult=true?

Composite models are usually designed inside out. First inner components are defined and the they are put in an enclosing model.
So the common case is to override inner settings from outside. Both use cases seem to be valid, but a modeler is not able to specify one of the two cases, depending on the defined rules.

[HansOlsson]

Language group:

• Precedence for hiding in case of conflicts (tools can always decide to store/show more).

Also consider using "protected".
Think more about it (including animation and similar cases where you want to include it - but can see as deliberate action).

[sbaetzing]

Some hints from the perspective of a model developer.
Not in all cases it possible to use "protected" since replaceable class declarations wont appear inside the parameter dialog. That is why we are going with hideResult instead.