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 ... 78
Bugs and Issues / Find in Browser; UI Change - 7.5
« on: February 16, 2009, 05:02:28 pm »
Previously, the "Find in Browser" functionality was a bit defective in that it didn't tell you when it didn't find anything.

However, the observant among us may have noticed that the status bar held the found item in the browser if it did, in fact, find something.

This was useful because you didn't actually have to go to a potentially "deep" (and therefore requiring a scroll to actually see the found item) browser entry and could therefore more quickly get to the item you were REALLY trying to find.  (I'll say nothing about the ACTUAL search functionality at this time - suffice to say a bit of EAUI).

The problem is that with 7.5 (unless it's peculiar to my machine) - the found item is NOT displayed on the status bar.

Before I report this as a bug, can anyone confirm the same loss of functionality?

In any event, couldn't 7.5 be the point at which there is some "help" to the users who have to use this functionality to locate entries in complex models and report the name of the found item or the not found message in the dialog itself?


Bugs and Issues / Can't Reset unknown DBMS type
« on: January 07, 2009, 06:31:10 pm »
If the DB is not set (or not recognized) on the package when reverse engineering a DB, the DB displayed in the Database Dropdown for a table is set to null.  However, there is no option on the Reset DBMS Options to change from a current NULL DBMS to something else...

Now, if the DB is NOT set, then you can't set the Foreign Keys (reasonable enough).  However, since you can't reset the DBMS - you're snookered...

The corresponding Code Language dialog has the <All> entry - which DOES allow language resetting from Null...


Bugs and Issues / Association Name not displayed if Foreign Key
« on: January 07, 2009, 06:23:19 pm »
If you have an edge between two tables and there is a Foreign Key Constraint, the Edge Name is NOT displayed.  This is because Foreign Key constraint field mapping is displayed in that label (Middle Top).  If no Foreign Key is yet defined, the Edge Name is displayed.

This is inconsistent with other uses.  The Foreign Key constraint could be displayed in the Middle Bottom label and that would allow the Edge Name to be consistently displayed in the Middle Top label.

NOTE: if you reverse engineer a Foreign key relationship, the Middle bottom label is blank.  If you create one, it contains the string: «FK»  - but that's another story (but should still be fixed).

There's also a synchronization problem with the on-screen display when you add the Foreign Key constraint and when you refresh the diagram - but that's yet another story (but should still be fixed).

Next, when you delete the Foreign Key constraint it will (at no charge) delete the Edge Name (even though the displayed label (Foreign Key constraint) has NO relationship to the Edge Name).  This one has to be FIXED!

Nonetheless, if a name IS specified, it should be displayed.

A side effect of this is that when you suppress line segments, you DON'T get the edge name at either end of the suppressed line segment (as you do with other renderings).  You get the Foreign Key Constraint which may not be unique enough (and which you can't change).  Which is how I discovered the 5 bugs above in the first place...


Bugs and Issues / {abstract} rendering with long names
« on: December 11, 2008, 02:01:28 pm »
I've observed this since I first started using EA over five years ago, but since it hasn't been fixed in that time, I'm finally formally reporting it.

Marking the [X] Abstract checkbox will (almost always) cause rendering problems for shapes with long names.   This is true of the initial marking and some subsequent resizing of the rendered element.  It is more pronounced with elements that don't automatically render compartments (such as Components).  However, it is still present on Classes (if there are no features defined).


Bugs and Issues / Project Transfer dialog inadequate
« on: December 22, 2008, 06:09:35 pm »
Using the Project Transfer dialog with DBMS sources or targets means that you can't actually tell which database is the source or the target.  The Initial Catalog sub-string is not visible, nor is the control scrollable.

The potential for wiping out the WRONG target is huge...


Bugs and Issues / Missing "In diagrams" menu item for Packages
« on: December 17, 2008, 03:45:24 pm »
There should be...

Package vertexes can be placed on diagrams - so you should be able to locate them on the diagrams they are present in - just like any other vertex.

Consistency, Consistency, Consistency! TM


Bugs and Issues / XMI import MAY differ from XMI (controlled) load
« on: December 05, 2008, 01:22:40 pm »
If you save a controlled package and then reload the file, you MAY get a DIFFERENT result from if you import the SAME XMI file.

By means of available EA functionality, I created Component "instances" - that is, Components with references to "Classifiers".  Thus the component appears n the browser as: <component glyph> Component Name: Classifier Name.  Why I resorted to this is another story (and may be the subject of another post).

If I use the controlled package mechanism, the Component instances are correctly saved and restored!  If, however, I import the same package, the classifier references are stripped!  Incidentally, the Export mechanism ALSO correctly exports the classifier information!

This is a high priority bug!  Being able to rely on correct XMI round tripping is crucial to effective use of EA!
Consistency, Consistency, Consistency! TM

Using EA in spite of EA, NOT because of it!TM!

Bugs and Issues / Default Initial Value dialog doesn't wrap text
« on: December 12, 2008, 05:02:08 pm »
For long values of the initial value the builder[1] engaged control dialog (Captioned: Default Initial Value), doesn't wrap.  So, not withstanding the control takes up a significant area of the screen, you only see part of one line (unless you put in explicit hard returns).

