Hi, for your issue #1 I'm afraid that is a known issue with XMI export/import - when you check "Export Alternate Images" in the XMI export dialog it doesn't actually export the images themselves into the XML file.
This can be worked around currently by loading each screen in SA, making it dirty (i.e. moving a control on the screen, then moving it back) and saving it - this will cause the diagram image to regenerated - alternatively if you right click on a screen and select "Properties" (to display the EA properties dialog) then cancel out of it, this will force the screen to be saved and the diagram image to be regenerated as well - which might make the operation less tedious.
We have another release due in mid January, we will attempt to introduce a feature which allows a user to regenerate all or some of the diagrams (much like generating a prototype) so that you can do this with a couple of mouse clicks after an XMI import to get everything back in sync - alternatively we may try to make this automatic, so diagrams are automatically regenerated after new screens have been detected in the EA model - automatic detection may still cause issues if the user doing the import at the time does not have SA installed.
For issue #2 are you able to email me an example XMI file that causes this to happen, so we can reproduce the issue in our own environment - it would be much appreciated, I haven't managed to find how to reproduce this myself as yet.
Also we haven't been able to reproduce issue #3, but we have noticed that when following these steps:
* Open EA project
* Edit SA screen
* Import XMI
* Edit SA screen that's been freshly imported (from the XMI)
That the designer will display the screen, but that the project explorer is out of sync and does not display all the new screens/packages which have been imported - we will endeavor to improve the way SA detects changes in the underlying EA model, but in the mean time you can click the "refresh" button on the project explorer toolbar to requery EA for the list of packages and screens to get it back in sync.
For your #3 issue, does it still crash if you close and reopen the project in EA, or only immediately after the import has been done. Depending on the sensitivity of the information, it would be very useful to us if we could get a copy of the:
* EA Project
* Your SA log file (which can normally be found in %ProgramFiles%\ScreenArchitect Limited\ScreenArchitect\logs\log.txt)
So we can attempt to reproduce your issues in house and see if the crash is an EA or SA related issue.
Alex Henderson
Lead Developer
Screen Architect Ltd.
email:
alex.henderson@screenarchitect.comweb: [
www.screenarchitect.com]
