Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Uffe

Pages: 1 2 3 [4] 5 6 ... 85
Hi everybody,

The quick linker definition format allows you to specify "captions" or menu item labels, in columns K and L.

It would be useful to be able to use macros which resolve to the source/target element names, eg #SRCNAME#.
The macros should honour the "Use Alias if Available" option in the diagram.



Hi all,

It would be useful to be able to force EA to open a particular page of the property dialog by default for a stereotyped element.

Is there a special attribute that can be set, or some other way to achieve this?

I'm thinking in particular of the custom tagged value page that EA creates. When you're designing stereotypes which are essentially just placeholders for a specific set of tagged values, having that page opened automatically on double-click would be a small but valuable time saver.



General Board / Re: Glossary plural terms
« on: May 09, 2018, 12:27:28 am »
And, another question, would it be possible to realise this in an add-in? That is, does EA call an overloadable function before a glossary look up and before highlighting terms?
Unfortunately not. There are callbacks which can catch the creation / deletion of a glossary term, but the lookup and highlighting are EA-internal.


I shouldn't lean in too much without testing, but refresh is to update a collection.
I know, but it's implemented by other classes as well, and the user guide (as quoted in my first post) explicitly states that you need to Refresh() the Element itself after adding attributes.

Well, I just ran your script and it worked with NO issues.

.... and that's the end of this argument. :)


General Board / Re: Glossary plural terms
« on: May 07, 2018, 07:53:21 pm »
Probably not too many of those, but enough to be annoying?
With this kind of function, you generally need a very low error rate (less than 1%) for it to be considered acceptable.

In a scenario where the glossary is used on a broad front and the models are well-described, there will easily be half a dozen glossary highlights in any given notes field. With an error rate of, say, 5%, this means you'll find an incorrect glossary highlight every four or five elements you look at. Granted, not every highlight will be a plural form, but if you throw in participles, tenses, and a few other fun things along those lines it very quickly breaks down completely.

My point is that guesswork is not going to be good enough for this. What is needed is the ability to use a proper dictionary (which provides forms of words, not just their respective meanings) in conjunction with the glossary. The users can then select the appropriate dictionary for their language and culture.


Suggestions and Requests / "New Project" in EA 14
« on: May 04, 2018, 06:15:48 pm »
Hi all,

The "New Project" function opens a dialog where you can select file type:
  • Enterprise Architect Project (*.eapx)
  • Enterprise Architect Project (*.eap)
  • Enterprise Architect Project (*.feap)
.eapx is new, the two others were in 13 as well.

The problem with this is that there's no explanation of what the different choices entail. A better list would be
  • Enterprise Architect Project / JET 4 (*.eapx)
  • Enterprise Architect Project / JET 3 (*.eap)
  • Enterprise Architect Project / Firebird (*.feap)

The "New Project" menu item should also be reworked so that it contains a submenu with items for the three file types. If you click the "New Project" item, the current dialog should be displayed, but if you point without clicking, the submenu should be expanded.


Hello Steen,

It's certainly possible to write a script that updates a set of elements with their position in the tree (you don't specify if you're just after the depth or the within-package order as well, but one isn't any harder than the other), but the problem with scripts is always that you have to remember to run them.

If you write an Add-In instead, you can update the elements automatically when they're created or updated, or even move them if they're placed in the wrong location -- and of course inform the modeller that you've done so, otherwise they'll think it's spöking. :)


Hello, and welcome to the forum.

Please note we're all EA users, not Sparx employees. Well, most of us anyway.

There is one feature that you might be able to tweak to get something like what you're after: Kanban diagrams. With a diagram in Kanban mode, you specify columns based on some element property (usually its Status, but IIRC you can use tagged values as well). When you subsequently drop elements onto the diagram, EA places them automatically.

The sticking thing, no. EA doesn't do that.

The only place I know where EA auto-generates diagrams is in source code import. But it's probably not worth it for you to define a language to match your import data in order to get EA to generate these diagrams. But if you want to give it a try, take a look at the grammar framework.



Yes, but he's refreshing the Collection, not the Element. According to the API documentation, you need to refresh the element after adding attributes.


I think you need to
as well.

Quote from: User Guide link=
Notes: Refreshes the element features in the Project Browser.

Usually called after adding or deleting attributes or methods, when the user interface is required to be updated as well.


Bugs and Issues / Re: DocumentElement fails for certain users
« on: May 03, 2018, 06:42:43 pm »
We have now traced this issue to an incompatibility between EA 13.5 and the TabletInputService installed on Lenovo ThinkPad T70S. This service controls the laptop's touch screen, and disabling it allows the script to run without crashing.

Why this should be I've no idea. But it worked with EA 11.1.


Bugs and Issues / Formatting on v14 Recent Features page
« on: May 03, 2018, 01:36:55 am »

I'm looking at the long list of features, fixes and tweaks in v14, and the formatting is off in some places which makes the page hard to read. Under 1400 "Execuable Statemachines" (sic) there's a bunch of stuff that's got nothing to do with state machines, and in that section as well as others (BPSim for one), all the bullets have been placed on the top level rather than the intended indented ones. I'm sure there are other similar issues on that page.

Completely boring, I know, but it would really be helpful if this could be fixed.


Bugs and Issues / Re: RefGUIDList tag: field too small
« on: May 02, 2018, 07:45:21 pm »

If I use the tagged value connector, the resulting technology does not include a tagged value type definition. So when my stereotype's tagged value runs out of space, I can't just create another identical tagged value -- there's no such tagged value type to choose in the dropdown.

I realize that every implementation has limitations, but conceptually I think if I specify a multiplicity as 0..* and EA implements that as 0..6 then that falls somewhat short of what I would consider reasonable expectations. 6 is, after all, << 32767 (the max length of EA's Collections, which determines the maximum number of elements in a package, connectors to/from an element, etc). Or to put it another way, when programming I don't expect to be able to create an array of infinite length, but if the compiler caps all specified array lengths at six, I would consider that compiler broken.

So if there's no way to achieve a single RefGUIDList tagged value with more than six entries, I would suggest that RefGUIDList should be redesigned based on <memo> tagged values. At the very very least, the user guide should be updated to reflect the max-six-entries limitation.


+1, and also for the return type of operations.


Bugs and Issues / RefGUIDList tag: field too small
« on: April 27, 2018, 11:29:25 pm »
Hi all,

I'm working with a profile where I've got a tagged value connector from one stereotype to another, with the target role multiplicity set to 0..*.
This is the equivalent of creating a RefGUIDList tagged value type.

The problem is that, after I've generated the MDG Technology, if I select more than six elements I get an error dialog saying

DAO.Field [3163]
The field is too small to accept the amount of data you attempted to add. Try inserting or pasting less data.

This is obviously because a GUID is 38 characters, which means a list of six GUIDs requires 233 characters, and with a maximum of 255 characters in the field another list entry won't fit.

The 255-character tagged value limit can be normally worked around with a <memo> value. So here's the question: is there a way of combining <memo> and RefGUIDList?

I tried creating a tagged value with the same name as an attribute in my stereotype, but that didn't work. I also tried manually editing the profile XML data to force the contents of a <memo> tagged value type into the RefGUIDList tag definition, but no luck.

Anyone else?


Pages: 1 2 3 [4] 5 6 ... 85