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 ... 78
16
Bugs and Issues / v14 Beta: Dialogs losing file references
« on: March 09, 2018, 01:02:25 pm »
A number of file-related dialogs are losing their memory.  In v13.5 and before the dialogs remembered their last values so one would just "Hit Return".  The Save as Profile... Dialog is particularly bad!   I've already overwritten the wrong file once!  Not to mention the added keystrokes to set up the file reference each time!   "Not happy- Jan"!

Anyone else seeing this?

Reported,
Paolo

17
If you have labels (for an element) generated with a shape script, if the [] Show Relationships checkbox is NOT marked (in the Connectors page of the Diagram Properties Dialog), then the label of the element can’t be selected!  (Sheesh!  :o )

Pure EAUI! ::)

My guess is that it is somehow related to the line from the centre of the element to the label which appears when the label is selected.

Reported,
Paolo

18
Bugs and Issues / v14 Beta: Advanced>Save as Profile... Missing
« on: March 08, 2018, 02:40:12 pm »
The Diagram context menu option:
Advanced>Save as Profile...
is Missing.

I can't "Save as Profile" like I used to be able to.

Anyone confirm this?
Reported,
Paolo


19
Bugs and Issues / v14 Beta: Technologies dialog crashing
« on: March 08, 2018, 01:22:02 pm »
Enabling/disabling technologies in the technologies window causes crashes.

Anyone else seeing this?

Reported,
Paolo

20
Bugs and Issues / v14 Beta: Missing MDG
« on: March 08, 2018, 01:19:17 pm »
Trying to open our production repository (SQL Server) I get:
Access to this model requires the following technologies which are not available:
SIMPLE

Which MDG is this message referring to?

Reported,
Paolo

21
General Board / EA v14 Beta - how to re-use your old layouts
« on: March 08, 2018, 12:25:30 pm »
We went to a LOT of trouble to set up specific window layouts for our various configurations.

In the upgrade from 12->13, we just copied our old layouts to the new directory ...\AppData\Roaming\Sparx Systems\EA\Workspace Layouts13 and off we went.

When we tried to do the same with v14: ...\AppData\Roaming\Sparx Systems\EA\EA1405Workspace-Layouts
we found the file format was not supported!  ::)

However, replacing the Sparx Systems Registry Exporter xx.x.xxxx with Sparx Systems Registry Exporter 14.0.1400
allowed us to at least import the layout.  It didn't quite come in correctly, but it SURE beats setting them up from scratch!

Saving the imported layout seems to work fine!

HTH,
Paolo

PS: Perhaps Sparx could allow import with a warning?  ;)

22
In a number of places, EA uses the results from an EA Search to do additional things.  For example, the Relationship Matrix.  In an enterprise environment, the same object may have multiple names/identifiers.  We have developed a multi-naming technology that relies on a "trick" to get around the fact that EA only allows at most two names (the Name and Alias).  The trick allows us to place a user selected name for an element on a specific diagram.  However, these additional names aren't available to the rest of EA.

It occurs to me that if we extended the CLASSGUID and CLASSTYPE tokens which provide specific functionality out of the searches, to include CLASSNAME and thus provide the "designated" name to be used, it would be very useful.  The search query would determine what value to supply as CLASSNAME (as it does for the other two tokens).

Thoughts?
Paolo

23
Automation Interface, Add-Ins and Tools / Importing Archi Models
« on: February 28, 2018, 04:21:28 pm »
Is there an easy way to import Archi models?  One of our users has a few and we'd like to save him the trouble of recreating them in Sparx EA.  He still has access to Archi, so if we need special export he can do that.

TIA,
Paolo

24
Bugs and Issues / How to enable the UML Element Toolbar
« on: February 26, 2018, 02:07:47 pm »
The Diagram Note Element is on the UML Elements Toolbar.  One of our Users has "lost" the toolbar, but there doesn't seem to be any way to enable it again.

It's not on the list of Start | Show | Window | Show Toolbar > ...

Help!

TIA,
Paolo

25
Automation Interface, Add-Ins and Tools / XSD Generation and Relationships
« on: February 19, 2018, 11:06:33 am »
We are experimenting with XSD round-tripping (but principally generation).  With RDBMS round-tripping there is the option of suppressing or including relationships are part of the process.

