BUG?: grey images after importing UML pofile (818)

[Mr. Sanders]

Hello,

I am creating an UML profile with new stereotypes in it.
Some of them have an image attribute where a jpg is assigned to it via a shape script e.g.

shape main{
image( "smiley.jpg", 0, 0, 400, 200);
}

When I import this UML profile in another EA project and use my custom stereotypes, the appearance of the elements is just a grey rectangle.

I have to do the following to get the images visible in the target project.

1. Add the image via Settings | Images.
2. Give the image the same id as in the UML profile.

But after this, the images are still grey.

3. Additionaly I have to close the EA and reopen the target project.

Than I have the images in my diagrams.

Now my questions:

I. It is nonsens, that in the target project where the UML profils is imported, the images have to be imported manually too and giving them the same names as in the profile.

The user can't know the images and their names.

How can I manage, that the images are importet automatically, when the profile is imported?

II. Is it a bug, that the images stay grey and I have to close the EA and restart it to get it visible?

Regards
Michael

[«Midnight»]

Michael,

This is almost certainly a bug. You should report it to Sparx using the usual best practice we use.

I have been working to isolate a closely related bug, having to do with shape scripts in a technology file. I'll be posting and reporting it in the next few days.

David

[KP]

What you need to do is build an MDG Technology ("Tools > Generate MDG Technology File" from the main menu) that incorporates your UML Profile and images in a single importable file. Full details in the help file or ask for further assistance...

[«Midnight»]

Neil,

I've done this as you directed - we've communicated on other channels regarding this - and still the shape scripts don't seem to take effect.

If I then import the profile - the same one I used to create the original MDG technology file - I need to open the stereotype dialog for a shape scripted element, open the edit box for the script - I do not need to make any changes - and exit the editor and save the stereotype. Suddenly, the script takes effect!

I'll be filing a bug report soon.

David

[jguerra]

Hi,

Has anyone an idea whether this issue has been fixed?

I bundled an image in a technology file for a brand new stereotype  which is using the image and when I apply the stereotype to my new element all what i got is a grey rectangle !!.

Thanks

Update: Using EA 7.1 b828

[«Midnight»]

You're several builds out of date - the current build, 833, just came out this week - so it might be worth retesting.

The above said, I've seen nothing in the release notes that would suggest this has been resolved. It was enough of an issue for add-ins that I went another way, and don't have time to test the EA implementation these days.

David

[jguerra]

Hi David,
Thanks again for your answer! Suppose we have similar constrains on time for testing releases ...

Anyway, just realized that the 833 was out. I tried it out and it didn't work either. I also went through the RNs and I suspect that this is not fixed yet. I suppose the work around is importing the images, but that's not acceptable for my case.

[«Midnight»]

Have you reported this as a bug? By that I mean have you reported the problem to Sparx rather than just mentioning it here, in a user forum? [It is good to mention it here of course, but the 'formal' bug report is the best way to bring these things to Sparx' attention.]

If not, click the Report a Bug link below the Support link near the bottom of any forum page. Fill out the form with the details. It would be a good idea to paste in a link to this thread as well. Should Sparx respond, please post back here to keep the rest of us in the loop.

If you are registered, you should perhaps fill out a different version of the bug report form; the registered user version lets you attach sample files to help Sparx diagnose the problem. If you send a project, remember to compress the file first. You'll find the registered users version by following the appropriate link just above the default bug report form.

[jguerra]

A possible work around for this it could also be exporting the stereotypes as reference data into a XML file. Import the data into a new project, and you will have then the full range of stereotypes available. The inconvenience is that you have two files to populate stuff, technology and reference data files.

btw, no I haven't reported this thing though the issue was spotted almost a year ago !!

[«Midnight»]

The reference data route is interesting, but has some limitations. For some users, one real show-stopper is the inability of EA to manipulate (load, transfer, etc.) reference data through automation.

FWIW...

Although I reported some of the issues in this thread almost a year ago, that was apparently not enough impetus to force (all of) them onto the fix list. If enough other users report these problems and associated feature requests, perhaps they will make the grade for upcoming builds, or perhaps for EA 7.5.

If we - that means not just me - make the reports and requests these things might be addressed. If we don't then Sparx has no real way of knowing what (really) needs to be done; we're unlikely to see progress any time soon if we stay silent.

David

[KP]

The reference data route is interesting, but has some limitations. For some users, one real show-stopper is the inability of EA to manipulate (load, transfer, etc.) reference data through automation.

Undocumented (and likely to remain so): Repository.CustomCommand("Repository","ImportRefData",sXML) where sXML is a string containing the reference data.

[«Midnight»]

Neil,

Is there a (possibly equally undocumented) variant to export the data?

David

[KP]

Neil,

Is there a (possibly equally undocumented) variant to export the data?

David

Afraid not: I've had a look through the source and there's nothing for exporting.

[«Midnight»]

So automation is still not a solution for 'real' transfer. It would only help if the reference data were (somehow) available for import.