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 ... 60 61 [62] 63 64 ... 78
Bugs and Issues / Shape script stops partition flip
« on: September 03, 2009, 01:06:07 pm »
If you set a stereotype with a shape script on a partition, it disables the Vertical Partition functionality.

I would have thought that whether a partition was "Vertical" or "Horizontal" was s property of the partition and should not be affected by the presence of a shape script.  The shape script might choose to be cognisant of the setting or not, but the setting shouldn't be inhibited.

This should be true for all elements which have "partition like" qualities.

[EDIT: Because of self-inconsistent EAUI, you can still flip using the little "thingy" at top right near the QuickLinker]


Bugs and Issues / Additional Views - Column settings NOT sticky
« on: September 02, 2009, 04:17:28 pm »
Some of the additional views:
System [Alt+2]
Testing [Alt+3]
Maintenance [Alt+4]

Have columns to show the various properties.  The column width settings are only SOMETIMES sticky.

Particularly if you switch between Show/Hide Properties functionality, the settings can get reset.  Strangely  ;), the settings seem to persist between closures of EA, but not during the live switch above...

Since I've not running a standard config, anyone else seen this?  If so, then I'll report it.

Also (and in a sense more importantly), these column settings don't appear to be saved when you save a custom layout.  I think they should.

Confirmation anyone?

Bugs and Issues / StateNodes - Composite - NO image!
« on: August 27, 2009, 05:03:33 pm »
We have developed some SDK Automation to create/maintain auto-updatable diagrams.

We have recently expanded this to include Activity diagrams.

Much to our surprise we discovered that when we made the StateNode "composite:, the image disappeared and left us with a blank area (if the correct size - since we can select it...).

All the other composite stuff works, you get the "chain link" glyph, double clicking the element will hyperlink tot he required diagram.  It's just a bit tough to be sure you're double-clicking on the element when there's no image to target!


Bugs and Issues / StateNodes - DON'T respond to FILL Colour
« on: August 27, 2009, 05:57:43 pm »
You can adjust the Font and Border colour for a State Node, but you can't adjust the Fill colour.  (You can set it and the value will be in the repository - but it doesn't affect the displayed shape).

StateNodes should behave as much like other elements as possible.


Bugs and Issues / Actions - Composite - NO "links" glyph
« on: August 27, 2009, 05:39:37 pm »
We reported in StateNodes - Composite - NO image! StateNodes lose their image when made composite.

As a temporary workaround, we decided to reclassify them as actions.  Imagine our surprise when we found we could now SEE the element, but couldn't tell if it was composite or not because the link symbol never appears - regardless of the state of the element.  The hyperlinking works!

But if you double click the action you get a "Magical Mystery Tour" as to whether you'll get a Properties box or a Hyperlink...

Since you can set whether or not the action is "composite" directly via the UI; this is, by definition, a bug...

Actions should behave as much like other elements as possible.

Actions should have Rectangular notation - as should ALL elements!


Bugs and Issues / StateNodes - CAN'T display any Compartments
« on: August 27, 2009, 05:16:43 pm »
We have developed some SDK Automation to create/maintain auto-updatable diagrams.

We have recently expanded this to include Activity diagrams.

Much to our surprise we discovered that when we added Notes to a StateNode there was no way to display them directly as you can with other element types - such as UseCases etc.

You can mark the Set Feature Visibility check boxes, but no notes appear.

EDIT: This applies to ALL the compartments.

StateNodes should behave as much like other elements as possible.

StateNodes should have Rectangular notation - as should ALL elements!


Bugs and Issues / Layout moves unselectable Diagram Notes
« on: June 05, 2009, 06:38:45 pm »
If there is only the diagram note (the title block, made unselectable) and one other shape on the diagram, the layout command will move the note.  If there are more than one shape, it won't

Create new diagram, insert diagram note, make unselectable, add another shape. layout diagram.  Observe the unselectable note moves.
Put the note back.  Add a third shape. layout diagram again.  Observe the diagram note now doesn't move.


Bugs and Issues / Stereotype adornment NOT working for some...
« on: July 20, 2009, 01:20:54 pm »
We used to have things like «Table», «View», «procedure» adorned with specific appearance changes (via the Settings|UML... dialog - not using shape scripts but just the Default Colors).

Sometime in the recent past, these adornments stopped being applied for us.  Anyone else noticed this?  Not all stereotypes are affected - in particular it seems the "special" ones (where it appears EA uses the stereotype to, in effect, define a new type of element) are the ones that refuse to budge.

I was hoping this would be fixed in 846, but it would appear not and it's now getting a bit problematic for us.


Bugs and Issues / Toolbox Collapsing NOT Sticky
« on: August 04, 2009, 12:41:08 pm »
If you collapse a toolbox when you move away and back to the diagram, the toolbox is not collapsed.  This is annoying as there isn't much point in providing the collapsing capability if the behaviour is this...


Bugs and Issues / Compare with XMI (only for XMI 1.1?)
« on: July 23, 2009, 02:15:34 pm »
I get an error:  "An error occurred during the compare process..." when trying to compare a model package with an exported XMI 2.1 export.

It works OK with XMI 1.1 export.

Is this a bug?  The documentation doesn't seem to suggest that's a restriction.  And if it was, EA should say so when it starts to load the XMI...


Bugs and Issues / Browse for Instance Classifier - not working (846)
« on: July 16, 2009, 11:19:48 am »

Anyone else seeing this?

<context menu>|Instance Classifier Ctrl-L

Browse tab only returns -- <none>

Search tab seems to work.


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"

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


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


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?


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:


in a ShapeScript draw exactly the same as a

setlinestyle("DASH");  ?


(and the others) seems to work fine!

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

7.1 (831)

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