annotation(Dialog(enable = ...)) is not working correctly

[christiankral <dr.christian.kral@…>]

I noticed the following issue in r20061 under Ubuntu 12.04, 32 bit.

I wanted to modify the parameter mu_rConst in the diagram parameter mode of an instance of

Modelica.Magnetic.FluxTubes.Shapes.FixedShape.Cuboid

But I cannot change the parameter, even though nonLinearPermeability is set to false. I can certainly set the parameter textually, but it does not work in the diagram mode of OMEdit.

I attached an example to demonstrate the issue (right click on iron -> Paramerers -> mu_rConst cannot be modified).

[christiankral <dr.christian.kral@…>]

Example demonstrates the issue

[Martin Sjölund]

This ticket was not closed for 1.9.1, which has now been released. It was batch modified for milestone 1.9.2 (but maybe an empty milestone was more appropriate; feel free to change it).

[Christian Kral <dr.christian.kral@…>]

Tested the attached example with r24056 under Ubuntu 14.04 and noticed that this issue still exists. I think the same applies to Windows 7, where I recently stumbled into a similar problem.

[Martin Sjölund]

Milestone changed to 1.9.3 since 1.9.2 was released.

[Dietmar Winkler]

Some more details what else does not work with the enable option.

parameter Boolean enableFoo annotation (Dialog(tab="Foo"));
parameter Integer Bar annotation (Dialog(tab="Foo", group="Bar", enable=enableFoo));

Will place enableFoo correctly in the "Foo" tab but Bar will appear in the "General".
What I noticed is that the input can actually be enabled/disabled as long as the value is hard coded in the modelica source. But OMedit will not react on any changes done to the Boolean in OMedit itself.

[Martin Sjölund]

Moved to new milestone 1.9.4

[Dietmar Winkler]

Small update. In my example above about the placement. Bar is as of 1.9.4~dev.beta1 correctly placed in the "Foo" tab. But the original bug of not being able to enter any value into Bar is still valid.

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[leo.gall@…]

One of our customers came across this problem when trying to use

Modelica.Blocks.Sources.CombiTimeTable

in OpenModelica 1.9.6.

If you set tableOnFile=true, you still cannot define tableName or fileName.
CombiTimeTable is a very frequently used block, therefore GUI support would be highly appreciated.

[Adrian Pop]

The problem here is that we evaluate the parameter once via getComponentAnnotations in the model and we don't do it again if is changed from OMEdit.

We need some sort of sequence setParameterValue, getComponentAnnotations again while the dialog is active. Adeel, could you try something like this?

[Francesco Casella]

See also #4008

[Adeel Asghar]

Replying to adrpo:

The problem here is that we evaluate the parameter once via getComponentAnnotations in the model and we don't do it again if is changed from OMEdit.

We need some sort of sequence setParameterValue, getComponentAnnotations again while the dialog is active. Adeel, could you try something like this?

No, this will not work since the parameters are set as modifiers on the component instance. I need some sort of component instance from OMC.

[Adeel Asghar]

As a workaround all parameters are enabled.
04e3776/OMEdit.

[Francesco Casella]

@adeas31, @adrpo is this going to be finally resolved with the new frontend-based API?

[Francesco Casella]

I understand from @adrpo that this should be fairly easily implemented with the new front-end-based API, so I am retargeting this to 1.14.0

[Francesco Casella]

See #2132

[Francesco Casella]

@adeas31, I understand this requires changes both to OMEdit and to the API. Are the former already done, and what is missing from the API?

[Francesco Casella]

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2.

This issue, previously marked as blocker for 1.14.0, is rescheduled to 1.15.0

[Francesco Casella]

Release 1.15.0 was scrapped, because replaceable support eventually turned out to be more easily implemented in 1.16.0. Hence, all 1.15.0 tickets are rescheduled to 1.16.0

[Francesco Casella]

Retargeted to 1.17.0 after 1.16.0 release

[Francesco Casella]

Rescheduled to 1.18.0

[Francesco Casella]

Ticket retargeted after milestone closed

[Francesco Casella]

1.18.0 blocker tickets moved to 1.19.0

[Francesco Casella]

Milestone renamed