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 ... 106
1
Automation Interface, Add-Ins and Tools / Element Names and Notes
« on: January 17, 2022, 02:48:59 pm »
We have the ability, with our Shapescripts to apply additional names to an element besides those in the Name and Alias fields (via the use of the Label subshape).  We also have the ability to render more than one shape when in non-rectangular (i.e. icon) mode.  However, while all this is useful, the one thing we CAN'T do at present is to show the Notes field in non-rectangular mode.  Neither can we shoe a name other than the name or alias fields in rectangular (i.e. compartment) mode.

Does anyone know how we could accomplish either being able to use an additional name in rectangular mode or render the notes (preferably in rich text) in non-rectangular mode?

TIA,
Paolo

2
Automation Interface, Add-Ins and Tools / v16β - new .EAPX schema?
« on: January 13, 2022, 03:29:06 pm »
We have a number of .eapx files that are generating a
"DAO.Database [0x00000d0e]

Invalid Memo, OLE, or Hyperlink Object in subquery 't_object.PDATA2'"
error under v16β (both versions).

Searching the Net doesn't bring up anything as to what the error means.

We have (in the past) "hijacked" t_object.PDATA2 and this has caused NO problems up to and including v15.2.

Since null is a valid value for PDATA2 we ran a test making the column null for all objects.  The problem persists and the upshot is that NO diagrams show ANY objects (whether PDATA2 is null or not).

Did we miss a schema change between v15 and v16β?  If not, what can this error mean?  Anyone else seeing this?

TIA,
Paolo

BTW: in the past, we have had error messages from EA that are spurious - that is the error is NOT what is claimed.  Unfortunately, as in this case, the actual problem can't be determined since the message provides no direction for the investigation.

3
When I started up one of the repositories we have this morning, I got the message:

"Ignoring metaconstraints for Stereotype from profile: <our profile>"

Is "Stereotype" the affected element[1]?  Or is the affected stereotype not shown?

TIA,
Paolo


Our profile does have a metaclass called "Stereotype" as shown below.
Code: [Select]
<Metaclass name="Stereotype" notes="">
   <metarelationships>
      <metarelationship metaclass="UML::Extension" constraint="StandardProfileL2::Metaclass"/>
   </metarelationships>
   <stereotypedrelationships>
      <stereotypedrelationship stereotype="PrIME::SeeAlso" constraint="Stereotype"/>
   </stereotypedrelationships>
</Metaclass>

4
Suggestions and Requests / v16β - Ellipsis for shortened Notes
« on: January 10, 2022, 04:57:23 pm »
Many of our items (especially those in our ontological models) have lengthy definitions and/or descriptions (sometimes many hundreds to - occasionally - thousands of characters) in the Notes field. We developed a mechanism to allow us to break these notes into separate portions. We created a "widget" (in this case the string "<--+-->"). By convention, text before the widget is the normative definition of the item (the notional "25 words or less"), whereas text following the widget is used for discursive narrative providing more detail about the item, its usage etc. We have a script to set the length of the visible notes to the start of the widget. Thus we only provide the full notes on the appropriate diagrams and no or minimal notes on the majority of diagrams.

The problem is that the script does such a good job of hiding the (larger) detail that often users aren't aware of "but wait, there's more!". We feel it would be most useful to provide an ellipsis character at the end of the shortened note display to indicate that there is more text but it is not visible. The use case I have outlined is our specific usage, but the use of the ellipsis to indicate a shortened note is of general applicability.

Thoughts?
Report,
Paolo

5
General Board / Can't enter "em-dash" in title...
« on: January 10, 2022, 04:16:46 pm »
There's a problem

6
Bugs and Issues / v16β – Notelink visual anomalies
« on: December 03, 2021, 02:07:09 pm »
Notelinks seem to be special!  They can appear to be disconnected from their shapes.

It IS connected since one can move it back...

Except if you try to connect it to the bottom.  The link won't get any closer than...

Drag it to one of the other edges, it connects correctly.

(BTW: also fails in v15)

Reported,
Paolo

