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 - Paolo F Cantoni

Pages: 1 ... 61 62 [63] 64 65 ... 76
Bugs and Issues / setpen(getUserBorderColor(),getUserPenSize());
« on: September 04, 2008, 05:51:32 pm »
If all the other bugs I've reported this week weren't enough...

as does:


puts EA into a loop from which there may be no escape...  On my machine, I have to swtich it off as there's no way to get a response...


Take care,

Bugs and Issues / Association Class destroys "Composite"
« on: September 03, 2008, 04:55:17 pm »
Before I report this a (yet another) bug.  Is anybody else experiencing this?

If you have a class marked composite (and therefore with an associated diagram), when you make the class an AssociationClass via <vertex context menu>|Advanced[ch9658]|Association Class..., the composite setting is removed.

AND... (to add insult to injury)

when you put the "composite" setting back, the:
<vertex context menu>|Advanced[ch9658]|Unlink Class and Association,
disappears to be replace by:
<vertex context menu>|Advanced[ch9658]|Association Class...which menas you can't unlink the the two.  Never mind the fact that on the diagram, the rendering clearly shows it's an Association Class, the menus don't.


you discover that the Association won't select consistently!


since there isn't a means to unlink the Class from the Association from the <edge context menu>, you're left up the creek without the proverbial paddle!

This is EAUI of the purest form...  ::)

Now lest my fellow users think I'm being too harsh... I'm NOT finding these wierd bugs by rigourously testing this product.  I'm just trying to use it to do my real job - Data Architecture!  (By the way I'm using IE notation on the diagram)

EA SERIOUSLY reduces my productivity over what it should be!

If there was anything better than EA out there I'd switch in an instant!  It is a sad indictment on our industry...  (You might gather I've had a tough time with EA this week - I actually started to use it again...)

Using EA in spite of EA not because of it...  :'(

Caveat - it may be that this is happening ONLY on my machine (hence the question at the start).  In which case I plead that the observed behaviour is only slightly stranger than the already admitted inconsistencies in EA!

Bugs and Issues / Non standard multiplicity in IE notation
« on: September 02, 2008, 11:59:31 pm »
I believe it is the normal convention in Information engineering data modelling that if there is a non-standard multiplicity, that this is indicated in addition to the normal "crows-foot" glyph.  Thus: if the multiplicity is 2..*, then one would see:

Now, I think in this world of UML, we could gainfully use:

but not the current:

What do others think?

Bugs and Issues / Reflexive assoc wrong in IE notation
« on: August 29, 2008, 02:57:45 pm »
Reflexive associations display multiplicity even in IE notation

They shouldn't.  Non-reflexive ones don't.

The whole inconsistency thing between the rendering and manipluation of reflexive versus non-reflexive relationships is beyond a joke...  Why does it have to be so hard?

Create both a non-reflexive and a reflexive association.  
Place multiplicities on both.  
Change connector notation to Information Engineering.
Observe the multiplicity rendering inconsistency.
Bug reported.


Bugs and Issues / Wrapping for multiple stereotypes
« on: September 02, 2008, 11:41:16 am »
I'm now starting to use multiple stereotypes in big way.  There doesn't seem to be a way of forcing wrapping when the list of displayed stereotypes (particularly on an edge) gets long.  The list seems treated as a single unit.

I suggest treating the comma as a wrap point.

What do others think?  If there's agreement I'll submit a suggestion.


Bugs and Issues / Shape script kills edge notation rendering
« on: September 02, 2008, 12:12:11 am »
I've reported a bug that using a shape script destroys any alternate notation (for example: Information Engineering or IDEF1X) rendering for edges.

In thinking about possible solutions to this problem, it seemed to me that part of the problem is that there is no way to say to EA - please draw the native shape.

Hang on!  There's a drawing method: drawnativeshape(); but as the documetnation says: it's not supported for edge scripts.

I think that if it was implemented for edges, it could solve a number of problems.  In particular, drawnativeshape() in the end shapes (source or target) could draw the appropriate glyphs.

It seems to me this could seriously extend the utility of shape scripts.

What do others think?


Bugs and Issues / CENTER origin in shape script inconsistent
« on: August 29, 2008, 01:14:02 pm »
shape main

Watch the preview window.

Observe how the other values move the circle (which displays as an elipse YET ANOTHER BUG!), for all the values other than CENTER moves as expected.  CENTER behaves quite differently.

If the intent is to have a position outside rest, then it should have a special name NOT center.


Bugs and Issues / Opening the Model Views Window
« on: August 26, 2008, 11:29:40 am »
For EA Help:
The Model Views window enables you to encapsulate your model into the areas you are interested in. You display the window by selecting the Views | Model Views menu option.

1) On my EA 7.1 (build 832) I don't have a Views menu.

2) On my View menu there is no Model Views item.

Can anybody tell me how to open the Model Views window?  It seems like a neat idea - I just can't use it...


