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.

Topics - Uffe

Pages: 1 ... 16 17 [18] 19 20 21
Bugs and Issues / Lock indications not updated
« on: October 17, 2011, 05:51:37 pm »

We're using EA 9.1 in a DBMS repository, with the "Require Lock to Edit" policy. We have observed the following behaviour:
1) User A locks package P, including child packages.
2) User A sees P and its child packages as locked (blue exclamation).
2) User B selects P in the browser, and expands it.
3) User B sees P as locked (red exclamation), but not its child packages.

The desired behaviour would of course be that user B sees all child packages as locked as well.
Has anyone else observed this, and/or has any input?



Bugs and Issues / Size of Port in Component
« on: February 03, 2011, 02:49:57 am »

I'm working on a rather large and involved MDG Technology, and I'm bumping into a problem with Port sizes.

I create a Component (A) with a stereotype defined in one of my profiles, and then drop that Component onto a different Component (B), the resulting Port ends up huge - and I can't resize it.

I get the same result if I create the Port first and set its Property Type.

If I then change the Port's Property Type to a stereotype-less Component (C), the Port shrinks down to the regular size.

Anyone recognize this? Is there anything I can do to fix it?



Bugs and Issues / Connectors btw Component Instance Ports one-way
« on: November 24, 2010, 07:37:28 pm »

If you create two Components, each of which has a Port, and then create Instances of both Components (and display their Ports), you cannot draw a two-way Connector between the Ports: if you open the Connector Properties dialog, the Direction listbox is disabled.

This behaviour is consistent for all types of connector. If the connector Source or Target or both is a Port in an Instance, you cannot change the direction of the connector. I have also tested with Classes instead of Components; same result.
There is a workaround: draw the Connector between the two Instances, change its direction, and move the endpoints.

So my question is: is this a bug? I can't find support for this behaviour in the UML standard.



Bugs and Issues / MDG Technology: Tagged Value Types not imported
« on: September 17, 2009, 05:14:15 pm »

I've constructed a fairly large MDG Technology with a few dozen stereotypes, toolboxes, diagrams, code generation templates, and MDA transforms.
These all work when I import them (using Settings - MDG Technologies).

I have also defined a few Tagged Value Types, which are used in some of the stereotypes. These do not get imported with the MDG Technology.

I am definitely using the MDG Technology creation wizard correctly. I have checked and the type definitions are clearly present in the MDG XML file.
I have also verified that if I copy the definitions manually from the project where they're defined to the project where the MDG Technology is imported, the tags in the stereotypes which use them work instantly with no need for restart or refresh - so the definitions are syntactically correct (I use some Custom ones for things like six-digit strings etc).

Has anyone else observed this behaviour? Is there a simple fix?



Bugs and Issues / Tagged Value visibility
« on: August 20, 2009, 10:51:02 pm »

EA refuses to display my Tagged Values. I'm using 7.5.847 Ultimate.
I have checked and double-checked that the Tags option is checked in Feature Visibility. Furthermore, I have set up a completely separate project where the exact same thing works.

I have side-by-sided the Options, and there are no differences. The only difference between the projects is that the one where the tags aren't displayed is in MySQL, while the other is a simple .EAP.

It's not "Show Compartments - Tags" in the Diagram Properties either. That's unchecked in both.

Am I missing another option somewhere?


Bugs and Issues / Code Engineering: Out of Resources
« on: March 31, 2008, 10:51:36 pm »

If you reverse-engineer a large number of classes (like the JRE rt.jar) and ask for logical diagrams to be created, pretty soon you run into error messages due (presumably) to the fact that you run out of windows.

This in turn is because each diagram is created when needed, entities are added as they appear, but the diagram is not closed until it's been Layouted (alright, laid out), which is only done after all the entities have been imported.

Wouldn't it be better to (have the option to) close the diagram after each entity has been added, thus ensuring you never run into the too-many-windows problem? It might take longer, but you'll get there in the end.

Or is there some other workaround?


Uml Process / Packaging Components vs UML
« on: March 31, 2009, 06:25:44 am »
Hi there!

The new Packaging Components in 7.5 solve a number of problems for me, particularly relating to CM - a pedestrian subject of which the lofty ideals of the UML specification remain serenely aloof.

However, I would like to be able to counter the arguments from the UML purists (of which I am one, as it happens). So how does the Packaging Component relate to the UML elements? Specifically, how does it relate to Package and Component? Which characteristics does it take from which?



Uml Process / Component interface realization / usage lollipops
« on: February 09, 2009, 06:39:15 pm »

In 7.1, if you drew a Realization from a Component to an Interface, the Interface would also appear on the Component as a (non-selectable) "provided" lollipop. However, a <<use>> from a Component to an Interface would not result in a "required" lollipop.

