Opened 7 years ago
Closed 6 years ago
#4595 closed defect (fixed)
Reordering models in a package has no permanent effect
Reported by: | Francesco Casella | Owned by: | Adrian Pop |
---|---|---|---|
Priority: | blocker | Milestone: | 1.14.0 |
Component: | Interactive Environment | Version: | |
Keywords: | Cc: |
Description
Open the attached P package. Browse to P.Q, select M2, then press Ctrl-Up to shift M2 before M1. Select P.Q and save.
Nothing happens to package.order, so the reordering is lost when the package is reloaded later on from disk.
Attachments (3)
Change History (9)
by , 7 years ago
by , 7 years ago
comment:1 by , 7 years ago
Component: | OMEdit → Interactive Environment |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 7 years ago
Owner: | changed from | to
---|
@adrpo, can you please fix this once replaceable is in place?
comment:3 by , 6 years ago
Priority: | critical → blocker |
---|
As noted in comment:1, the problem does not depend on having packages in separate files, in fact I have the same issue with model contained in sub-packages where the master package is contained in a single file.
To reproduce:
- open the attached TestMovePackage.mo
- open packages A and B
- move M1 before M2
- save
- unload the package
- reload the package
- the models M1 and M2 are still in the wrong order
by , 6 years ago
Attachment: | TestMovePackage.mo added |
---|
comment:4 by , 6 years ago
Summary: | Reordering models in a package which are saved as separate files has no permanent effect → Reordering models in a package has no permanent effect |
---|
comment:6 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
The problem is with
moveClass
API. I have slightly updated your example to show the problem.moveClass
API does work fine for sub classes of a top level package but doesn't work for sub classes of sub packages.Inside
P1.zip
there is aP1.mos
script file which shows the problem.Note that the sub class
P1.N2
moves correctly butP1.Q.M2
does not.