7
We have just discovered that we have an issue with shapescripts that inherit the shape "Label".
In v15.x - following advice from Eve, we abstracted the shape Label from our items so that we could have a standard set of such labels.  For example, we have a label at the centre of the item, another at the southern end etc.  Under v 15.x, the code below operates are desired and will create a label in the "Southern" position of the item (BUT only under non-rectangular form).  The shapescript is inherited by a large number of items (where we wish to have the label default to the southern edge).  It works fine.
Code: [Select]
shape Label   //v2.2 29-Nov-2021   //@S
{
   if(hasproperty("rectanglenotation","0"))   //label only in Icon Form
   {
      setorigin("S",0,0);
//SoF: [[PrIME Naming (Label)]].sub.shp   v1.2   29-Nov-2021
      if(hasproperty("Nm.Prfrrd","1"))
         if(hastag("PreferredName"))
            print("#TAG:PreferredName#");
         else
            printwrapped("?PreferredName Tag - missing!");
      else if(hasproperty("Nm.Nrmtv","1"))
         if(hastag("NormativeName"))
            print("#TAG:NormativeName#");
         else
            printwrapped("?NormativeName Tag - missing!");
      else if(hasproperty("Nm.Abbrvtd","1"))
         if(hastag("AbbreviatedName"))
            print("#TAG:AbbreviatedName#");
         else
            printwrapped("?AbbreviatedName Tag - missing!");
      else if(hasproperty("Nm.Smntc","1"))
         if(hastag("SemanticName"))
            print("#TAG:SemanticName#");
         else
            printwrapped("?SemanticName Tag - missing!");
      else if(hasproperty("Nm.Spcd","1"))
         if(hastag("SpacedName"))
            print("#TAG:SpacedName#");
         else
            printwrapped("?SpacedName Tag - missing!");
      else if(hasproperty("Nm.Adhc1","1"))
         if(hastag("AdHocName1"))
            print("#TAG:AdHocName1#");
         else
            printwrapped("?AdHocName1 Tag - missing!");
      else if(hasproperty("Nm.Adhc2","1"))
         if(hastag("AdHocName2"))
            print("#TAG:AdHocName2#");
         else
            printwrapped("?AdHocName2 Tag - missing!");
      else if(hasproperty("Nm.Archtctr","1"))
         if(hastag("ArchitectureName"))
            print("#TAG:ArchitectureName#");
         else
            printwrapped("?ArchitectureName Tag - missing!");
      else if(hasproperty("Nm.NrmAbb","1"))
         if(hastag("NormativeName"))
         {
            printwrapped("#TAG:NormativeName#");
            if(hastag("AbbreviatedName"))
               print(" (#TAG:AbbreviatedName#)");
            else
               printwrapped(" (?AbbreviatedName Tag - missing!)");
         }
         else
            printwrapped("?NormativeName Tag - missing!");
      else if(hasproperty("Nm.AbbNrm","1"))
         if(hastag("AbbreviatedName"))
         {
            print("#TAG:AbbreviatedName#");
            if(hastag("NormativeName"))
               print(" (#TAG:NormativeName#)");
            else
               printwrapped(" (?NormativeName Tag - missing!)");
         }
         else
            printwrapped("?AbbreviatedName Tag - missing!");
      else if(hasproperty("Nm.Als","1"))
            print ("#Alias#");
      else if(hasproperty("Nm.ActlNm","1"))
         print ("#ActualName#");
      else
         print ("#Name#");
//EoF: [[PrIME Naming (Label)]].sub.shp   v1.2
   }
}      //Shape: Label   //@S
Under v16β, the label is made visible under all circumstances (i.e. both non-rectangular and - anomalously - under rectangular forms).  Other parts of the shapescripts respond correctly to the IsProperty("rectanglenotation","0")) conditional, so we suspect a problem with shape inheritance.

Anyone else seeing this?
Reported,
Paolo

8
In previous versions, you could quickly get the "schmick" diagram layout by "nudging" the end-points of the line.  Doesn't seem to work AT ALL in v16β!  it's a REAL Pain!  Even holus-bolus moves of Direct Line Style lines don't work.


Anyone else seeing this?


Paolo

9
It seems as though when we Purge items from the repository under v16β, the Integrity Checker is broken (since it returns immediately), but more importantly, it seems as though the Purging process doesn't clean up after itself (purging related rows from the various tables).  If we run the v15.2 on the same repository after we have purged the item, it finds a pile of errors - apparently related to the item (since in a massive UI fail, the IC doesn't tell you the affected items).


This is MOST concerning!  Anyone else seeing this?  If true, needs fixing NOW!


Reported,
Paolo

10
Just tried to publish a series of HTML reports using a script (under 64-bit).  The diagrams look good, but the Navigations cells on the diagram don't work - that is, they don't Navigate!


Repubiished under v15.2 works fine.


Anyone else seen this?


TIA,
Paolo

11
Bugs and Issues / v16β – Weird message on .eapx opening
« on: November 17, 2021, 12:47:32 pm »
Opening a pre-existing .eapx file with a default diagram, we get an error message:
"Invalid Memo, OLE, or Hyperlink Object in subquery 'to_object.PDATA2'."
The default diagram has a set of Navigation Cells and a couple of diagram Hyperlinks.  When we click [OK] on the message, we are presented with a blank diagram.


We immediately checked t_object.PDATA2 for rows of type "Text" and found NONE had anything other than NULL for the PDATA2 values.
So what is this message telling us?


Reported,
Paolo

12
General Board / v16β – Consistency check?
« on: November 16, 2021, 03:41:18 pm »
When I run the Consistency Check on our Production Clone, it returns immediately with NO errors.  Suspicious...

Anyone else seeing this?

TIA,
Paolo

13
General Board / v16β – New Element... Dialog - dropdown confusion
« on: November 16, 2021, 02:07:38 pm »
The Type dropdown used to present an ordered list of the metatypes in the selected MDG.  The order in v16βis (apparently) random.

Took me AGES to find the right metatype!

Needs fixing!

Reported,
Paolo

14
General Board / v16β – Navigation Cell - New Rendering
« on: November 15, 2021, 01:38:38 pm »
Well, I finally got to install v16β on a non-production machine.
One thing that intrigued me was the new rendering of the Navigation Cell.  The circle is now within the rounded rectangle and has moved from top right to bottom right.


Can anyone provide the rationale?  Not complaining, just interested.


Paolo

15

Apparently one can create an HTML report via the Project Class method:
RunHTMLReport (string PackageGUID, string ExportPath, string ImageFormat, string Style, string Extension)
However, one of the options you can use when you do it manually is to choose the current diagram as the initial diagram to display.
How is this possible under automation?  There isn't any place to do it in the API call.

TIA,
Paolo

Pages: [1] 2 3 ... 106