Opened 7 years ago
Closed 3 years ago
#4469 closed defect (fixed)
OMEdit does not update diagrams of derived classes
| Reported by: | ceraolo | Owned by: | adeas31 |
|---|---|---|---|
| Priority: | high | Milestone: | 1.18.0 |
| Component: | OMEdit | Version: | |
| Keywords: | Cc: |
Description (last modified by ceraolo)
If I rename a partial class submodel, the inheriting class does not show the submodel as renamed, but works.
Using the attached TestRename:
1) rename in PartialIce from the diagram view toPowW into toPowW0; save file
2) look at IceT (that uses PartialIce): toPowW is not renamed.
3) run TestIceT (that uses IceT) => it works!
I'm not totally sure, but in addition to not updating the model name in inherited models, something more serious is done by OMEdit in such cases. This morning, when doing something similar, I ended up with a corrupted package. But I can not replicate this.
Attachments (1)
Change History (10)
comment:1 Changed 7 years ago by ceraolo
- Description modified (diff)
comment:2 Changed 7 years ago by adeas31
- Milestone changed from 1.12.0 to 1.13.0
Changed 7 years ago by ceraolo
comment:3 Changed 7 years ago by ceraolo
comment:4 Changed 6 years ago by casella
- Milestone changed from 1.13.0 to 1.14.0
Rescheduled to 1.14.0 after 1.13.0 releasee
comment:5 Changed 5 years ago by casella
- Milestone changed from 1.14.0 to 1.16.0
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
comment:6 Changed 4 years ago by casella
- Summary changed from improper OMEdit behaviour when renaming partial classes' models to OMEdit does not update diagrams of derived classes
comment:7 Changed 4 years ago by casella
- Milestone changed from 1.16.0 to 1.17.0
Retargeted to 1.17.0 after 1.16.0 release
comment:8 Changed 4 years ago by casella
- Milestone changed from 1.17.0 to 1.18.0
Retargeted to 1.18.0 because of 1.17.0 timed release.
comment:9 Changed 3 years ago by adeas31
- Resolution set to fixed
- Status changed from new to closed
Fixed with PR#7453.
I checked with 1.12 beta2 and the issue is still there.
BTW, It seems that I forgot to add the test case, that I enclose now.
For me it is a bug, and should be fixed before 1.12 official release. Maybe this is rather simple and was not addressed earlier because the lack of the supporting file.