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 ... 5 6 [7] 8 9 ... 74
Bugs and Issues / TimeLine data
« on: October 16, 2017, 08:24:37 pm »
Hi all,

I'm trying to work out where EA stores data for a TimeLine.

The transitions are in RunState. Got that.
The states are in t_xref. Alright.

But where is the Timeline Range?

Seeing as the range is set to 0-100 if I drop a TimeLine onto a different diagram, I thought it might be in the diagram object. But it's not, even though the range is only set to default in the new diagram.

There seems to be an additional transition that corresponds to the range's lower value, but I can't find anything that represents the higher one. Nothing in PDATA.

Little help?


Hello boys and girls,

An operation parameter's multiplicity is stored in t_xref. The API Parameter class does not have a CustomProperties collection.
Is there a way to set a parameter's multiplicity through the API?



Uml Process / Action pins and instances of artifacts
« on: October 11, 2017, 07:16:50 pm »
Hi all,

EA lets me draw object flows between actions or action pins and instances of classes (objects). This is useful for when you want to show the object states explicitly in your activity diagram.

But if I make an instance of an artifact, EA says the requested connection is not UML compliant. Why is this?

I can work around it and force EA to accept this construction. That's not the question. The question is, why does UML say I should not make instances of artifacts and have them be the endpoints of object flows, like I can with instances of classes?


Hi all,

In a shape script, and without resorting to an Add-In, is it possible to retrieve the parameter type for an action pin?

The problem is that the action pin is an instance type, and its classifier is the corresponding activity parameter -- not the type (classifier) of that activity parameter. And there's no classifier.classifier.type property to be retrieved.


Automation Interface, Add-Ins and Tools / Re: Scripts submenus
« on: October 10, 2017, 07:21:49 pm »
Hi Guillaume,

This doesn't specifically address your issue, but with Add-Ins you can create sub-menus of arbitrary depth. So a workaround would be to rewrite your scripts in C# and deploy them as an Add-In. I think Geert has some thing that allows you to run scripts from an Add-In, which might reduce the effort required.

But I agree that there should be some form of grouping in the script context menus. At the moment, MDG Technology browser/diagram script groups get flattened. There should be one submenu for each script group in the MDG Technology.


Bugs and Issues / Re: Scripting engine seems to "cache" parts of scripts
« on: October 10, 2017, 07:10:31 pm »
Hi all,

I have observed some of this behaviour for a long time, but I can't speak to later versions than 11.1.
(Please stop ragging on V11. It's what I'm stuck with over here. :( )

The cross-project issue was new to me as I've always just restarted the client when I've encountered this. I have also not noticed any issues when running scripts from an MDG Technology, or just running previously completed scripts. I've only seen it during script development.

As to whether this makes EA unfit for enterprise deployment, I'd say no. In an enterprise deployment, you would discourage users from hacking their own scripts and test-driving them in a production environment: you'd have all scripting done centrally (or at least in a co-ordinated fashion), and you'd do it as software development and not as the equivalent of command-line fiddling.

But as I say, I see this as a problem with the script editor. If it's in the engine, then yeah, that's a bit of a showstopper.



Yes! That works! :)

Now unfortunately, if you select an attribute or operation in a diagram and right-click it, there's no Script sub-menu.

But you can select the feature first, then move the cursor to some other part of the element and right-click, and the script will pick up the selection. So that's close enough.



Hi Kent,

Just a couple pointers.

There are two options you may not have considered: model documents and the specification manager. Whether they'll be of much use in your scenario I couldn't say.

You can do a fair bit with template fragments, and also the element filters within the templates, but if you want complete control over the document generation process control flow you're going to have to script it.

Depending on your familiarity with the document generation facility in general, it may be less effort to write a script where you control everything than to construct a complex set of templates to achieve the same result.

But I'd hold off on any decision until the undisputed master of document generation weighs in: Geert Bellekens. I assume he's at the User Group meeting in Brussels today.


Hey guys,

Is there a way to retrieve the currently selected element feature (I mainly need attributes and operations) in a diagram?

The information is there, because you can right-click an operation and find it in the project browser -- but is it available in the API? All I can get out of the Diagram class is the selected connector and elements.

It's no, right? The answer is no?


Sure. Just set the package ID or parent ID (for packages).


Please post new topics in new threads. This one is two years old.

If you wish to get in touch with a specific individual, please use the PM feature.


I'm not aware of an API call that does this. I'd say the simplest way is to use Repository.SQLQuery() and parse the resulting XML data.

You need to match t_object.Object_Id or t_object.Classifier to t_diagramobjects.Object_ID, and t_diagramobjects.Diagram_ID to t_diagram.Diagram_ID.



Bugs and Issues / Re: hasProperty("concurrency")
« on: October 03, 2017, 11:47:29 pm »
Classes have Concurrency.

In the old GUI style, it's on the Details page of the properties dialog. There are four options: Sequential, Active, Guarded and Synchronous, expressed as radio buttons with none selected by default (but if you pick one, you can't then ever unselect it).


But there's no way to check for the element's 'direction' in a shape script -- it doesn't have its own property for retrieval, and it's not a tagged value.
This works...

Ah! So it's not that the property isn't available for retrieval, it's just that it isn't documented.

I can create stereotypes with shape scripts which set different colours -- but how do I specify that when using my «outpar» ActivityParameter stereotype toolbox item, an 'out' ActivityParameter should be created as opposed to an 'in' one which is the default?
In your profile, give your "ActivityParameter" metaclass element an attribute named "direction" with initial value "out". This appears to work, but it's possible it only works for properties named "direction".

OK. But now that you showed me how to get the shape script to work I can make a single stereotype «actpar» rather than four different ones, which is better because it means a modeller can't set the direction to conflict with the stereotype.

Cheers, KP!


Bugs and Issues / Re: IPv6 support in license server
« on: October 03, 2017, 07:44:05 pm »
OK. Thanks, Simon.


Pages: 1 ... 5 6 [7] 8 9 ... 74