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 - Simon M

Pages: 1 2 3 [4] 5 6 ... 422
If you don't want EA to set filenames for you, don't check "Auto Generate Files". (

Short of creating an MDG add-in, there's nowhere EA calls code you can write to request the filename. The easiest solution is to write a script that sets the filenames for all classes as needed.

Bugs and Issues / Re: IIS Configuration
« on: April 19, 2018, 09:23:56 am »
The Application Pool settings in the EA help say that you need to enable 32-Bit applications. It sounds like you haven't done that.

From memory, enabling auditing upgrades the version to 7.0 to that versions of EA prior to version 7 know they shouldn't use it.

Disabling auditing either gives you the option of going back to 4.01 or does it automatically.

In a similar way, if you set a minimum EA version in the model options, it changes the version to something that old versions of EA that don't know about the option just set won't open.

Bugs and Issues / Re: Pro Cloud Server Installation
« on: April 19, 2018, 09:18:11 am »
From what I can see, that's all the shutdown in response to the error.

Much easier if you send the full log to support.

Metatypes too, please!  We're trying to wean our users off stereotypes - which in our MDG are quite cryptic and move them to metatypes.
Did you even look at what was being requested? It's used metatypes for years.

Bugs and Issues / Re: Pro Cloud Server Installation
« on: April 18, 2018, 09:09:37 am »
I'd recommend running the installer with full logging (msiexec /L*vx installlog.txt /i c:\path\to\installer\cloudinstaller.msi) and sending the log to sparx. That should allow us to work out what's going wrong.

Bugs and Issues / Re: Downgrading from 13.5
« on: April 18, 2018, 08:54:31 am »
Uffe, the schema upgrades will work with practically any version of EA.

That function hasn't been added to the API because it requires user feedback on how to handle dependencies.

The MariaDB ODBC driver is not similar (enough) to the MYSQL ODBC driver.
Unless I'm mistaken, the part that isn't similar enough is that it identifies itself as MariaDB ODBC instead of MySQL ODBC. EA version 13 doesn't know what that driver is, or how to use it. I believe version 14 allows you to use the MariaDB ODBC driver.

I confirmed that I am using the latest MDG packages.
How? Did you go on to our webpage and download the latest installer for both add-ins? Then uninstall the old ones and install the new? What version information do the add-ins give in EA and in the properties of the installer?

2. When I open sample models, I get the "Cannot Create XML Document" at least three times, five times for the ZF example.
This is another sign that you aren't using the latest add-ins. The old version of those add-ins relied on EA installing something it no longer installs.

Bugs and Issues / Re: Python reverse - empty result
« on: April 10, 2018, 08:38:26 am »
You may be able to use the gdb debugger to do that, but I suspect the gdb support for python is in the UI side, not the API side.

That extra information makes a difference. It seems like the logical or operator is ignoring the right side. I certainly can't explain why.

I'd say it has to do with the way COM handles booleans, and that JScript has a closer integration with COM than Javascript.

COM is unusual as a framework that the integer value of true (VARIANT_TRUE) is not 1. It's -1. Apparently JScript handles that, but the way COM is being called from Javascript isn't wrapping that value into a 'normal' true. It doesn't make any difference until you try to compare it. Then again, I remember being told very early on that you shouldn't try to compare two different true values.

Code: [Select]
Stereotype: testcase
HasStereotype('testcase'): true
HasStereotype('testcase') == true: false

As with version 13, it will only place one parameter for each unique name.

'Select...' brings up the 'Interaction Points'1 dialog

1 Interaction points is a name directly from the UML specification. it was formerly known as Structural Elements and further back Embedded Elements.

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