#5400 closed defect (fixed)
Moving a model in package breaks other models
| Reported by: | massimo ceraolo | Owned by: | Per Östlund |
|---|---|---|---|
| Priority: | blocker | Milestone: | 1.14.0 |
| Component: | Interactive Environment | Version: | v1.14.0-dev-nightly |
| Keywords: | Cc: | Adrian Pop, Per Östlund |
Description (last modified by )
to reproduce the issue both mo files must be loaded and the txt file should be added in the OMEdit working directory.
Once both mo files are loaded
1) open myEVPkg.WithRecord.EVBasicMB.
2) Run this model -> everything it ok.
3) click on "Car", and move it downwards through ctrl+down arrow.
4) run again EVBasicMB -> it does not run anymore!
Tested with OM 1.14-dev-383
Attachments (4)
Change History (12)
by , 6 years ago
| Attachment: | AccBrake.txt added |
|---|
by , 6 years ago
| Attachment: | myEVpkg.mo added |
|---|
by , 6 years ago
| Attachment: | wbEHPTLib.mo added |
|---|
comment:1 by , 6 years ago
comment:2 by , 6 years ago
It is today's nightly build under linux.
The same issue is seen using the 1.13.1 version under windows.
comment:3 by , 6 years ago
| Cc: | added |
|---|---|
| Component: | OMEdit → Interactive Environment |
| Owner: | changed from to |
@casella my changes has nothing to do with moving of the model.
@ceraolo I looked at it very briefly. The problem is that moveClass API is somehow clearing the whole AST. A made a mos-script that shows the problem.
This is a very serious bug we need to fix this ASAP. I am making it a blocker.
by , 6 years ago
comment:4 by , 6 years ago
| Priority: | high → blocker |
|---|
follow-up: 6 comment:5 by , 6 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
@perost, can you have a look at this while @adrpo is busy with the new API?
comment:6 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:8 by , 4 years ago
| Description: | modified (diff) |
|---|
@ceraolo, I'm not sure about the version number, it seems the Linux one, which doesn't match the Windows one for some reason. Are you using the latest nightly? There were some fixes pushed in by @adeas31 two days ago on possibly related issues.