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 2 3 [4] 5 6 ... 78
When switching to Rectangular Notation, the shapescript will ignore the existing diagram object sizing (especially if larger than the default) and reset to the default size specified for Rectangular Notation.

If object sizing is  Ox×Oy and the default non-Rectangular (Icon) Notation sizing is Ix×Iy and the Rectangular Notation sizing is Rx×Ry, then it could be argued that if at the switchover, if Ox = Ix and Oy = Iy, then they should be switched to Rx and Ry respectively.  However, if they are not the default values, then the object sizing should remain Ox×Oy.

My user found it quite annoying that where they had large object sizes, typically encompassing other objects, on switchover, the sizing became very small and they had to resize.


When in the Matrix Diagram, it appears one can't use keyboard shortcuts.  I tried a couple [SHift+F9 and [Ctrl+F9] and neither worked.  This doesn't happen in other "special" diagrams such as the Model Search page.


Bugs and Issues / Project Types not disabled when project is not loaded
« on: October 02, 2017, 05:44:44 pm »
When you open EA without a specific project, the Configure | Reference Data | UML Types ribbon item is (correctly) disabled.  However, while the individual items below the ribbon dropdown Configure | Reference Data | Project Type s are also (correctly) disabled, the item itself is not.  I thought it was a "standard" UI/UX pattern that "disabledness" should percolate "upwards".  Am I wrong?


Bugs and Issues / Suppress Relationships still shows NoteLinks!
« on: October 02, 2017, 11:34:36 am »
If you unmark the Diagram Properties | Connectors | [ ] Show Relationships, the Relationships currently visible in the Diagram are suppressed.  However, this is NOT true for Notelinks - they are still visible!  While acknowledging that they may be implemented using a different technology, they are ALSO implemented as normal relationships.  Especially in the latter case, and particularly where stereotyped (and do NOT involve a Note item), they should be suppressed.


Unlike the Created Date which is rendered as disabled (light grey font), the Diagram Modified Date is not so rendered even though it is similarly disabled.


We'd like to be able to create diagram types that include a Stereotype for the Diagram.  Of the available properties in the diagram profile, "stereotype" doesn't seem to be one of them.  Is it possible, currently, to do this or do I need to put in a Feature Request?


It's really a rhetorical question, if I can I can probably only check for Incomplete/Complete, not the individual selections.  Bu, could someone confirm for me, please?

As mentioned in other recent posts relating to other places where one would like to get at the specific selections, the implementation leaves a lot to be desired.


Suggestions and Requests / Model Search: More than one Search Term?
« on: September 22, 2017, 04:47:14 pm »
It would be good if we could have more than one Search Term per Model Search.


Suggestions and Requests / setorigin() to be more useful
« on: September 22, 2017, 10:15:07 am »
When writing shapescripts, setorigin() is used to position text labels.  It would be cool if it could be extended to positioning the output of print() statements.


As many will know, we "roll our own" MDG, semi-manually.  It has now grown to over 10Mb and will continue to grow.  We suspect that some of the anomalous behaviour we are seeing around MDGs (which I won't list here) is caused by the file being so large.

We tried to split out the QuickLinker section into a separate MDG (since the QuickLinker doesn't need a specific MDG name for the entires).  It almost worked!  The link appeared to be formed correctly except for the multiplicity specification (which it didn't pick up from the main MDG.  Is this actually a bug (if it apparently picked up everything else)?

In any event, it doesn't work NOW!

So is there a way to split an MDG file into multiple files?


Bugs and Issues / Model Search: How to inhibit null <Search Term>
« on: September 20, 2017, 04:55:08 pm »
Is there any way through the normal Model Search mechanism to stop the user running the search with a null <Search Term>?

A user accidentally did that and the search returned a result set and it took us a while to figure out why.  Because the result set with the <Search Term> and without the <Search Term> were the same it looked like a bug, but it's not (just a coincidence).  However, the lack of the <Search Term> might not be noticed.  This particular search NEEDS a <Search Term>.  How can we make sure the user provides one?


Bugs and Issues / Model Search : Metatype/Class return is “Pot Luck”
« on: September 20, 2017, 04:47:59 pm »
We have an extensive set of metatypes and the Model Search will use the metatype as a synonym for the type field.  The problem is that the rendering appears to be "potluck".  For the same search with the same result set (in terms of objects returned - in this case, ALL of the same metatype), a varying number of the entries will have the type set to the metatype and others to the base class.  Run the same search again, a bit later and a different subset of the same result set will have the metatype and the rest the base class.

Anyone else seeing this?


Suggestions and Requests / Matrix Profiles: Tooltip for Search name
« on: September 20, 2017, 09:58:47 am »
We have meaningful and fairly explicit (and therefore long) names for our enterprise-wide model searches,  many of which are used in Matrix Profiles.

However, the name text box in the matrix profile dialog is quite small and the names overflow more than one "line".  This is particularly annoying when the same search is used with different search terms as the <Search Term> is the "first to go" and disappear into the second line.  On my machine, I can teasingly see the tops of the characters of the second line.

Can we please have a tooltip for the search specification in the Matrix Profile that provides the entire name?


Bugs and Issues / Model Search: One Of.. - trap for young players
« on: September 19, 2017, 05:21:19 pm »
The Help for Model Searches - says when using "One Of.." use a comma-separated list.

However, this is not actually the case for strings.  The set members need to be enclosed in the appropriate quotes.  Otherwise spurious errors will be generated.


Automation Interface, Add-Ins and Tools / ProxyConnectors - where to store?
« on: September 18, 2017, 05:19:39 pm »
We have grouped all our elements by metatype into specific branches of our repository.  We have automation to move elements around between folders when EA or our users don't put them where we need them.

EA now has t_object entries of type ProxyConnector (actually ConnectorProxy).  These are related to the end of a relationship that is NOT an element.  That is for relationships from relationships to elements and relationships between relationships.

We have folders for those items that don't end up in the browser and we manage those in a similar way behind the scenes.

My question is, where should we place these Connector Proxies.  They are placed somewhat arbitrarily as far as we can make out.  We suspect we run the risk that if we purge a folder that doesn't appear to have any objects within it we will inadvertently purge any ProxyConnectors.

Should we place them in the same folder branch as the origin object of the relationship or with the destination object of the applicable relationship?  Does it matter?


Pages: 1 2 3 [4] 5 6 ... 78