We have noticed that if we try and "visualise" the relationships between the XSD componentry (via composition and other relationships) when we generate we find an entry for the attribute and an entry for the relationship.  In the example below, the entries where the name and the type are the same are from the relationship, the others are from the attribute.
Is there any way to suppress/control the use of relationships?
Code: [Select]
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:complexType name="Message">
<xs:sequence>
<xs:element name="Header" type="StandardMessageHeader" minOccurs="1" maxOccurs="1"/>
<xs:element name="Status" type="StandardStatusMetadata" minOccurs="1" maxOccurs="1"/>
<xs:element name="Payload" type="MessageSpecificPayload" minOccurs="1" maxOccurs="1"/>
<xs:element name="StandardMessageHeader" type="StandardMessageHeader" minOccurs="1" maxOccurs="1"/>
<xs:element name="StandardStatusMetadata" type="StandardStatusMetadata" minOccurs="1" maxOccurs="1"/>
<xs:element name="MessageSpecificPayload" type="MessageSpecificPayload" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="MessageSpecificPayload">
<xs:sequence>
<xs:element name="element1" minOccurs="1" maxOccurs="1"/>
<xs:element name="element2" minOccurs="1" maxOccurs="1"/>
<xs:element name="element3" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="StandardMessageHeader">
<xs:sequence>
<xs:element name="element1" minOccurs="1" maxOccurs="1"/>
<xs:element name="element2" minOccurs="1" maxOccurs="1"/>
<xs:element name="element3" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="StandardStatusMetadata">
<xs:sequence>
<xs:element name="element1" minOccurs="1" maxOccurs="1"/>
<xs:element name="element2" minOccurs="1" maxOccurs="1"/>
<xs:element name="element3" minOccurs="1" maxOccurs="1"/>
</xs:sequence>
</xs:complexType>
</xs:schema>
TIA,
Paolo

26
Automation Interface, Add-Ins and Tools / Can we hijack «trace»?
« on: February 16, 2018, 11:04:18 am »
Time Aware Modelling (TAM) uses the «trace» relationship to link the "doppelganger" to the "base" item.  The instantiated trace relationship is a "local" stereotype (not connected to an MDG).

We wish to "hijack" this relationship and create an MDG based «trace» relationship (so that its t_xref value changes from @STEREO;Name=trace;GUID={<guid>};@ENDSTEREO; to @STEREO;Name=trace;FQName=<MDG>::trace;@ENDSTEREO;), to allow us to alter the rendering and to add additional properties. It would appear that "with no loss of generality" this is possible.  Can anyone confirm?

TIA,
Paolo

27
Anybody else attempted to create shapescripts for RequiredInterface or ProvidedInterface elements?  They SURE are different, aren't they?

Among some of the issues we've found is that there is NO real distinction between Rectangular form and non-Rectangular form.  In fact, the drawnativeshape() only works for the Rectangular mode.
You can't change some of the drawing properties from within the shapescript - so that the behaviour of drawnativeshape() behaves differently than for most other element types.
Regardless of whether you define the MDG to have the base type in the metatype definition, it pops up the Provided/Required dialog (and it doesn't even change the radio button to the correct one)!

As part of our consistent modelling environment, we require each metatype to have a unique stereotype - so the stereotype is a proxy for the metatype.  If the user isn't watching what they are doing when they will create an inconsistent metatype.  Does anybody know how to suppress that dialog or at least to be able to specify the right interface type?

Thoughts?  (Before I report a set of bugs?)
Paolo



28
I'm pretty sure I know the answer  ;), but just in case, has anyone used the API to do any time aware modelling?

As mentioned in another thread, we're looking to intercept the cloning process to add some additional functionality post process.

Also, is the element.Clone() the only method used?

TIA,
Paolo

29
Bugs and Issues / TAM - Incorrect item cloned!
« on: January 22, 2018, 12:57:13 pm »
We've found what we consider a SERIOUS defect in TAM (Time Aware Modelling).

Scenario:  We have a set of current items, in diagrams in a branch versioned "Curr".

We intend to make a RoadMap branch indicating the "To Be" state.  We clone the Current Branch - which gives us new Folder structure and Diagrams (but not the items) - which is what we want; to a branch versioned "RdMp".  Since we only want to clone items that will change in the future.  We clone an item in a RdMp diagram to version "RdMp".  The item is cloned correctly; so far, so good.

As part of our on-going repository management, every year (at the end of the year) we intend to clone Current into a "Past" "snapshot" that describes the state at the end of that year; giving us the ability to "compare and contrast" over time.  So I select the Current branch and say Clone structure (in this case, to a folder structure versioned "Past").  Again, folders and diagrams cloned, no items, as desired.  This time, however, to achieve our goal of snapshotting the entire Current branch we have to clone ALL the items in the "Curr" version.  We select all the items in the diagram in "Past" diagram (which are all namespaced "Curr::") and say Clone to new version (to "Past").

Imagine our surprise when for the item in "Curr" that had been cloned to "RdMp", instead of getting a new item in "Past", we got the "RdMp" item on the "Past" diagram!  :'(

We confirmed that the original item on the Current diagram was still the "Curr" item and that that item WAS NOT CLONED into Past as a new item.  This is a defect, the original "Curr" item (on the diagram) should have been cloned, not the "RdMp" item (which was nowhere to be seen).  We also confirmed it's not a caching problem since we exited Sparx and re-entered and then cloned the structure. This needs to be fixed urgently!

Reported,
Paolo

30
We are about to embark on a serious implementation of Time Aware Modelling (TAM) in our corporate repository.

As we understand TAM, if we have the different versions (of items) in their individual branches, we can use items from another version in the diagrams for a specific version.  So far, so good.

When we clone an element (from another branch from within a diagram in this branch), a clone of the external element will be created in the current diagram branch.  The external element in the diagram will be replaced by the cloned element in that diagram.

Question:  Is there any mechanism to replace the external element in every diagram in the appropriate version, or will we have to "roll our own"?

TIA,
Paolo

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