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 ... 63 64 [65] 66 67 ... 77
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.


Bugs and Issues / Hyperlink Address for diagrams flawed
« on: February 12, 2008, 11:20:26 pm »
The hyperlink process for Diagrams (at least) is flawed.

The Hyperlink address does not mirror the actual address of the diagram.

The actual link is managed internally by a GUID, so the address field for the Diagram hyperlink should be read only (and, perhaps, mirror the other internal links such as $Matrix and be rendered as $diagram //<name>)

The Notes field is used to display the text on the diagram.  Therefore for diagrams, there might be an additional check box: [  ] Track Name which would be updated when the diagram name changed.

A secondary check box: [  ] Suppress Package would suppress the package part of the name.


Bugs and Issues / BUG: Editing stereotype in Browser fails
« on: February 12, 2008, 10:13:20 pm »
In topic: [size=13]BUG: Get the primary stereotype from one place][/size]  I mentioned the stereotype in the browser was different to the one in the properties.

As part of the experimenting and diagnosis, I tried changing the stereotype directly via the Browser [F2].

Although you appear to be changing the value in the browser, you aren't.  EA adds the stereotype value to the element name (including, obligingly (NOT!), the guillemets).

Now, unfortunately, guillemets are legitimate characters for names of elements.  So figuring out how to fix this bug isn't easy, but I can think of at least one viable method.


Bugs and Issues / BUG: Notes in Diagram Frames broken!
« on: February 06, 2008, 11:00:24 pm »
I don't think this is directly related to the new Rich Formatted Notes in the Beta...

Notes in Diagram frames are NOT displayed properly.

All NOTES have their size miscalculated.

Diagram Note linked Notes don't have text in them at all.


Bugs and Issues / EAUI: outliners missing branch functions
« on: February 07, 2008, 09:21:54 pm »
I first noticed this in the new (825) Views window, but I've since found it in others - such as Resources...

Although these windows show an outline control, the outlining widgets DON'T have the branch expanders and contractors (as does the Browser window).

Please provide...

Consistency, Consistency, Consistency! TM


Bugs and Issues / (825) EAUI: Packages out of order?
« on: February 11, 2008, 04:48:20 pm »
I've upgraded an existing model to EA 71.1 (825 Beta).

If I add a package to an existing view AND the package name is lower down the alphabet than the first existing package, it will be entered ABOVE the diagrams!

You have to move it with the Arrows to get it back into the right place.  This behaviour doesn't occur under previous versions.


Bugs and Issues / Can't order edges on RTF documents
« on: February 07, 2008, 10:34:17 pm »
In the RTF Options, you can order: Packages, Elements and Diagrams (vertexes).

But you CAN'T order edges (connectors).  This means the output order of linkages appears arbitrary.

Ordering options for edges should be (at least):
(none) - the present
Type  (new default)
Origin  (source - implies name)
Destination  (target - implies name)

It would be better still if at least two (hierarchical) orderings could be specified for edges (due to their nature).

In addition, I feel it would be useful to add:
Primary Stereotype
to the list of ordering options for all types.

[size=0]2008 Paolo Cantoni, -Semantica-[/size]

Bugs and Issues / EAUI: Tab order inconsistent!
« on: February 07, 2008, 05:38:23 pm »
One a few of the dialogs, the forward [Tab] and reverse [Shift+Tab] tab orders are inconsistent!

If you go forward and go to far and then try to go back, it doesn't go where you came from!  [Specific case - most edge dialogs - tab from Name to Notes then backwards...]

This violates the "principle of least astonishment"

Consistency, Consistency, Consistency! TM

"Astonished"  (I didn't know you could do that!)

Bugs and Issues / BUG: (825) Can't use keyboard extended characters
« on: February 06, 2008, 10:46:02 pm »
The new formatted notes do NOT allow the use of keyboard extended characters such as: [ALT+0171] for [size=16][/size] and [ALT+0187] for [size=16][/size].

You can paste the characters in, but you can't enter them in-line.


Bugs and Issues / BUG: NO support for inherited features in RTF
« on: February 06, 2008, 10:16:29 pm »
The RTF document generator needs to be consistent with the features in the Set Feature Visibility dialog.

Basically if I can/want to see these things on a diagram, I'm likely to need to see them on the generated RTF output.

Things like Inherited Responsibilities, Inherited Tags  Inherited constraints... etc

Consistency, Consistency, Consistency! TM


Bugs and Issues / RTF responsibility ordering inconsistent!
« on: February 06, 2008, 09:54:26 pm »
In [size=13]BUG: Can't order Responsibilities[/size] I note that the ONLY ordering available on the diagram or in the dialog is alphabetic.

So I go to a great deal of trouble to get the right ordering by prefixing my responsibilities with numeric text prefixes to achieve the desired order...  Looks terrible, but at least it's ordered!

Imaging my chagrin (and the "blue" air around my head) when I discover that the RTF output for the Responsibilities (aka Internal Requirements) appears arbitrary!

It must be the same as the Diagram/Dialog!

Consistency, Consistency, Consistency! TM

If the bugs weren't there, I wouldn't find them!

Bugs and Issues / BUG: quick linker and toolbox inconsistent
« on: February 05, 2008, 11:48:33 pm »
If the vertex selected is one of the vertexes on the toolbox for this diagram type, then the list of vertexes createable by the quick linker should (at least) contain the set of vertexes in the toolbox.

Similarly, list of edges should be consistent between the toolbox and the quick linker.

If the current toolbox is NOT the default one for the diagram type, then the issue is more problematic.  However, when the defaults are in place they need to be consistent!

Consistency, Consistency, Consistency! TM


Bugs and Issues / BUG: Internal Requirement type not cleared
« on: February 05, 2008, 05:59:41 pm »
The internal requirement (aka Responsibility) Type is not cleared on saving (as is the actual requirement).

Nor is it correctly cleared on prior requirement selection, if the type is empty!

This means the user is thoroughly confused as to the state of this field!

Consistency, Consistency, Consistency! TM


Pages: 1 ... 63 64 [65] 66 67 ... 77