Since the field is a memo field, it should wrap - like other memo fields.  We acknowledge that in the associated text box this isn't possible, but the memo control should.  (also, if the text does overflow the text box, there should be the usual ellipsis to indicate more...).

[1]Yes Simon, this time I DID spot the builder button ;)

Bugs and Issues / UI creates different XSD Tagged Values from RE
« on: December 03, 2008, 06:51:20 pm »
When you reverse engineer an XSD, and then update a value (such as MaxOccurs - as in the UI problem with XSDElement MaxOccurs bug report), an additional set of properties with default values are created by the UI within the tagged value set for that element (including: anonymousRole, form, default, fixed)

The reverse engineering process should create these values also OR the UI should not create them, since they are defaults.

Consistency, Consistency, Consistency! TM


Bugs and Issues / UI Problem with XSDElement MaxOccurs
« on: December 03, 2008, 06:28:01 pm »
There is a UI problem for XSD Elements.  When you reverse engineer an XSD, it will correctly set the maxOccurs:unbounded to MaxOccurs: * for the XSDElement.  Thus the MaxOccurs (Multiplicity Upper Bound) reads * and the Tagged Value maxOccurs reads unbounded.

If you change the MaxOccurs to (say) 6, EA correctly changes the Multiplicity Upper Bound to:6 and the maxOccurs Tagged Value to: 6.

If you change the MaxOccurs back to *, EA incorrectly sets the MaxOccurs (Multiplicity Upper Bound) to: -1 which makes the Tagged Value read -1.  This is incorrect.


Bugs and Issues / Delete "Feature" on diagram - silently purges
« on: November 28, 2008, 06:57:27 pm »
If you accidentally have a feature selected on a diagram and press the delete key, the feature is silently purged from the model.

This needs to rectified immediately!

A user, while trying to remove a vertex from a diagram, may accidentally create a "click too far" and accidentally have selected a feature rather then the encompassing vertex.  So far I've done it 5 times this week, and fortunately noticed EA had purged the feature and reverted to my backup.  But in other circumstances this could go unnoticed for a long period of time.

Any purging of items from the repository should be failsafed.

Consistency, Consistency, Consistency! TM


Bugs and Issues / Import filename overwritten
« on: November 28, 2008, 06:06:34 pm »
If using controlled packages, when you do a package load, the file name of the package overwrites any file specified in the import/export menu item.

Given that the package load makes transient use of the import/export dialog, the file name should not be "sticky" in this way.


Bugs and Issues / Diagram Notes disappear
« on: November 28, 2008, 01:04:28 pm »
The Diagram Notes which are added by using the Diagram Notes Element button on the UML Elements toolbar.  Are a funny beast...  They are stored by EA in the t_object table.  Now that is questionable, but not the REAL problem in this bug report.

Since, in EA, a Diagram is NOT an element (and therefore doesn't exist in t_object), EA cannot attach the t_object to the diagram.  So what it does is to attach it to the nearest available t_object.  In the case of a diagram created under a package, it attaches (by means of the ParentID column) to the Package t_object entry.  If the diagram is created under a class (say, by means of the infamous <Vertex Context Menu>|Advanced>Make Composite menu item), then it attaches to the parent object.

Now you can move the diagram from where it was created to somewhere else.  But the ParentID of the Diagram Notes object doesn't change.  Consequently, when you delete the original object, the Diagram Notes object is also erroneously deleted.

When you move the diagram, the parent of the Diagram Notes object needs to be refactored to the new parent of the diagram.

So...  If you've ever had the Diagram notes element disappear inexplicably... Now you know why!


Bugs and Issues / Save/Load Visual Layout - breaks
« on: November 14, 2008, 04:00:55 pm »
Has anyone else noticed this?

I have a complex layout that I save to Layout 4 (but the problem exists even without saving, it's just more in your face).

When I load it back (having done nothing in between) it comes back slightly changed.  I have a number of windows stacked,and the stacking heights change.  Eventually I got a rule out to check my eyes weren't deceiving me.

If I close EA and reopen, the "sticky" layout moves by the same amount as the difference in save/load.  So if I repeatedly open/close EA, the topmost set of stacked windows eventually reduces to nothing...

Since I'm running Windows Server 2008 it may be related to this, so I'm asking if anyone else sees this before I report it to Sparx as a real bug.


Bugs and Issues / Inconsistency in off-diagram parents & glyphs
« on: October 10, 2008, 02:10:17 pm »
EA has a neat facility to allow the tracking of parents from whom the vertex inherits but are not on the page to be documented somewhere in the top right hand corner of the rectangular notation.

EA also has the facility to place a glyph (depending upon the vertex, type and stereotype) somewhere in the top right hand corner of the rectangular notation.

The observant among you may have noticed that I used the word somewhere (italicized - for emphasis) both times.

Now, admittedly I'm using EA somewhat creatively to create new kinds of models not envisaged by UML's creators.  But, I don't think that invalidates my following comments or observations.

On a diagram I have three types of vertexes.
On one type, the parent list is above the glyph, on another type it is below the glyph and  for the third it is underneath the glyph (so it is obscured by the glyph).  ::)

Is it worth reporting this as a bug?  ;)

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