Package import/export - Bad Comparison issue.

[Paolo F Cantoni]

Call me naive, but I would have expected that if I did a comparison of a package immediately after export, it should be identical - apart from missing items due to externalities.  Similarly after an import.

For the same exported/imported file, it seems that there are differences in some layout details.  It looks like a comparison problem since on both export and import, the Model values are empty and the Baseline populated - which CAN'T be the case.  Also interestingly, the export and import have different sets of objects affected! PURE EAUI!

Reported,
Paolo

[qwerty]

I reported quite a number of bugs many years ago. It had been improved, but never got fixed completely. I simply stopped using that feature.

q.

[Paolo F Cantoni]

I reported quite a number of bugs many years ago. It had been improved, but never got fixed completely. I simply stopped using that feature.

q.

Yes,  I avoided the feature for many years, so it was a surprise that this should be still a problem.  Its NOT that hard to construct a Test Regime to validate that the round-trip works...

You may remember the battles (nearly a decade ago) over the straight round-trip of packages where our tests, on premises, would show issues with the process that Sparx were unable or unwilling to identify.  At the time we were developing models to the European EN50128 Railway Safety standard.  If our software didn't work - PEOPLE COULD DIE!  So we had to be sure that the models weren't corrupted by the transport process.

Paolo

[qwerty]

I worked many years for German Rail (DB) and later for Bombardier Transportation. I know what you're talking of. In the flight industry they us those expensive software variants (10k$ per license) for that reason.

q.