Messages

1

Automation Interface, Add-Ins and Tools / Re: Adding existing toolbox pages to extended diagram

« on: August 29, 2017, 09:49:41 am »

The Extended Requirements page contains a bunch of stereotyped Requirements, but they are not "UML::xxx".

EAREQ::FunctionalRequirement(UML::Requirement)

The rest follow the same pattern. If you get stuck, create one in an empty model and then look in t_xref for a definition like this

@STEREO;Name=FunctionalRequirement;FQName=EAREQ::FunctionalRequirement;@ENDSTEREO;

Thank you.  A real answer from someone who seems to have actually read the question.

2

Suggestions and Requests / Re: Ability to move the link of an association class

« on: August 29, 2017, 07:04:29 am »

If you want good semantics, you need to "roll your own MDG".

We mark our Associative Elements (including Association Classes) with a Tagged Value (IsAssociative) which, in turn, causes an Associative Glyph to appear on the Element.  This means that even if the association is not visible on the diagram, the Element is known to be Associative.  Over a decade ago, there was a discussion on the forum N-Ary Associations and Association Class.

You may find this useful.

Paolo

Interesting. I like the decoration idea.  Did you do this with an MDG or some sort of script?  Also, did you solve the problem of being able to see what two classes it was an association between?  The object model most likely allows you to find those classes, but you cannot see them in the properties editor of the association class itself.

3

Automation Interface, Add-Ins and Tools / Re: Adding existing toolbox pages to extended diagram

« on: August 29, 2017, 06:56:03 am »

You can type in the meta types manually if they are not present.

q.

Except I cannot, because the other requirements types seem to be extensions themselves, and are not UML::xxxx.  I know how to add UML default meta types to a tool box.  These seem to be in another namespace that is known only internally.

4

Automation Interface, Add-Ins and Tools / Re: Adding existing toolbox pages to extended diagram

« on: August 26, 2017, 09:45:29 am »

I did extend UML::Feature. What I want is the rest of the requirements tools available in the same tool box.

5

Automation Interface, Add-Ins and Tools / Adding existing toolbox pages to extended diagram

« on: August 26, 2017, 07:33:07 am »

I am creating a simple MDG to do some requirements modeling.  I wanted to extend "Requirement" to create a stereotype unique to our current problem, specifically to add a set of tagged values.  I really just want to add my new requirement type to the existing "Requirements" toolbox and diagram type. I believe that is not really possible, so I went ahead and created a tool box and diagram type for my MDG.  That all works fine.  But, I really want the "Extended Requirements", "Requirements Relationships" and "Patterns" pages you get when you create a UML::Requirements diagram. 

Is there any way to simply add those pages to my new diagram type/toolbox?  The Extended Requirements page contains a bunch of stereotyped Requirements, but they are not "UML::xxx". I have not been successful in creating a toolboxpage in my profile that adds those Built-in Types, because they are not Built-in Types.  I believe they are part of "Core Extensions" but I don't know how to address that MDG in my profile (since it is internal and not an XML file)

6

Suggestions and Requests / Re: Ability to move the link of an association class

« on: August 25, 2017, 02:50:01 am »

See figures on pp. 205/206 in the specs. The lozenge seems to be a placeholder for the connection point.

q.

In the 2.5 Beta it is on page 211.

As indicated (if it's the same diagram) the (n-ary) Association Lozenge is an AssociationClass in itself.  It should not be used as a substitute for the connection point of the (binary) AssociationClass virtual link (BTW, Uffe, there is a backing representation in the DB - but not as an arc of any kind).  These days, if you really want to have a "moveable feast" for the connection point, use a Notelink from the association to the AssociationClass.  This gives you a REAL arc which you can customise to your heart's content.

Paolo

Except that that is not optimal either, from the semantics point of view. 

When you look at the "links" of the association class, the association doesn't even show up.  So, from the UI you only know that it is an Associative Class when viewing the Diagram on which the association is displayed.  Not sure what it looks like in the object model, I haven't had to write an addin to use it.... yet.  But I want the proper semantics, not just a "nice diagram".

The modeling tool we were creating back in the day actually let the user create the association link separately.  Any class could become an associative class.  The association link itself had attributes that could be used to store information.

7

Suggestions and Requests / Ability to move the link of an association class

« on: August 23, 2017, 04:09:38 am »

The inability to move the link of the association class (the dotted link between the association and the class) is highly annoying.  It prevents the ability to make readable diagrams that use this highly useful UML element. On the contrary, the association diamond, which gives the desired behavior to move the link, is much less useful modeling-wise. 

8

Automation Interface, Add-Ins and Tools / Re: Out of memory while debugging in Visual Studio

« on: May 10, 2017, 03:44:35 am »

I have always had this problem when trying to launch EA from VS during debug.  I just attach to EA after it has launched.  Then debug works fine.

9

Bugs and Issues / Re: Shapescript vs Local diagram rendering

« on: May 10, 2017, 01:27:49 am »

My company tries to do things with color as well, no matter how much I tell them not to.

Color of model elements in a diagram is nice, but has no semantic value. It's not "part of the model".  You should always use stereotypes or tagged values when giving different elements different "meanings".   If you want to give color to stereotypes or tagged values for a visual effect, than that's fine, but never use color alone.

Your shape script is drawing based on stereotype or property (ie, tagged value), just as it should.  Use a tagged value to color your elements.

10

Bugs and Issues / Exclude Filters not working when trying to generate document

« on: April 05, 2017, 05:45:12 am »

I am trying to generate a document using the pre-existing filters in the Generate Documentation dialog. I want to exclude all <<trace>> relationships.  These should be Trace relationship, created using the Trace common tool.

When the "Generate Documentation" dialog appears, I select the "Data Modeling Report" template (or any other template really).  I then go to the "Exclude Filters" tab of the dialog and select the "Trace" connection under the "Exclude Connector Type" list.  Without closing the dialog, I navigate back to the "Generate" tab and select "Generate".  The report generates just fine. However, every single Trace relationship is included in the report.

How do I get the Exclude Filters to work?

11

Automation Interface, Add-Ins and Tools / Re: If-Or-Statement within Shape Scripts

« on: March 16, 2017, 09:36:39 am »

I believe what qwerty is saying is that you cannot do text or value comparisons in ShapeScript.  There is no "if ( a=1 )" syntax.  There is only "if (hasproperty(a))"

12

Automation Interface, Add-Ins and Tools / Re: Creating EA MDG Technology

« on: February 14, 2017, 03:18:00 am »

Well, even if there is something specific to a Port, the question would still remain for any metatype:  How do you create a box that sizes to the contained text?

13

Automation Interface, Add-Ins and Tools / Creating EA MDG Technology

« on: February 11, 2017, 10:55:25 am »

Hi,

I am creating an extension to EA using the MDG Tech helpers.  I want to create some stereotypes the extend existing elements, just like any other MDG.

I am having some problems getting shapes scripts to do what I want.  The issue at hand is that I want to stereotype the Port element.  I want pretty much what a port already is, but I want the name of the element contained inside of the shape and have the "port" resize accordingly.  I simply cannot figure out how to get the port to be anything other than its default size. I can get the text to appear "centered" in the box, but of course it extends to the left and right.

There has to be a way to get this to work, right?