Messages

1

Suggestions and Requests / Re: Multiple instances of element in diagram

« on: February 06, 2009, 06:21:54 pm »

And if you ever include it, please make it optional so I can configure EA to work the old way.

I guess I'd use it while documenting the dependencies of legacy code, but it would mean a lot of work. You would have to set the individual visibility of all connectors (and EA would have to save it per diagram and per instance) to make a diagram readable.

For planning and designing purposes I'd rather have a warning when I inadvertently drop an element a second time. And if a diagram gets so complicated I would need second instances, I'd rather stop it, have a cup of coffee, and think up a better structure.

2

Suggestions and Requests / Re: Multiple Diagrams

« on: May 08, 2008, 10:19:37 pm »

I didn't find the old threads either. Search for "diagrams" and you get swamped, search for "MDI" and you get nothing.

Anyway, it's been requested many times before, but Sparx seems reluctant to implement it. They're probably afraid of the synchronization issues they would have to face. When you change an element and it is visible in the current diagram, you will see the change immediately. When you switch to another diagram containing the same element, you will see the change as well.

But when has it been changed on the other diagram? When you changed the element, or when you switched to the diagram? Nobody knows but Sparx, but I guess it's the latter.

If you could see more than one diagram at a time, and the element were visible on all of them, you would get some funny flickering, and maybe would have to wait a while before EA reacted again. I guess it's something like that of which they are afraid. They just couldn't hide the time it takes to render a diagram in the diagram switching event anymore.

3

Suggestions and Requests / Re: Set label visibility for all connectors

« on: April 08, 2009, 08:23:00 pm »

Ah yes, the awful Geometry property. That would make a good feature request indeed: to wrap the values contained therein into nice integer properties. and the same for other strings like that.

It's been suggested before, though, to no avail.

4

Suggestions and Requests / Re: Set label visibility for all connectors

« on: April 08, 2009, 04:07:26 pm »

In the automation interface, DiagramLink.IsHidden should be the property you need (I've never tried it out, though).

5

Suggestions and Requests / Re: Any plans to add a Threat Modeling feature?

« on: October 18, 2010, 07:54:57 pm »

Sounds threatening...

6

Suggestions and Requests / Re: Feature req: Copy class Notes field to an inst

« on: August 26, 2010, 09:05:10 pm »

Maybe a new optional compartment for instance rendering to show the classifier's notes?

7

Suggestions and Requests / Re: How to modell exceptions

« on: April 28, 2010, 10:01:13 pm »

I haven't tested MDA transformation or report or code generation, but I'm pretty sure the Connector model works better there too.

I wouldn't be so sure about this, Uffe. In EA 7.5 there was no way to determine via code generation (or MDA) template or via API to which feature a connector is linked, and I don't see anything new in the current (EA online manual.

8

Suggestions and Requests / Re: How to modell exceptions

« on: April 28, 2010, 07:59:20 pm »

Instead of tagged values you could use the "link to element feature" feature which was introduced with EA 7.5:

- Draw a dependency from the class containing the operation to the exception class;
- Give the dependency a stereotype "throws";
- link the dependency source to the operation.

Then you can easily trace which exception classes are thrown (those which have "throws" dependencies in the links tab).

9

Suggestions and Requests / Re: Internal Transtions

« on: March 18, 2010, 05:11:01 pm »

You can get excactly what you want by adding an operation to a state. In the wikipedia example, open the "Operations" context menue for state "default", add an operation "send_lower_case_scan_code" and in the "Action" combo type "ANY_KEY".

10

Suggestions and Requests / Re: Code Template Framework: Attribute Constraints

« on: August 13, 2009, 10:43:56 pm »

But in the case of tagged values we can get at the various objects and collections.

Can we? What about tagged values on parameters?

11

Suggestions and Requests / Re: "Nesting" Compartment

« on: April 30, 2009, 12:40:48 am »

Yes, a nesting compartment would be excellent.

12

Suggestions and Requests / Re: Subversion Credentials

« on: July 15, 2009, 05:21:34 pm »

OK, but EA still hangs when e.g. you have changed your SVN password and forgot to log on before starting EA, which is definitely a bug.

13

Suggestions and Requests / Re: Repository node in Project browser

« on: July 11, 2009, 04:20:50 am »

There could be an option for showing it.

By the way, this reminds me of all the things which actually are UML elements and still do not show up in the project browser (like concurrent state regions or forks).

14

Suggestions and Requests / Re: Tracking changes to connectors

« on: May 22, 2009, 06:22:22 am »

If I needed an author field and such for connectors (or for attributes and operations, come to that), I would probably use tagged values for those, and I would ignore the fields supplied for elements and use an "author" tagged value for elements as well. Just to get some of the consistency which EA is lacking, and to unify e.g. the x-path expressions I would then need to extract the author of anything from xmi.

But of course it would be preferable if EA treated all entities in a consistent way.

15

Suggestions and Requests / Re: Tracking changes to connectors

« on: May 21, 2009, 02:50:02 am »

You could use tagged values to store your additional values.