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 ... 530
At a guess, the dialog is showing the current selection like any other property.
<sound>LOUD Klaxon...</sound>

Then it's not a default!   There are two components to the dialog, the type and the value.  When there is NO link, the type should default to "Attribute" and the selection show <none>.  When a link exists, it should show both the type and the value of the link.  In my 10 years of use of this feature, I don't believe I have ever changed a setting in this dialog, once initially set, although I concede there is a use case for it (but it should be rare).


I want to change the Database property of a lot of Table elements, but I somehow cannot manage to access the property.
It seems not to be available in the selected element.
Does anybody of you know how to access it?
Geerts book "Scripting EA" does not mention table dialogs in the GUI reference, so are they not available via script? I also could bot find any values considering this in the database.
Design | Model | Manage | DBMSOptions...


Can someone please explain to me the reasoning behind the choice "none" as the default selection for the Link to Element Feature dialog?

One would assume that the default option should be the one that is most often used. I personally think the option "attribute" is used in more than 99% of the cases, but yet "none" has been chosen as the default value.
I'm pretty sure the actual usage of "none" is 0%. Nobody chooses the option "Link to Element Feature" in order to not link it to an element feature.

This type of thing is very hard to explain when giving a demo or explaining this feature. I usually resort to something like "yeah, weird choice, you know Aussies and all"

"Hush yo' mouth, sah!"  Your comment is an affront to those of us who live in 'straya!  Since the Sparxians live on planet Sparx, you can "dis" them all you want.

As you'd guess, I can't explain it, other than to observe that the meaning of the term "default" is more usually used "in the breach, than in the observance".


General Board / Re: Co-existence of EA16 -64 and -32 bit ?
« on: October 21, 2021, 11:02:21 pm »

General Board / Re: Sparx Blocks Password Manager = Bad Bad Not Good
« on: October 21, 2021, 11:10:10 am »
Hi Thelonius,

My password manager (Roboform) has no problem with these authentication dialogs.


General Board / Re: Co-existence of EA16 -64 and -32 bit ?
« on: October 21, 2021, 09:16:31 am »
Is it allowed to run both versions? What might be the result?
I know, I could try, and see what explodes, but that's like pressing the button which says 'don't press this button'...
See Eve's answer to my original query last week...


I found the solution...  Download the 32-bit ODBC driver (the 64-bit version seems to have problems) from this Microsoft site.  The driver allows the reverse-engineer of tables and views only.  ("still, better than a kick in the head")


While we can create a .accdb repository.  We want to reverse-engineer a .accdb database - to see what's in it.

I tried to link to it with ODBC, but the access driver we had crapped out.  Can it be done? If so, how?
The documentation doesn't seem to have any suggestions.


General Board / Re: Slow project transfer speed eapx to SQL Server
« on: October 19, 2021, 10:52:56 am »

We are using OLE DB SQL Server connection and were just wondering if anyone had similar slow speeds when transferring from eapx to SQL or have ideas what could be causing the slow speed.
Tried using the latest builds of V15.1 and 15.2
Hi Sunshine,

We have ALWAYS found .eap(x) to SQL Server transfers MUCH slower.  Consequently, we don't do it.  IIRC the last time we did it (say 5 years ago) it was 10 mins export, 6 hours import, for a 0.5Gb file.  Also, IIRC, the files were on the same machine!  We routinely snapshot out SQL Server repository to .eapx and it takes about 10-15mins for a 0.8Gb file between two machines (although in the same datacentre).  For the record, if we have to recover stuff, we use direct connections to both repositories and use SQL to recover the affected portions.


Hi Thelonius,

If you drag, say the table, onto a diagram, you'll see that its fully qualified stereotype is EAUML::table - so it IS a native EA MDG, probably Core Extensions.


Not really. When you ask the wizard to create the Property it will produce a Part (One of those EA bugs, you know). Then you have to manually rename the metaclass to property. Alternatively, you skip the wizard and create a metaclass manually and name it Property.

I think it's weird that the AssociationEnd is of metatype Property. But InstanceSpecifications are Objects too - in EA.

Yes, I was surprised that the stereotype's base class was an Association Role, particularly as I was adding it to a Dependency!


Bugs and Issues / Re: This weird "Unsaved Property Changes"
« on: October 16, 2021, 05:00:19 pm »
I ranted about this weird dialogue elsewhere. However, it's even worse. Just changing the tab in the connector properties (say from the Connector to Source) it pops up that weird warning when "clicking elsewhere". I did not change anything! Who has designed this dialogue? Could you please sem him back to scrub the floor again?

Yes, that's part of the bug I found with the DestStereotype (and I guess, SourceStereotype).


No, that does not work.


P.S. Uh, wait. Another bug. I created Property from the wizard (I hate those wizards) and it placed a Part. So I tested with Part. Well, well, ...

P.P.S. And yes: that works! Could we have some official documentation for that? (And maybe a fix for that Part thingy?)
Thanks, guys,
for the input.  So, is the upshot that I create a metaclass using the wizard, "Property" and then use the created "Part" metaclass to define the AssociationRole stereotype?

Glad I asked... ;)


This needs to be fixed ASAP!
If you try to set the TargetEnd Stereotype for a connector (via the dialog ellipsis), it is visible in the properties window and a shapescript can react to it (target.Stereotype value)!  The t_xref entry is correct.

HOWEVER, if you reload the diagram, the entry disappears from the properties window and the mark in the dialog is missing!  The shapescript will no longer react to the target.Stereotype value (since it's no longer cached in memory)!  Reloading the repository doesn't change anything.  If you reset the same value, you get a NEW entry in the t_xref, which ALSO disappears when you reload the diagram.

Truly EAUI!  As an Aussie, I am ashamed of such coding!

NOTE: I haven't tested this on v16β but, as q would say, I can bet money it's also present there!


For a very specific purpose, we are using the target stereotype on a specific form of connector.  We managed to create local stereotypes which we can use and they ended up being set (by EA) to the associationrole (as the base class in the dialog).  Having got it working with local stereotypes, we went to move the stereotypes to our profile.  Once we've moved them, we could fix the t_xref stereotypes entry to point to the profile instead of the local (and then delete the local stereotypes).

However, there doesn't seem to be any mechanism to create an associationrole metaclass from which to define the stereotype.  How can we create an associationrole stereotype in the profile?


Pages: [1] 2 3 ... 530