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.

Messages - Paolo F Cantoni

Pages: [1] 2 3 ... 544
Thanks, Helmut!

I believe the response from the Sparxians isn't quite correct.  They imply that .NET Framework is aligned with .NET, but that's not the case is it?
There is NO .NET 6.0 Framework, is there?

BTW, when you were experimenting, did you manage to find the "Make the assembly COM-Visible" setting?


General Board / Re: Name followed by Alias
« on: June 24, 2022, 07:58:19 pm »
In version 15, enabling this applies to both elements and connector aliases, including the aliases at both ends of the connectors. Showing the aliases at both ends of the connectors enclosed in parenthesis does not sound right, by definition connector ends don't have names.
Hi Modesto,
Can you elaborate on why you believe this to be the case?

I am reminded that "a named association end IS an attribute" (from early UML), thus connector ends can have names (at least some).


Thanks, Geert,

I was told by a colleague that the reason .Net 6.0 doesn't support COM-Visibility is that .Net 6.0 is cross-platform and thus has lost the ability to support COM interoperability.  Can anyone confirm or deny this?


I've had to rebuild my Add-In infrastructure from scratch as I can't get the symbol tables to load to allow debugging.
I've managed to rebuild creating Solution and Project files from scratch and resolved any Errors and (most important Warnings).  However, when I try to make the DLL file COM-Visible, the option isn't there in the Project properties.  Researching this via Google implies that I need to build the Add-In as a .Net Framework (instead of using a .Net or .Net Standard template - as I did originally).

Since I'm not a .Net guru and haven't touched Visual Studio for years, am I correct in understanding that in order to create an EA Add-In I must make it COM visible and thus am limited to a .Net Framework template that only goes up to .Net Framework 4.8?


Notwithstanding the fact that Sparx has rejected a (to some of us) request to have the ability to open a new diagram in a new tab (similar to "concise navigation" in web browsers (see:,43166.msg264550.html#msg264550), we've persisted in trying to use "concise navigation".  This started under v15, but as of v16x, we are unable to find any rhyme or reason as to why even if you go to the Project Browser and try and open a new diagram it will NOT open a new diagram tab, but replace one of the existing tabs as if you had tried to use concise navigation from within that diagram.

What is the algorithm that EA uses to determine which tab the new diagram from the browser will occupy?  It's driving us nuts!  So unproductive!

Has anyone else seen this?  Is it just as annoying for you?


Thank you Eve, you made my day. :)

Wot 'e sed!

No, the relationship isn't incorrect, the words in the Trace window and on the QuickLinker menu are wrong. The OP doesn't need to do anything to his model except to carry on modelling...
Thanks for clarifying, KP.  I was a little confused since the "standard" Trace relationship is fine.


Oh Boy now what do we do  ???
n this type of situation, we rewrite our custom shapescript to draw the incorrect relationship in the correct way, but we don't extend other MDGs (usually) so it's easier for us.
An alternative might be to reverse the direction in the repository (via SQL).  Then when the fix arrives (if ever), you can revert.

Sorry if that's not much help.


The code I shared actually traverses some of the relations and puts them onto the diagram.

There's not much more I can do. You'll have to dig in, and try it yourself. If you find yourself stuck, by all means, post here (although maybe next time use only black text, my eyes hurt a bit trying to read your colourful posts ;D )

Yes, Rob, Geert is now an old man, and I am even more ancient!   ;D   Do keep us in mind when posting.  Even with my reading glasses on it was too hard to read your post.  If you see some of my posts over the decade or so, you'll see I'm not averse to colour, but it must be used judiciously!   ;)


General Board / Re: How to close a Portal Window
« on: June 19, 2022, 10:55:47 am »
I remember I was searching for that menu for the first time for quite a time. EA as usual...

15 years of using EA and I never thought to do that before...  :o

Learn something new every day!  I always went for the dropdown, pin and cross -which should have been consistent across ALL windows with this functionality.  EAUI strikes again, as you say.

Anyway, thanks Geert!  Geert to the rescue, as usual!  :D


I stumbled over this too and found no solution. Except you would write an add-in for it.


General Board / Re: How to close a Portal Window
« on: June 17, 2022, 09:58:46 pm »
Offline now. But IIRC, in the context of the top bar, there's a Hide.

Sorry, q, not that I can find. Can you confirm with your version?


As we know, setting the background colour and border in an MDG will cause the created element to have those properties.  I tried to set the Notes compartment to visible and the size of the note in the MDG for the stereotype, but this didn't transfer to the created element.

Is it possible?  If so, how?

General Board / How to close a Portal Window
« on: June 17, 2022, 12:47:42 pm »
I normally DON'T have the Portal window open.  However, I needed to use it and then accidentally save that arrangement as my default.
No problem, I'll just close the Portal window and resave!   ;)

Err...  Can't seem to close the Portal window.  Can a kind soul tell me how to do it?


Does anyone know why EA doesn't allow MDGs to create alternate project browser images for extensions to 'package' ? There's just a 1-liner in the documentation (V15.2:  'This does not apply to package elements").
Has anyone tried to get around this by defining a specialization of an element instead - for example as an extension of 'class' - and using this in place of a specialized package? Seems like most things will still work, except stuff like 'show package contents' in diagrams. Are there any big gotchas out there?
I seem to want this capability quite a lot, to show the modeller that not all packages are alike, and some should have certain kinds of elements, and others ones other kinds. Seems intuitive.
Is it possible to decorate the built-in icon?
@Sparx - is this just something you didn't get around to yet, or is there some deep reason why we shouldn't do it?
Hi Ian,
It won't surprise you to find "I've been here, done that!"!  We have a number of package stereotypes each with its own icon.  They are managed in the normal way (icon attribute on the stereotype).  However, the instantiation of the icon in the browser during EA use can be intermittent.  Most of the time it's fine, but occasionally it "disappears" to return with a reload of the package content.

Sparx refused to fix what (to me and others) appeared to be a defect.

There you have it.

Pages: [1] 2 3 ... 544