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 ... 62 63 [64] 65 66 ... 79
946
Bugs and Issues / Browse for Instance Classifier - not working (846)
« on: July 16, 2009, 11:19:48 am »
Hi,

Anyone else seeing this?

<context menu>|Instance Classifier Ctrl-L

Browse tab only returns -- <none>

Search tab seems to work.

Paolo

947
Bugs and Issues / Hyperlinks not resizable (7.5)
« on: April 21, 2009, 06:12:04 pm »
In past versions, Hyperlinks could be resized (to be as big or a small as desired).  We would put borders around them and they would behave like "composite" boundaries.  We have them all over our models!  They were VERY useful!

In v7.5 (844) they aren't resizable any longer.  Our diagrams have been distorted and no longer "make sense"

Steps:
Create a hyperlink, format it with a border.  Attempt to resize.  Observe hyperlink shape returns to the default size...

Reported,
Paolo

948
Bugs and Issues / Enumerations don't respond to Default coloring
« on: April 22, 2009, 12:46:20 pm »
We use Metafile default coloring adornments to render Enumerations (UML Stereotype «enumeration»)  with specific backgrounds, borders and fonts colourings etc.

With v7.5, these adornments disappeared.  You can't use the Settings|UML... Stereotypes to control the rendering of Enumerations.

Steps to reproduce:
Create an Enumeration.  Create the corresponding stereotype rendering using default coloring.  Observe rendering will NOT apply...

Reported,
Paolo

949
Bugs and Issues / 7.5 Stereotype GUID changes
« on: March 31, 2009, 12:27:19 pm »
We're developing a process of formally identifying changes between releases of EA.  We've been "hit" before by changes in the DB content which EA relies on for its operation which aren't back-filled into old models (Some of ours are approaching 5 years old).

Anyhow, I'll start a separate topic on agreeing on a process so we users can be confident we haven't missed something.

This topic is to investigate if what I've discovered is universal and if it is a bug.

We exported the list of stereotypes from v7.1 (build 834) (and compared them with the list of stereotypes in v7.5 (build 843)  (in both cases, we created an "Empty" project, selecting ALL the possible aspects that EA provides - for each specific version).

We discovered two new stereotypes in 843 (no surprise here - that's what the process is designed to do...).  However, we also discovered that ALL the stereotype GUIDS have changed.

Now we're not sure of the impact of this.  From first principles, I would have expected them NOT to have changed... I mean we keep OURS in line by exporting the list from our master repository and importing it into our working ones.  In addition there IS an error message from the Tools|Data Management[ch9658]Project Integrity check [Shift + F9] process that concerns fixing mismatched stereotype GUIDs - so EA obviously thinks stereotype GUID mismatching is harmful.

Can a Sparxian, or anyone, tell me what's going on and what we should do about it?

What are the consequences of having more than one identified stereotype with more than one GUID floating around a system of repositories?

TIA,
Paolo

950
Bugs and Issues / "DASHDOT" == "DASH"  in ShapeScripts
« on: July 24, 2008, 02:21:31 pm »
Are my ancient (but still 20/20) eyes deceiving me or does a:

setlinestyle("DASHDOT");

in a ShapeScript draw exactly the same as a

setlinestyle("DASH");  ?

setlinestyle("DASHDOTDOT");

(and the others) seems to work fine!

If it's a common problem I'll file a report...

Paolo
7.1 (831)




951
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?

TIA,
Paolo

952
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...

Reported,
Paolo

953
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...

Reported,
Paolo

954
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).

Reported,
Paolo

955
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...

Reported,
paolo

956
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

Reported,
Paolo

957
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

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

958
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...).

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

959
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

Reported,
Paolo

960
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.

Repoprted,
Paolo

Pages: 1 ... 62 63 [64] 65 66 ... 79