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 ... 5 6 [7] 8 9 ... 80
91
It would be useful if the "Source" and "Target" names could be replaced with meaningful names, specific to that Relationship Matrix.  They could then appear on the printout (where even the "Source" and "Target" values are suppressed).

Reported,
Paolo

92
Bugs and Issues / Relationship Matrix: Can't always delete relationship
« on: September 07, 2017, 05:32:53 pm »
It turns out that if the Direction is set to both, the delete relationship functionality is disabled.  At a minimum, this should be mentioned in the Help.  Better still, just as one can Add Source->Target or Target->Source, the appropriate cell contents should be available for deletion.

Reported,
Paolo

93
Am I correct in understanding that there is only one relationship matrix allowed at a time?

We're only just getting into relationship matrices and it might be useful to "flip between" different matrices as one does with diagrams.

Paolo

94
Bugs and Issues / Relationship Matrix: Can't add inverse relationship
« on: September 05, 2017, 05:26:05 pm »
I mentioned elsewhere that I get why the Relationship Matrix uses directionality rather than navigability.  When you have an empty cell, you can add either the Source->Target Relationship or the Target->Source relationship.  However, once a relationship is entered, you can't add the other (via the matrix) - in order to get it in, you have to go to a diagram and create it there.  The Relationship Matrix then shows the symbol for the inverse relationships.

Reported,
Paolo

95
When you save a Relationship Matrix to a CSV file the default file name is "*.CSV",  it would be more useful if the default were the "<profile name>.CSV".

Reported,
Paolo

96
We hold all out elements in special branches, away from the diagrams.  Since we have so many, we have multi-leveled alphabetic folders to group them in.  When we display them on the Relationship Matrix (and use the "Include ... Children" option), the path to the element is rendered.  While for many use cases, this is useful, it is particularly annoying for this one.  Please make the display of the path optional for both origin and destination.

Reported,
Paolo

97
Bugs and Issues / Relationship Matrix fails with "Information Items"
« on: August 31, 2017, 05:00:00 pm »
We have our own element metatype called "Information Item" according to the following (partial) MDG definition.
Code: [Select]
<Stereotype name="InfrmtnItm" metatype="Information Item" If we try to select it from the dropdown for the Element Type, EA helpfully (It's an ironic observation, Joyce) replaces  "Information Item" with "InformationItem".  Consequently, we can't use them in a Relationship Matrix.  Pure EAUI!

Needs to be fixed!

Reported,
Paolo

98
Virtualized Connector Ends (VCEs) now honour shapescripts.  BUT it doesn't seem to provide access to all the properties used by the shapescript.  We have a decoration that will provide an indicator that the Notes field for an element is empty.
Code: [Select]
if(hasproperty("notes","")) //Notes empty...
The base object responds correctly, but the VCE does not, it ALWAYS shows the notes as empty regardless of the actuality.

Reported,
Paolo

99
Bugs and Issues / Virtualized Connector End as Diagram Object
« on: August 30, 2017, 05:24:45 pm »
I've just reported another defect in the Virtualized Connector End functionality.  I did a search and found that the only posts that mention that functionality are mine!   ::)

In quickly reviewing them, and having used the functionality from time to time, I've come to the conclusion that a significant part of the problem with the shapes and connectors tot he virtualized connector end is that there is NO corresponding Diagram Object.

With automation, one can place MORE than one instance of an object on a diagram (and AFAIK the Consistency Checker accepts it).  I guess that, at present, EA synthesises a diagram object.  My suggestion why not make that item persistent?  It can be distinguished in some way from the Base diagram object and be referenced in the virtualized connector end.  This would, it seems to me, allow the full functionality of a REAL diagram object, without significantly deviating from the concept of a virtualized connector end.  Because the VCE diagram object can be distinguished from the base object, one can finesse any appropriate functionality through to the base object.

Thoughts?
Paolo

100
In 1303: Virtualized Connector End needs shapescript I mention that the virtualized connector end is different from the base diagram object.  However, today we discovered that not only does it do that, but it will resize the base diagram object to the default size (at least for Rectangular notation).  Once it's done that, you CAN'T readjust the sizing back to what you started with (not even by "jamming" the DB!!!)

Reported,
Paolo

101
Insert Related elements doesnít have Select All/None on Connector and Element types.  Anywhere where there can be more than 3 possible values (either permanently or as a result of a query), there should be Select All/None functionality available.  It would also be good to have a "remember settings" in the case of this dialog (even if only on a per session basis).

Reported,
Paolo

102
As far as I'm aware, there's no mechanism in a shapescript to determine whether or not the relationship is Self-Referential.  We'd like to vary the shapescript if the line is self-referential.  Can we please have such a property in the Connector Properties list?

Reported,
paolo

103
Bugs and Issues / Orthogonal Style Lines don't terminate consistently
« on: August 24, 2017, 04:57:36 pm »
I added 23 objects (all same metatype and size) to a diagram.  I needed to connect them to one object also on the diagram.  So I used the Quicklinker to make the first link and then used [F3] to repeat the relationship for the other objects.  So far, so good!  I noticed after the first half-dozen or so of these operations, that the lines were overlaying each other at the destination end (the one object I'm connecting to).  Cool, I thought!  That's neat!  However, as I kept adding connections and the side to which the destination was connecting changed, the subsequent lines didn't overlay each other on the second side.  That's inconsistent.

Could I suggest that the default terminations of the Orthogonal line styles be the centre of the side EA has decided to attach it to?  In the first case above, the lines were overlayed at one corner of the side.  In the second case, they were distributed across the side.

Reported,
Paolo

104
Now that we can have relationships from relationships to elements, it is defective to make every relationship to a UML Constraint be replaced by an implied (not even a real) Notelink.  We defined a number of relationships between arcs and stereotyped Constraints in our QuickLinker.  Imagine our surprise when, as we released the mouse, we weren't given a set of QuickLinker options, but an implied notelink was automatically created.

Reported,
Paolo

105
Bugs and Issues / Canít display hidden label for Constraint
« on: August 23, 2017, 10:03:31 am »
We're naming our UML Constraints - so we can tell one from the other.  This will produce a Label.  However, once the label is suppressed (either intentionally or otherwise) there is no mechanism to recover it and make it visible again.

Please Rectify!
Report,
Paolo

Pages: 1 ... 5 6 [7] 8 9 ... 80