Messages

1

Uml Process / Re: Activity Diagram : Switch case

« on: October 29, 2008, 02:04:17 am »

What I use for switches is the regular Decision, with a <<switch>> stereotype name the choice after the switch var/object.

That done, the actual cases can be created using regular guards.

If you don't need, or don't want to use the stereotype, I think it is acceptable to put a Switch(ObjectName) on the name of the choice, as long as your team is ok with it.

2

Automation Interface, Add-Ins and Tools / Default line style

« on: May 18, 2013, 03:42:44 am »

Greetings.

Is it possible to spcify a default line style for a custom connector stereotype?

Are there any properties that I can set on the profile diagram elements to achieve this?

3

Automation Interface, Add-Ins and Tools / Re: True Nesting Connector

« on: September 29, 2010, 11:28:46 pm »

But this notation is for the automation interfaces, is it not? Is it possible to achieve the same results in scripts? If so, could someone post a small example?

TIA

Marcelo

4

Automation Interface, Add-Ins and Tools / Re: True Nesting Connector

« on: September 29, 2010, 11:40:55 am »

Thanks for both your replies, Paolo,

But regarding this topic, how do I do that? I mean, how do I go and set the parent of an object through script?

5

Automation Interface, Add-Ins and Tools / True Nesting Connector

« on: September 29, 2010, 02:06:25 am »

Is there a way, via script or via addin, for a custom connector to make the target element nest inside the source?

I'd like to have a custom connector that, when dragged from a source element  to target element, would move the target inside the source, setting the parent property of the target element to the source and updating the project hierarchy accordingly.

I've seen something like that in the SysML video and would like to know how to repplicate this in my customization.

TIA

Marcelo

6

Automation Interface, Add-Ins and Tools / Strange behavior in shapescript

« on: September 29, 2010, 02:18:22 am »

Hi there. Below are two very simple and very similar stereotypes created for our customization, both extending the Object metaclass:

stereotype-> output

shape main
{
      SetFillColor(150,200,255);
      DrawNativeShape();      
}

stereotype-> input

shape main
{
      SetFillColor(80,200,70);
      DrawNativeShape();      
}

The only problem is: the first one displays correctly, a nice blue object.

The second displays only when I create the object with the stereotype.

If I close the diagram and open it again, it reverts to the default shape.

And I've seen the same thing happen with at the least 3 other stereotypes I created, all of which include the DrawNativeShape();      command.

And the strange thing is that in all cases, there are a few stereotypes that work and a few that don't.

Is this related to the name? If so, is there a list of names that should be avoided?

TIA

Marcelo

7

Automation Interface, Add-Ins and Tools / Re: Shape width and other attributes

« on: January 27, 2010, 04:47:08 am »

Hi there.

I was stuck with this one for quite some time and found the following solutions:

1- You can set the scalable attribute to false, and have the units of the drawing methods behave like absolute pixel units.

2- If you need the shape to scale, you can export the profile checking the Element Size checkbox. If you do this, the elements will be sized after the size of the stereotypes on the profile diagram.

The only problem is that, if you use this second approach, there's usually a limit to how small you can scale the stereotype element... to circumvent this, you need to go to the diagram properties and uncheck all element feature visibility checkboxes, or you need to change the auto-size behavior of the elements.

Either way, you'll be able to resize your stereotypes and, when you drop the elements from the toolbar, they will have the same size they had when you defined the profile.

There was a third option, setting the width and the height on the stereotype attributes, but I don't remember what were the attribute names.

Hope this helps.

Marcelo

8

Automation Interface, Add-Ins and Tools / Toolbox profiles

« on: January 27, 2010, 12:42:04 am »

Hi there.

Here I am again at a new job and with another chance to play with EA and UML Profiles.

I am building a MDG technology to create some standards for our projects, and I stumbled on some issues while diggin my way through it:

From all the toolboxPage attributes described on the manual, only the isCollapsed is working for me. The other two I'v tried (isCommon and imagesOnly) are ignored by EA.

So my main question is: How do I set these attributes so that they are recognized by EA?

