OMEdit scrambles up package directory structure

[Francesco Casella]

Please consider the attached test package. It contains a directory named Test, which contains package.mo, package.order, A.mo and B.mo (two sub-packages).

OMEdit opens it correctly. However, as soon as I modify something within package A (e.g., add a package constant definition), it does the following weird things:

• it creates two directories Test/A and Test/B
• it saves Test/A/package.mo and Test/B/package.mo with the content of the packages (including modifications)
• it keeps the old Test/A.mo and Test/B.mo files
• it complains that classes A and B are defined in multiple files

The intended behaviour should be

• if a package within Test is modified, the modifications should be applied to the existing files
• if a new package is added to Test (e.g. Test.C), the user should be given a choice between
  • adding it to package.mo
  • adding it as C.mo
  • adding a directory Test/C and then a file package.mo there

[Francesco Casella]

Test files

[Adeel Asghar]

Isn't it same as #3179.

[Francesco Casella]

It is, in fact I looked for something similar in the database but did not use the right search keywords.

I'll attach the test case there.

[Francesco Casella]

I thought better, the two are related, but are not the same. I am not complaining about the effects of automatic saving, I complain about the effects of intentionally saving the modifications.

[Adeel Asghar]

This issue has now been fixed in a development branch ​https://github.com/adeas31/OMEdit/tree/indentation for OpenModelica 1.9.4 final release.

[Adeel Asghar]

The fix is now available via the nightly build.

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Milestone renamed