Opened 6 years ago
Last modified 3 years ago
#5312 assigned defect
OMEdit does not handle final parameter bindings properly
| Reported by: | Francesco Casella | Owned by: | Adrian Pop |
|---|---|---|---|
| Priority: | high | Milestone: | |
| Component: | NF API | Version: | v1.14.0-dev-nightly |
| Keywords: | Cc: | Andrea Bartolini |
Description
Please consider the attached test package. There are currently three issues with OMEdit related to the final prefix.
- If you open model B, display the graphic view, and double-click on
a, you can't set/unset thefinalattribute onp1
- If you open model
Cand double-click ona, you still see parameterp1, which shouldn't be the case, as it is modified with afinalprefix in the ancestor modelB
- If you then open model
B, change the value ofp1in the GUI, and save the model, thefinalprefix is actually removed from the code
OMEdit should allow to set/unset the final prefix when setting parameter values, and should also consider the final prefix in ancestor classes when deciding whether or not to display the parameter in the parameter window.
Attachments (1)
Change History (7)
by , 6 years ago
comment:1 by , 6 years ago
| Summary: | OMEdit does not handle final annotations properly → OMEdit does not handle final parameter bindings properly |
|---|
comment:2 by , 5 years ago
| Component: | OMEdit → NF API |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
comment:3 by , 5 years ago
| Milestone: | 1.14.0 → 1.16.0 |
|---|
comment:5 by , 4 years ago
| Milestone: | 1.17.0 → 1.18.0 |
|---|
Retargeted to 1.18.0 because of 1.17.0 timed release.
Note:
See TracTickets
for help on using tickets.
Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0