I was hoping to see this in 7.5, but instead the automatic "provided" lollipop has been removed.

Can anyone straighten this out for me? Is there a way to get auto-lollipops in 7.5 (or auto-"required"-lollipops in 7.1)?



Hi guys,

I've got a set of doc templates with fragments. Some of these fragments issue SQL queries, some run scripts. Everything is deployed in an MDG Technology.

One of my users is having problems. The script-type fragments produce empty sections, and the output window shows the error
"Script Error - utomation [sic] server can't create object"

All the other sections come out correctly, and her model is structured as the templates require.

The error message indicates that the embedded script fails to run, presumably due to a problem with permissions or even missing libraries. Neither the user nor I have admin access to her machine as we are in a controlled IT environment, so what I need to know is what to tell the IT guys.

So: what libraries and permissions are required for EA to run the embedded script in a template fragment?

That is my question, and I'm hoping for one of the Sparxians to respond. So please please, if the usual suspects could not chime in with "you should do it a different way" or "that's EA for you" or "use my product instead" or anything along those lines just this once it would be very much appreciated.

Helpful hints are of course always welcome.



Automation Interface, Add-Ins and Tools / Profile: redefinition
« on: August 10, 2015, 06:41:47 pm »
Hello all,

One of the QuickLinker's suggested connectors from a stereotype to a metaclass is Redefinition. I can't find any documentation on this in the help file, and it doesn't seem to do anything different from the usual Extend.

My questions are:
1) What does it actually do?
2) Is there a way to achieve an actual redefinition of a metaclass?

Say I want to redefined Component to always include a tagged value just for funsies -- can I do that?



Hey everyone,

Got a lot of ducks here that need lining up.

I'm generating a .docx document using a script. The script and the templates are in an MDG Technology, and everything is working except one thing -- headers.

Adding headers to my regular templates does zip. EA ignores them. (Unless I put them in the template fragments, in which case some but not all of the fragments cause the header to appear in the middle of the page, some but not every time that fragment is invoked.)

I can get headers by creating a linked document, which has the header but is otherwise empty, and calling Document.InsertLinkedDocument(). OK good.

But. InsertLinkedDocument() takes a GUID, which it uses (it would appear) to look up the linked document in t_document -- in the target project. I want to include the header document in the MDG Technology.

I've tried creating a linked document template in the MDG Technology project's resources, and including that with the MDG Technology, but referring to its GUID doesn't work -- presumably that's not included in the XML file, or otherwise EA doesn't check the MDG Technology to look up the linked document.

Is there a way to get this to work? Or am I going to have to place a copy of the header document in each target project?



Hi all,

Is there some way to induce an instance type (eg Action) to display its classifier's diagram in a compartment or frame? There's no such selection in the context menu, but can I do it with a shape script?

I don't want to reuse the classifier in other diagrams, and I don't want to resort to diagram frames if I can help it. An Add-In is also out on this occasion. I'm still on EA 11, if that makes a difference.

Any ideas?



Automation Interface, Add-Ins and Tools / Shape size and selection box
« on: March 09, 2015, 10:56:36 pm »

I need to create a small element shape, about the same size as a Port but for a proper non-embedded element type.

I can draw a smaller rectangle in the main shape, but if I then select an element with that stereotype in a diagram the selection box fills out to the regular element size.

Is there some property I can set to change the actual size of the element shape script drawing canvas?



Automation Interface, Add-Ins and Tools / Gradients in subshapes
« on: March 04, 2015, 09:17:52 pm »
Hey everybody,

I've got this stereotype with an unpleasantly large number of tagged values, which I need to display in different boxes in a single shape. I'm using subshapes with rectangles in a top-down layout.

Problem is, the color gradient is applied separately in each subshape, so I end up with a very stripy-looking beast which is hard to read.

Is there a way around this?

I'm looking for something I can set in the shape script or the diagram definition, but I'm coming up empty. I can minimize the effect by using white as the fill color, but I can't make it go away completely.

I'm on 11.1.1112.



Automation Interface, Add-Ins and Tools / Icons in package contents
« on: January 28, 2015, 09:44:50 pm »

I'm working on an MDG Technology which includes stereotype icons. These show up as expected in the project browser and the toolbox, but if a package is displayed with its contents, the metaclass icons (Activity, Class, Object, etc) are used instead.

I wouldn't call this a bug necessarily, more of an oversight. Or is there a specific reason why the metaclass icons are used in package contents?

I'm using 1112 -- can anyone confirm this behaviour in EA 12?



Pages: 1 ... 16 17 [18] 19 20 21