Bugs and Issues / NoteLink - inconsistent with other edge types
« on: February 26, 2008, 05:26:41 pm »
I'd like to link the Notes in one element to the text of the Notes in another.  I can't do that (although it would be a neat variant of the feature linked note technology).

So I create a "NoteLink" edge between two non-Notes.  Not your usual usage, I grant you, but EA lets me do it.  This allows us to write automation that will keep the origin "in step" with the destination.

I can do most things with this NoteLink - except set the stereotype.

I CAN do this by changing the type to something else, changing the stereotype and then changing back - but this is supremely tedious.

Couldn't we just let the NoteLink be consistent with everything else?

Please enable setting of the Properties Window for NoteLinks.  (even if a global setting - off by default).


Bugs and Issues / (825) Formatted text renders inconsistently
« on: February 13, 2008, 10:06:42 pm »
If you paste some new Formatted text (from one Formatted Text control) into another, it will render correctly in the control, but will expose the underlying HTML on the diagram.

Set up "Formatted Text" (including quotes) in one box and copy and past into another - the diagram should show: &quotFormatted Text&quot


[Edit - Got caught by EAUI!  The bug is really that setting formatted notes is NOT a diagram default.  So you HAVE to remember to set each one - absolutely, uneccesairly, tedious!]

Bugs and Issues / (825) Hyperlink Notes needs formatted text
« on: February 12, 2008, 11:09:15 pm »
Caption says it all.


Bugs and Issues / (825) Paste into lists fails
« on: February 13, 2008, 10:30:56 pm »
If you paste into a new Formatted text control, the pasted text will not go into the right place:

1)    Some text
2)    More <-paste here (text = Pasted Text)

1)    Some Text
More Pasted text


Bugs and Issues / BUG: Get the primary stereotype from one place
« on: February 12, 2008, 09:51:50 pm »
This one is a doozie!

In topic: [size=13] EAUI: Can't rename Resources [/size]  I comment on one of the worst kinds of design smells - more than one independent paths to ostensibly the same fact...

Here is another example.  I had requirements and I noticed that the Requirement Types is stored in the stereotype field of the t_object - and is rendered on the browser.  So I decided to see if I could create customized renderings for the various requirement types.

Success!  Add a stereotype to the Settings|UML...|UML Types|Stereotypes dialog and you get the rendering you need!

Great! Except...  (and with EA there is almost always an except...)

The next diagram, none of the stereotypes worked...

Why? Lots of checking values and stuff, reloading of diagrams, shutdown/restart of EA etc - all to no avail.

Then by chance I started using [Alt-G] (locate in browser) and I noticed that the stereotype shown in the browser changed from my stated one (obtained by opening the properties dialog) to "Functional" on the browser.  I opened the properties again - it's what I asked for (not "Functional").  How could this be? There are already numerous Browser update issues but this didn't "smell" like one.

Then I remembered that additional stereotypes are stored in t_xref.  A quick query and there is the culprit!  The stereotype in t_object was set to one value, the one in t_xref to another (the original "Functional").  Changing the stereotype using the Properties dialog for the Requirement didn't seem to fix it!

Creating a new requirement from scratch seemed to create a consistent (that work again) result in both places, but updating did not.

Unfortunately, it is the t_xref field that controls the stereotype rendering NOT the stereotype field in t_object!  (Verified by simple experiment)

The two locations MUST be synchronized correctly!

(in passing, we aren't ALLOWED to build software like (as bad as) this).

Geoffrey, you have no idea how much time is wasted trying to sort out why EA has the inconsistent behaviour it does.  Why not hire some more staff and actually fix the product?


Bugs and Issues / (825) Colour picker not context sensitive
« on: February 13, 2008, 06:55:39 pm »
The Colour Picker dialog in the new (825) Formatted Notes is not context sensitive.  That is, if you place it on a section of text, and open the colour picker, it does not highlight (preselect) the existing text colour.  This is contrary to the generally accepted behaviour of colour pickers isn't it?

If multiple colours are in the selected text, then no colour should be preselected.  Preferably, there should be some indication; but if the following UI is adopted, the resulting behaviour will allow one to deduce it without explicit indication.

If a custom colour is the selected text, it should be preselected.

If the colour is neither a standard colour (in the picker) nor a defined custom colour, then the Define Customer >> button should be activated and the colour appropriately selected in the RGB values.

Thoughts? Votes?

Bugs and Issues / ISS: Recovering vertical space in element
« on: February 12, 2008, 10:48:22 pm »
In the Feature Visibility [Ctrl+Shift+Y] dialog, under the When Resizing Elements group, there should be a check box [X] Recover Vertical Space.

This could be linked to an extension of the [Alt-Z] (say [Ctrl+Alt+Z]) which would allow the width of the element(s) to remain the same, but the vertical size adjusted to the minimum.

This is an issue and not just a suggestion because if you alter the number of characters in the Note to less than the current value, then only that number of character is display, but he vertical space is not recovered!  This also occurs when you edit the notes and remove text.

This is in contrast to adding text which automatically elongates the element vertically.


Pages: 1 ... 61 62 [63] 64 65 ... 76