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 ... 3 4 [5] 6 7 ... 76
61
Bugs and Issues / Connector Labels and Dotted Line styles
« on: June 21, 2017, 05:33:04 pm »
I'm sure I've reported this over the decade or so, but I can't find it in the search.

If you create a label for a connector (such as add name of Association), if the line is a Solid line, then the text of the label can be positioned so that it overrides the line and you can CLEARLY see the text.  However, if the line is one of the non-solid (setlinestyle()) lines, then the underlying line will "peek" through - making the text unreadable.  Can this be fixed, please?

Report,
Paolo

62
General Board / Inconsistencies between Help and t_connectorTypes
« on: June 15, 2017, 03:55:15 pm »
There are inconsistencies between what the help says in .../User%20Guide/model_domains/transformingconnectors.html and the t_connectortypes table in the repository.

Connector_Type   Help Document
Abstraction      Abstraction
Aggregation      Aggregation
Assembly         Assembly
Association      Association
Collaboration      Collaboration
CommunicationPath      
Connector      Connector
ControlFlow      ControlFlow
Delegate         Delegate
Dependency      Dependency
Deployment      Deployment
ERLink         ForeignKey
Extension      
Generalization      Generalization
InformationFlow   InformationFlow
Instantiation      Instantiation
            Interface
InterruptFlow      InterruptFlow
Manifest         Manifest
Nesting         Nesting
NoteLink         NoteLink
ObjectFlow      ObjectFlow
Package         Package
ProtocolConformance      
ProtocolTransition      
Realisation      Realization
Sequence         Sequence
StateFlow      
Substitution      Substitution
            TemplateBinding
            Transition
Usage         Usage
UseCase         UseCase
            Uses

Should these be identical or, if not, why not?

Paolo

63
We use stereotyped Notelinks for various administrative metatypes in our repository.  We've observed that if we create the first link from the Toolbox, the [F3] (repeat last connector) functionality will work correctly and create a new arc of the correct metatype.  However, if we use the QuickLinker to create that first link, the [F3] function will create an unstereotyped Notelink.  Obviously, the same functionality is not being used...  Can we please ensure that the behaviour is the same (for ALL metatypes) - regardless of the first instantiation method?

Reported,
Paolo

64
Bugs and Issues / Tooltips show HTML codes
« on: June 15, 2017, 09:58:43 am »
If you enable "hovering" tooltips (don't know if this bug also occurs for the status bar tooltips) and the tooltip cutoff occurs in the middle of a HTML element, the HTML code is visible.  Since there is no formatting on a tooltip, the HTML should have been stripped off in the first place.

Reported,
Paolo

65
Increasingly, we are developing scripts that operate directly on the Selected Diagram Link (rather than the underlying Selected Connector).  Similarly with Diagram Objects.

However, there is no SelectedDiagramLink or SelectedDiagramObjects attributes for the Diagram Class.  We are forced to scan the appropriate collections to determine the diagram link from the underlying connector.

Can we have direct access to the diagram specific items?

Reported,
Paolo

66
The [ ] Use Rectangular Notation context menu item is created on the fly by EA by inspection of the shapescript.

However, for a number of element types, Activity, being the one that caught us out today, this is NOT respected.

Please rectify.  I see no reason why, if the shapescript has the requisite coding, that the context menu items shouldn't be provided.

Reported,
Paolo

67
We are finding increasingly that we can define a structured Tagged Value (typically an enum) and re-use it in a number of places.  I'm not talking about using the same named tagged value in multiple elements - that's easy enough to manage.  I'm talking about using the same set of values (with effectively the same set of semantics) multiple times for the same element.  One example is  "Degree of Fit" - where the same enum values are used for three different types of "fit" (for the same element).  We have currently created three Tagged Values defined identically, but once they've been created the fact that they have the same enum literals and semantics is lost.

I couldn't see how to use one definition in multiple named tagged values.  Is there such a mechanism?

TIA,
Paolo

68
It seems that status colours are only visible if the item is in rectangular form.  Is that correct, or have I left the secret sauce off the shapescripts I'm using?

Paolo

69
Suggestions and Requests / Word Wrap on non spaced names
« on: May 29, 2017, 04:50:08 pm »
I'm sure there was some discussion recently on the forum about word wrapping.  But I can't find it.

Anyway, there should be the ability to word wrap names that don;t have spaces, but do have mixed case naming.  We commonly use a naming scheme we've called Complex Pascal Naming where capital letters separate words, but Acronyms and Initialisms are allowed to retain their Uppercase.  It's not that hard to write an algorithm to split the words up and determine where the word wrap should be.

Please consider.

Reported,
Paolo

70
Bugs and Issues / MDG File grows too large!
« on: May 26, 2017, 01:25:50 pm »
We recently significantly increased the size of our MDG by automatically generating a series of relationship to relationship QuickLinks (some 7000 odd in this case)

EA complained about a failure in our XML.  But it turned ut to be a size-related issue:  At line 42965 (round about column 13x - it varies depending upon the file content).  EA will fail to import the MDG.  This expansion was to be only the initial step, the file is currently 10-12 Mb in size and we expect it to grow more.  What is the current Maximum size for an MDG file?  Can this be fixed urgently?

Reported,
Paolo

71
QuickLinks "from" relationships don’t work correctly in “empty space”
  • Inter-relationship QuickLinks are listed (they shouldn’t be)
  • @Element QuickLinks don’t do the right thing (open the available set of elements from the list of available elements)
Reported,
Paolo

72
Relationship to relationship QuickLink doesn’t indicate selected target (like for elements).  This makes it difficult to ensure you're going to hit the right "target".
Please rectify.

Reported,
Paolo

73
Please allow Source & Target Dropdown in the arc's Roles page to access Operations as well as Attributes for (any arc type).

In these days of complex systems modelling, being able to access a Service object's operations and link to them in the arc in the same way as Attributes would be MOST beneficial (for example for the ArchiMate Serving relationship.

Reported,
Paolo

74
The Set Attached Links dialog needs an indication of whether the arc is visible on the diagram or not.

Otherwise, the user may check the box of a connector hidden on the diagram and wonder why the "Notelink" doesn't show on the diagram.

It is accepted that one can create a link to a hidden connector, but the user experience should be considered.

Reported,
Paolo

75
If you use the Link to Connector Feature functionality on a Note Element (say Link to Connector Note) and you have more than one connector attached to the Note, the displayed note will change (apparently arbitrarily).

However, it is NOT arbitrary, it appears that the Connector Note that will be displayed is that of the highest sequence number in the Set Attached Links dialog!  This is not appropriate!  There should be a checkbox against the Connector in the Set Attached Links dialog to indicate that a particular has been designated the one for the Note to be displayed.

Reported,
Paolo

Pages: 1 ... 3 4 [5] 6 7 ... 76