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 ... 80
46
We've started to look at converting our "hand-rolled" MDG file to a formal MDG metamodel using the MDG Generator.

One nice thing about our hand-rolled version is that WE decide what the order of the stereotypes is.  Is it possible to influence the output order via the generator?

TIA,
Paolo

47
Bugs and Issues / TAM- confusing UI
« on: April 12, 2018, 04:47:51 pm »
Following some feedback on TAM - Incorrect item cloned! Sparx advised that: "Time-aware versions can be built sequentially, but not in parallel."

What this means is that if you have an item that has been cloned, you should not be able to clone it again!  Indeed, this appears to be the case.  However, the UI doesn't indicate this.  The "Clone Element as New Version..." context menu item is still enabled for the original item.

Furthermore, executing the menu item will replace the original item on the diagram with the latest clone.  I say the latest clone because if there is a chain of (say 5 items each one cloned from its predecessor), and you are selecting the first (original) item, the original item will be replaced by the fifth item.  Note further, that I said replaced, not cloned, since NO cloning has, in fact, taken place!  Now, to be clear, I have no problem with the end result (if that's what I understood would happen- - given "sequential only" cloning).  Once the latest clone has been inserted into the diagram, executing the "Clone Element as New Version..." a second time will NOW create a new (in this case 6th item)!

The concept of Time-Aware Modelling is difficult enough without confusing matters further by using the wrong terminology so that the unexpected happens (AND you can't reverse the effects once you've executed the menu item!).

Now, the "Clone Element as New Version..." menu item can be disabled by EA for a variety of circumstances (still to be fully investigated by us), so it's not as if EA can't work out when to enable/disable the item.  In some cases, the "Clone Element as New Version..." is enabled, but when you execute it, nothing seems to happen.  That would suggest that it should have been disabled.

In the case of the chained clones above, selecting any item other than the latest clone should enable the "Replace Element with Latest Version" (replacement) menu item.

In an enterprise setting, anyone may have created the diagram you are working on at any time in the past, you (AFAIK) have NO visual indication that the item you  are wanting to clone has already been cloned, so it is vital that you are assisted by the system in understanding what will happen if you execute the menu item.

Reported,
Paolo

48
Bugs and Issues / v14Beta: Issues with MDG profiles
« on: April 12, 2018, 01:55:25 pm »
Something has gone horribly wrong with MDG management in build 1415.

Attempting to load/unload an MDG (even standard ones) in 1415 will cause a crash.

The MDG patterns for the projects we have in 13.5 are no longer visible in the Package creation dialog (Model Wizard). They used to be visible right at the end of the list, but now aren't there at all!

The Toolbox management process also ignores the MDG supplied toolbox configuration profiles - they are no longer visible on the list (More Tools... in 1352).

Because this is missing, we can't work around a caching bug we have found with the toolbox profile itself. We thought this was an exclusively v14 bug, but we have found the issue with 1352 also.
When we changed the profile (for example changing the isCollapsed status of a toolbox section), this would not be reflected in the toolbox. However, we have discovered that it's a caching problem since (under 1352) if we reselect the profile via the "More Tools...", the "Correct" toolbox (as opposed to the "Cached" toolbox) could be made to appear.

Interestingly, exiting EA and reentering DOES NOT show the "correct" toolbox, but the original "cached" toolbox.

Consequently, since we can't reset the profile (since it's not visible on the list) we can't use v14! EAUI rearing its head?

Reported,
Paolo

[Edit: Oh, I forgot...  You also can't add a diagram type that's specified in the profile. The New Diagram dialog doesn't include the list of Profile diagrams.]

49
On out Neighborhood diagrams, we list all the diagrams that the main item (the Root Vertex) appears on (that aren't Neighborhood diagrams of the related items) as hyperlinks.

However, we'd like to open the diagram with the nominated item as the focus - Find in All Diagrams [Ctrl+U] Functionality.

Is there a syntax or property we can encode in the hyperlink to get it to move the focus to the nominated element?

TIA,
Paolo

50
Bugs and Issues / v14Beta: Local MDG projects at end of very long list
« on: March 23, 2018, 01:41:11 pm »
When you try to add a project with a local MDG specified pattern, it is placed at the end of a very long list on the Model Patterns tab!  Can we either have them at the top or in a separate tab on the dialog?

Reported,
Paolo

51
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

52
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

53
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

54
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

55
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

56
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

57
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

58
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


59
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

60
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

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