Also, the manual says that in order to give a title and a hint (tooltip?) to a toolbox page, I should enter them on the notes fields, in the following format:

Alias=Something;Notes=Something;

But this is not correct: The only way I found to make it work was to put the whole hint in the notes fields and the alias on the Alias field of the stereotype class. Maybe this should be updated on the manual.

Right now we're at build 845. I've already requested the responsible department to update, but this may take a while.

Thanks in advance,

Marcelo

9

Automation Interface, Add-Ins and Tools / Re: Resizing objects

« on: November 08, 2008, 03:41:31 am »

7.1.831

The old project was developed under 7.0 (don't know the build).

Has this behavior been corrected on the last build?

10

Automation Interface, Add-Ins and Tools / Re: Resizing objects

« on: November 07, 2008, 06:03:10 am »

One more thing:

Just opened an old project with stereotypes for ports and, as soon as I click them, they blow up to about 100x100 in size, and just won't resize back!

This project was created with 7.0 or 7.1, I don't remember.

11

Automation Interface, Add-Ins and Tools / Resizing objects

« on: October 31, 2008, 02:50:17 am »

Hi there.

I've made an add-in that can read method info from a type in an assembly and create activities and activity parameters for the methods of this type.

All is working fine, except for one small problem:

I am using a custom stereotype for the parameters, with shapescript, and when I drag the activity into a diagram, the parameters are huge!

I tried to set the _sizeX and _sizeY, but to no use... is there something that needs to be set on the metaclass in order to correct this?

This is not a big deal, since as soon as I click them, they go back to the normal size, but I'd like to be able to create them with the right size.

Also, once I add objects to the diagram, is thre a way for me to tell the diagram to execute the Auto Layout command?

12

Automation Interface, Add-Ins and Tools / Re: UML Profile - Archimate

« on: October 30, 2008, 02:37:29 am »

One more thing: I was reading the ArchiMate profile proposition, and I understood a little better why they propose to extend such low level classes as Element and Relationship: it appears that these classes introduce some attributes that will be inherited by the more specialized ones.

If this is the case, you can create a Relation stereotype, which will have the base attributes. This stereotype will not extend anything, and you can even mark it as an abstract class.

Later on, when you create concrete relations, you will have them extend the proper metaclasses, so that they inherit the behaviors and validation rules, and make them inherit from (specialize) the abstract Relation class you created earlier, to make them inherit the desired attributes.

Hope this helps.

13

Automation Interface, Add-Ins and Tools / Re: UML Profile - Archimate

« on: October 30, 2008, 02:26:07 am »

Element, Model and Relationship are all too abstract for you to extend through EA's stereotypes.

To create a profile out of these, you would need to provide not only the shape scripts, but the whole metamodel, including which elements accept which connectors under which circumstances,  etc.

So, to cut it short, you would do better (and a lot faster) by extending the closest elements, connectors and diagrams to each of the corresponding items on your desired profile.

And, about connectors, since you probably will be crating some new ones, which may not adhere to standard UML connection rules, my advice is for you to extend these from the Dependency connector, since it is by far the most flexible of them all.

14

Automation Interface, Add-Ins and Tools / Re: Show icon if notes are filled

« on: October 29, 2008, 10:10:20 pm »

Simon,

Are decoration scripts the ones treated on the "Show stereotype icons" option?

Could you give me an example of one such example?

15

Automation Interface, Add-Ins and Tools / Re: A few more about profiles and MDG's

« on: October 29, 2008, 03:37:53 am »

There is btw a good reason why some relations are not allowed by EA and this is called "consistency". If everything is available to be related anything else without rules then you will soon come to a point of confusion.

Agreed! That's why I want to edit the rules, not disable them! And even if I do this, it would not be a global change, but only in a very specific scenario, where I need to use elements from more than one diagram type in a customized diagram.

I honestly don't understand why the statemachine generates trigger objects that can't be linked to anything, except thorugh dependencies.

The basic use I have for triggers in my process is to show, in an activity diagram, where the events that cause state transitions are actually triggered.

I'd be happy to use regular events from the activity toolbox, but they cannot be selected on the transition event drop-down.