OMEdit saves whole model hierarchy when changing a parameter and simulate afterwards

[Dietmar Winkler]

When using OMEdit 1.9.3+dev (r25570) it will save the whole library in a new single file per class structure if one edits a parameter and then starts another simulation run.

[Jan Kokert]

I observe similar problems. Saving files which define a package creates also a new folder, which is not the case for Dymola. It would be very nice, if all such editing issues (also #2905) would be fixed. Thanks!
BR Jan

[Dietmar Winkler]

sjoelund.se pointed out to me that there is the option "save class before simulation" that can be deactivated (on by default) in order to avoid this. Since OMEdit does not simply save the class but saves it in a different format (one class per file) than the original library format I would suggest to change the default to "unticked" to not mess with users libraries.

So the disabled options kind of helps but does not solve change of "save format" problem.

[Adeel Asghar]

The only reason to have "save class before simulation" is to avoid users data loss and it should be enabled by default so that if OMEdit crash during simulation the user data is not lost. However, we should fix saving issues which is very important. There is already a ticket about it #3179 so I am closing this one.