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 ... 56 57 [58] 59 60 ... 73
Bugs and Issues / Reference data export: matrix profiles
« on: November 10, 2011, 10:43:10 pm »

I've got a couple of diagram matrix profiles defined in a project (visible in the Resources window), which I'd like to transfer to another one.
Problem is, when I try to export them (Project - Model Import/Export - Export Reference Data) I end up with an XML file which contains only the <RefData> tag - no actual contents.

Has anyone got any input?
I'm on 9.0.905 on XP SP3.



Bugs and Issues / Re: Strange lock behaviour
« on: October 28, 2011, 10:53:06 pm »
2-3) Locking is stored per element. The context menu just looks into the selected element to set the radio button to the opposite. So that seems logical.
Well, not quite. The context menu appears to be controlled not by the actual lock but by a client-internal cached lock state, which is not updated correctly when the same client manipulates the lock in a different way.

6) You can rename the model root without any lock!
Also worth a bug report, I think, but I haven't sent one. I did send one off regarding my OP; I have a 100+ user deployment here, and locking simply has to work.

Bugs and Issues / Strange lock behaviour
« on: October 17, 2011, 11:03:05 pm »

I am in a DBMS repository, with the "Require Lock to Edit" policy.
I am observing the following locking anomalies in 9.0.905:

1) If I have a diagram open when locking / unlocking its parent package, the "Delete Connector" menu option in the connector context menu is wrong. It remains available when I lock the package, and remains unavailable when I unlock it.
   The latter is an inconvenience, but the former is potentially dangerous.

2) If I apply a lock on a diagram from within the diagram itself (not the project browser), I can then add new elements even though the parent package is not locked (ie, I cannot right-click the package and Add an element).
   If I do this, I can then not delete the element again (requires package lock).

3) The in-diagram Apply / Release User Lock menu options replace one another. They seem not to check the current lock status, but instead to remember which one of them was called last.
   In other words, you can lock the diagram using the in-diagram menu, then unlock it in the browser, and then unlock it again in the in-diagram menu.

These all seem like bugs to me, but I can find no specific reference to them in the version history. Can anyone say whether they have been adressed in 9.1, or reported to Sparx?



Bugs and Issues / Re: Lock indications not updated
« on: October 17, 2011, 10:34:43 pm »
Yes, it makes sense for it to work that way since EA has no server of its own and the actual lock itself (in t_seclocks) does not remember whether it was applied recursively. Thought I'd check though. Thanks to you both.


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 / Re: Hyperlinks in NOTES (856) not working?
« on: February 04, 2011, 08:04:27 pm »
OK, I just realized that maybe when you said Notes fields, you meant Notes fields - not Notes themselves.  :-[

I tested this in 8.0 (864), and here's the scoop.

You can create a hyperlink inside a Note field, as above.
The link is not displayed as a link in a diagram, nor is it clickable.
If you switch on formatted Notes for the Element, the link is displayed properly, but is not clickable.
If you create a separate Note and link it to the Element's Note, again, the link is displayed properly, but is not clickable.

In other words, it doesn't work in 864.

Sorry about my confusion there.



Bugs and Issues / Re: Hyperlinks in NOTES (856) not working?
« on: February 04, 2011, 07:58:13 pm »

I'm using 8.0 (864), and it works there.
First off, you need to select the text in the Note, then bring up the link dialog - if you try to add the link without having any text selected, you end up with nothing (like you describe). This is because the link itself is not displayed, it needs a text label - pretty much like HTML.

Here's what a note with a "Web Site" link looks like in XMI:
Code: [Select]
<packagedElement xmi:type="uml:Package" xmi:id="EAPK_768A8BCF_8565_45e8_8321_E16FD320A811" name="Link in Note" visibility="public">
    <ownedComment xmi:type="uml:Comment" xmi:id="EAID_AA4CC489_85C0_4ecb_A20B_D26E2F1723D5"
     body="Some text <a href="$inet://"><font color="#0000ff"><u>and a link</u></font></a>."/>

This is a note with the text "Some text and a link.", where the "and a link" part covers an http link to

Hope that helps.



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 / Re: MDG Technology: Tagged Value Types not importe
« on: September 18, 2009, 04:53:13 am »
Well I'm pretty sure they're not imported-but-invisible, because if they were, wouldn't they still provide the functionality in the tags which used them?

Be that as it may, I've found the solution.

The whole Tagged Value Types option in the MDG Technology Creation Wizard is one big fat greasy red herring (being a Swede, I know all about these tasty little morsels).

What you need to do in order to get your Tagged Value Types across to your deployment environment is to do Export Reference Data - Property Types, drop the resulting file in a shared directory, then (in the deployment projects) select Import Reference Data - Shared File, and select the file.

This is not entirely dissimlar to the way EA is configured to look for MDG Technologies (under Settings), but there are some differences:
  • For MDG Technologies you specify a directory or a URL, for reference data it's a file and one or more Datasets within it;
  • With reference data, you can tell EA to confirm the import (EA will alert you when the imported datasets have changed);
  • Reference data settings are per project, MDG Technology configuration is per user
So there is a way around it, which is good. A consistent way of configuring these things would be even better.



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 / Re: Tagged Value visibility
« on: August 25, 2009, 12:52:16 am »
Same diagram types. I'm using EADDS in some diagrams, but I get the same results in plain vanilla Class and Component diagrams.
Also, not only are Tagged Values invisible and resistant to the Feature Visibility and Diagram options, the same goes for Constraints.

What the hey is going on?

The only clue I've got is that the project which is acting up is a multi-user project (MySQL). Can the settings become corrupted to the point where switching the display flags has no effect?

Bugs and Issues / Re: Tagged Value visibility
« on: August 21, 2009, 08:09:45 pm »
Nope, it's a simple package for which I've defined a stereotype in a Profile and assigned two Tagged Values. No shape script, nuthin'. The Profile is deployed as part of an MDG Technology.

I've tried opening the same model in 848, same result.

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 / Re: Code Engineering: Out of Resources
« on: April 01, 2008, 08:17:19 pm »
No, no discovery options. You can choose whether to create the diagrams, whether to synchronize or overwrite existing classes, and whether to import Private members, but that's it.

I've only got 2 GB RAM on this machine, maybe that's the problem.

Pages: 1 ... 56 57 [58] 59 60 ... 73