Aparently _defaultDiagramType property doesn't wor

[jguerra]

Hi,
Just notice that defining _defaultDiagramType property doesn't work to me as it 's described in the hyperlink below.
http://www.sparxsystems.com/EAUserGuide/defining_child_diagram_types.htm

I created a new stereotype for the component metaclass, I defined the attribute _defaultDiagramType to "Component" to define this type of diagram when the element is made composite. Once installed the new technology file, the new element is "ok", but when i try to make it composite, nothing happen!. No diagram, no composite sign, nothing. If I take out the attribute and the new element is made composite, it creates the default diagram "CompositeStructure Diagram" and the composite thing on it as usual. Has anyone experienced a similar problem??

Thanks

[«Midnight»]

Try setting the value to "UML Structural::Composite" (without quotes, but with the space and bothcolons). Does that work?

[jguerra]

Yes, that's definitely works!. At least creates the CompositeStructure diagram. (The attribute doesn't break anything)
I changed your suggestion to this "UML Structural::Component" but it creates the Component Diagram outside of the composited element scope, not beneath of it as usually it does. Not too great btw .

Thanks
-added a comment-

[«Midnight»]

You should contact Sparx support about this. Provide an example of your profile. If it is a bug they can get working on the solution. If it is 'finger trouble' of some kind they are the ones who should be able to see where it is.

I've been through a few variations of this kind of thing. The only lessons I have learned are that the EA profile paradigm is very fragile with regards to how things are named - the exact formatting of everything counts - and that some errors are really bugs (but it is really difficult for users to determine which, given the limited documentation).

David

[jguerra]

Yeah, but I start to think it could be a bit evil problem.

Well, what i want to do is basically changing the default diagrams for custom stereotypes when you make composite an element. In my case, i want to change that behaviour in order to get a "Component Diagram" for a custom stereotype with the metaclass StateMachine. I tested out with another metaclass (Component) and it exactly behaves in the same way.

So back to the bussines, it seems to me that the problem could be, in somehow, related to the technology file, not sure. The element stereotyped is in a custom toolbox. When I drag the element from the toolbox to the diagram and I make it composite, it behaves in the way in described before, (Using your suggestion) I mean, the Component diagram shows up outside of the element scope. However, if I drag the native element (the metaclass of the stereotype) from the UML toolbox, and manually I select on it Properties -> stereotype and change the stereotype to my custom stereotype, and now I make it composite, it behaves in other way, the diagram is located beneath of it as usual but the diagram type is “CompositeStructure Diagram”. I changed _defaultDiagramType attribute to different other diagrams and it always comes out with the same diagram types’; “CompositeStructure Diagram”. Awesome!!. So, I start to think this attribute has got troubles !


Using EA 7.1 b828

[«Midnight»]

First and foremost, move to a non-beta build. There seem to be numerous problems in 832, so either 831 or wait for 833 (which might come out soon, it's been about a month or so).

As to the fragility of technology files, I've been through this at length with Sparx. They were able to resolve several of the issues I've brought up, but (IMHO) have not attacked the root problems. Some time ago we (Sparx and I) shelved this whole area while they worked on other priorities. They have not indicated to me that they have returned yet to this area.

Perhaps you (and any others who are experiencing problems with this area) would consider submitting detailed bug reports to Sparx. We need to tell them about the problems before they can solve them. It would also help them realize that these issues are important, and should have appropriate priority.

If you are registered EA users follow the Registered Users link near the top of any forum page and you'll see the appropriate link near the top of the page. You can attach an example file using the registered users bug report.

If you are not registered, or don't need to submit a report, you can use the Bug Report link below the Support link near the bottom of any forum page.

If any of you do report issues, please first start a forum thread and tell the rest of us. Quote the URL of the new forum thread in your bug report. That way the Sparxians can also participate in the discussion. If you hear back from Sparx on the issue, please post back to your thread to keep the rest of us in the loop.

David

[jguerra]

Yes, we try it to avoid them. The problem is build 832 has got a nice bug fixed for us, but it's got this another bug (see link below) and I had to go back to b828.  And yes i'll report the problem to Sparx, and I'll post the result of it.

http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1219339484/0#0

Regarding the issue, well we have a strong dependency on the technology file as we supplied a whole set of UML customization for our internal process. To be honest EA is great stuff, but at times we get this issues we can't get through it to get a nifty feature!!  

[«Midnight»]

I've been there.  

You have both my sympathy and empathy, but that doesn't help you at all. If only I could solve these problems for us...

[jguerra]

No worries !! This is not the end of the world. !!
Oops!  
Btw, I reported the issue to Sparx. Hopefully they will figure out whether or not is a bug.

and thanks for your sharp hints!, EA wouldn't be EA without the forum !!
Cheers

[Paolo F Cantoni]

and thanks for your sharp hints!, EA wouldn't be EA without the forum !!
Cheers

You said it!

Now, if only Sparx would listen...  

Paolo

[jguerra]

Hi
just let you know that Sparx fixed this bug and the fix will likely be available on the next build (833).

Cheers