Opened 5 years ago
Last modified 3 years ago
#5609 new defect
Redeclared model shows icon of base class
| Reported by: | Francesco Casella | Owned by: | Adrian Pop |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.19.0 |
| Component: | NF API | Version: | |
| Keywords: | Cc: | Andrea Bartolini, H.J.van.Weers@… |
Description
Please load the attached test package in OMEdit.
When opening Test2, the model in the diagram should have an icon with "M2". Instead, the icon of the base class, "M1", is shown.
Attachments (1)
Change History (10)
by , 5 years ago
| Attachment: | TestRedeclareIcon.mo added |
|---|
comment:1 by , 5 years ago
| Summary: | Redeclared model show icon of base class → Redeclared model shows icon of base class |
|---|
comment:2 by , 5 years ago
| Milestone: | 1.14.0 → 1.15.0 |
|---|
comment:3 by , 4 years ago
| Milestone: | 1.15.0 → 1.16.0 |
|---|
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
comment:4 by , 4 years ago
I have tried to use a re-declared icon the v1.16.0-dev.02 (64bit) release and redeclaration of model icons still seems to fail in this release.
I can really don't understand how people could use replaceable models in a "professional manner" if the user is not able to recognize a replaced model by a modified (and thus re-declared) model icon. In essence the graphical information provided by OMEdit is wrong for the model which contains a redeclared model. There is no visual difference between the base class and the derived class.
In our institute the diagrams as presented in OMedit are leading in the documentation of our models. Not being able to indicate in these diagrams which sub-models are actually used (the base class or the re-declared) is a major omission.
Will this defect be corrected in an update of the 1.16 release? Is there any known work around?
comment:5 by , 4 years ago
@h.j. since 2020 we have moved to a time-based release schedule. 1.16.0 is expected to be released in July, before the summer break.
We still have over 50 issues marked as blocker for 1.16.0, and it's obvious we will not be able to cope with all of them due to lack of resource, so we'll have to prioritize.
In general, we are well aware that OMC and OMEdit still have many shortcomings that need to be addressed to allow no-compromise professional use. This is a list of all issues we identified to reach that goal. Getting all of them fixed is our main goal for release 2.0.0.
Becoming a member of the Open Source Modelica Consortium would give you and your institute a means to have a say on development priorities.
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