SysML flowPort appearance

[mpdelbuono]

Is it possible to override the appearance of a flowPort? I tried going into Settings->UML and changing the ShapeScript for the flowPort stereotype on Ports but this doesn't seem to have changed anything at all (even with very obvious changes like making the entire thing black).

I'm looking for a way to change the background color of a flowPort if another (specific) stereotype accompanies <<flowPort>> (that is, it is both a flowPort and has another stereotype <<foo>>). Any suggestions?

Thanks,
Matt

[Paolo F Cantoni]

Hi Matt,

I've recently spent (literally) weeks trying to sort out how to get stereotypes to activate in a consistent order.  Sparx have been cooperating to help me sort out what's going on in my MDGT.  I think I'll have some bad news for you...

Before I respond more fully, I need to know the details of how EA is applying the «flowPort» stereotype.  For a FlowPort, look in the t_xref entry that contains its stereotype identifier.  (Use a join from the t_object ea_guid to the t_xref client).  Report back what you find.

I can then give you some hints about what may or may not be possible.

Paolo

[mpdelbuono]

Hi Paolo,

Sorry for the late reply. Three-day weekend and all. See the below, which is, I believe, what you asked for. You will note that there are 3 stereotypes. Specifically, I'm looking for a way to easily identify the <<latch>> stereotype. Preferably this would be as simple as making that the visible stereotype on the diagram, but I'm open to any suggestions.

Code: [Select]

1> SELECT *  FROM t_xref JOIN t_object ON Client=ea_guid WHERE ea_guid='{8FD8F106-07FA-48ba-853A-4EA93C31E4F6}';
2> GO

XrefID: {88756B37-E05C-42a9-8552-4F7E0B0FE41B}
Name: Stereotypes
Type: element property
Visibility: Public
Namespace: NULL
Requirement: NULL
Constraint: NULL
Behavior: NULL
Partition: 0
Description: @STEREO;Name=CORBAStruct;GUID={7E249D45-27CB-4a8f-B326-3F07E5A2338B};@ENDSTEREO;@STEREO;Name=flowPort;GUID={A8240D62-38DF-4b7a-9AFF-05EB125A184B};@ENDSTEREO;@STEREO;Name=latch;GUID={66750FBF-DD99-418c-A91F-B8E0DA7C23A4};@ENDSTEREO;
Client: {8FD8F106-07FA-48ba-853A-4EA93C31E4F6}  
Supplier: <none>
Link: NULL
Object_ID: 66252
Object_Type: Port
Diagram_ID: 0
Name: Foo
Alias: NULL
Author: Matthew Del Buono
Version: 1.0
Note: NULL
Package_ID: 4336
Stereotype: CORBAStruct
NType: 0
Complexity: 1
Effort: 0
Style: NULL
Backcolor: -1
BorderStyle: 0
BorderWidth: -1
Fontcolor: -1
Bordercolor: -1
CreatedDate: 2010-05-27 13:55:16.000
ModifiedDate: 2010-05-27 13:55:16.000
Status: Proposed
Abstract: 0
Tagged: 0
PDATA1: {405AFD8A-49D0-4edf-85BC-44BDF49E3372}
PDATA2: NULL
PDATA3: NULL
PDATA4: NULL
PDATA5: NULL
Concurrency: NULL
Visibility: NULL
Persistence: NULL
Cardinality: NULL
GenType: <none>
GenFile: NULL
Header1: NULL
Header2: NULL
PackageFlags: NULL
Multiplicity: NULL
StyleEx: NULL

(1 rows affected)
1>


[Paolo F Cantoni]

Firstly a warning: Wrong stereotype identified may be in place here...  This will "DO your head in...".

So check that out (and support the bug fix).

Remove/rename any global stereotypes with the same names as those on the list.

Remove and reapply the stereotypes for that element.  Does the t_xref entry change?

Let me know the results...  Sorry for taking so long a route, but I also have a vested interest in sorting out EXACTLY what's going on here.

However, if after the reapplication, none of the stereotypes have an FQName= entry, make «latch» the primary stereotype and the rendering should change to that for the (new) latch - there should be a new global entry for «latch».

HTH,
Paolo