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 / setpenwidth() does not propagate to sub-shape
« on: March 22, 2018, 05:48:47 pm »
The penwidth() setting doesn't seem to propagate to a sub-shape, whereas the other pen related methods do.

Code: [Select]
setpencolor(getuserbordercolor());
setpenwidth(getUserPenSize()); //<-doesn't work
setfillcolor(getuserfillcolor());
addsubshape("X",100,100);
shape X
{
noshadow=true;
setpenwidth(getUserPenSize());//<- need to set it here!
startpath();
...
}
Please rectify.  NOTE: this is also true of setpen()

Reported,
Paolo

17
We're finding asymmetrical problems with link:<relationship type> QuickLinker entries.

Code: [Select]
// Everything can derive (by traversal) from anything else
link:Abstraction,,link:Abstraction,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:Aggregation,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:Association,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:Composition,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:ControlFlow,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:Dependency,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:Generalization,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:InformationFlow,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:Nesting,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:NoteLink,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:Realisation,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
link:Abstraction,,link:Substitution,,,,,Abstraction,Drvtn,to,derives from,derives from,True,,,True,Derivation,0,,,,,&#xA;
(we've n x n of these)

So in both directions, we should be able to derive one type from another.  However, it's not working under v14 (1405).  Sometimes it works in one direction but not in the reverse.  Sometimes in neither.  Information Flows seem to be the worst.

Works fine under 1352 (and prior versions).

Reported,
Paolo

18
We have decided that we want to attach details of the REST API endpoints to our Required or Provided Interfaces (as operations on the interface).

The problem comes when we want to render them.  Even if we create a shapescript which has both Rectangular and non-Rectangular notation forms, Required and Provided Interfaces are "special" - there is no Rectangular form as we usually know it (drawnativeshape() - ONLY draws a ball or socket).  In addition, the sizes are (pretty much) fixed. The scripts don't respond to defsize() requests (although, in typical EAUI fashion, Ports do!).

So my question is, is there a way to make an MDG item be defined as "attached" (aka embedded) directly in another item?  In that way, we could use some other form of item (which does support Rectangular notation) as the basis for our specific Required or Provided Interfaces?

Paolo

19
Bugs and Issues / v14 Beta: Workspaces vs My Workspaces
« on: March 19, 2018, 05:12:41 pm »
It is an axiom of natural language processing that an unqualified noun includes all the subtypes.

Consequently, having two tabs on the Start | View | Workspace | Select a Workspace page named, Workspaces and My Workspaces is incorrect.

The Workspaces tab lists only workspaces, the My Workspaces tab lists my Custom workspaces and (in this case) the BABOK technology workspace - which is NOT one of my and smells more like a system than a personal workspace.

Perhaps General Workspaces and My Workspaces (with Technology Workspaces in General)?

Reported,
Paolo

20
As I've mentioned, we "hand roll" our MDG.  Don't ask...  However, before I go down a spurious track (and waste a PILE of effort), I'd like to confirm that I can theoretically do the following...

We have a number of components that are very similar.  At present, each has it's own metatype (to make it easy for the modeller to select the one they want to drag off the toolbox).  But, in fact, they are pretty much the same metatype but with a specific property set to an enumerated value.  The property can be a tagged value.  What I'd like to be able to do is have one metatype on the toolbox and as the modeller drags it off the toolbox, it asks which "subtype" it is (using the hidden menu) and sets the tagged value appropriately.  I realise I can do it with scripts and events, but I'm after a declarative solution if possible.  Our shape script (for the metatype) can then respond to the tagged value.

TIA,
Paolo

21
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

22
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

23
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


24
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

25
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

26
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?  ;)

27
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

28
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

29
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

30
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

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