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 - Aaron B

Pages: 1 [2] 3 4 ... 58
As Geert suggested, assign your value to StereotypeEx, not Stereotype.

Assigning values to Element.Stereotype intentionally does not overwrite existing stereotypes. If there is an existing stereotype on the element, then assigning a value to Stereotype will set that new value as the primary stereotype and the old value becomes a secondary stereotype.

Assigning to Element.StereotypeEx will overwrite any existing stereotypes on the element.

It's been that way for a very long time. (EA 6.5?)

General Board / Re: Change language of all elements of a package
« on: March 30, 2017, 12:15:42 pm »
In EA 13 - Configure > Model > Options > Source Code Engineering : Default Language for Code Generation.

Hi Martin,

Unfortunately the help is referencing a version of MDG Link for DOORS that is still in development and not yet released, but there is an early (unsupported) pre-release version that we can provide to registered users. If you wish to get this download, please email support to request a link.

General Board / Re: New Cloud Services: Publishing Feature
« on: March 09, 2017, 03:09:25 pm »

In scripting just use stInternal, not EnumScenarioTestType.stInternal.  Enums such as this are defined in Local Scripts.EAConstants-JScript.

Code: [Select]
!INC Local Scripts.EAConstants-JScript
var test = stInternal;

Regarding your original problem, you need to pass the ElementGUID for the element that contains the scenarios, not the GUID of a specific scenario.  Using GUIDtoXML is also optional here - EA will recognize it either way.

Code: [Select]
Project.GenerateTestFromScenario(element.ElementGUID, stInternal);

You should be able to call ExpandEnvironmentStrings on the WScript.Shell object.

Code: [Select]
'Expand Environment variables such as %TEMP% and %APPDATA%
function ExpandEnvironmentStrings(s)

dim WshShell, retval
retval = ""

set WshShell = CreateObject("WScript.Shell")
if not WshShell is nothing then
retval = WshShell.ExpandEnvironmentStrings(s)
end if

ExpandEnvironmentStrings = retval
end function


General Board / Re: Addition/subtraction in DLL templates ?
« on: February 27, 2017, 12:44:05 pm »
Hi Qal,

There are actually function macros available in the code gen / transformation templates for MATH_ADD, MATH_SUB and MATH_MULT.  Unfortunately they don't seem to be documented though.  We will look into getting the help updated.

MATH_ADD(x, y)
Returns the value of x+y.

Returns the value of x*y.

MATH_SUB(x, y)
Returns the value of x-y.

Note: x and y for above parameters can be passed as either numerals or strings.  E.g. %MATH_ADD("10", "2")% returns 12.

Automation Interface, Add-Ins and Tools / Re: DOORS MDG
« on: February 15, 2017, 09:40:02 am »
Something I'm not getting trying to read the posts is whether the MDG link connects directly to the DOORS server, or through a local DOORS client. [...] Does using the MDG require a local DOORS client to work?

Yes, MDG Link for DOORS requires the DOORS Client.  Information is pulled via the API of the DOORS Client, it does not connect directly to the DOORS database.  To connect your DOORS module from EA, you need to have the DOORS client open and connected to your database, and have the specific module open that you want to connect with.

General Board / Re: Webinars
« on: February 01, 2017, 10:07:04 am »
There were also webinars in December and January.  You can find them here:

What are the strings you are returning for your menu items (particularly the root menu)?  Do any of them contain a hyphen at the beginning (indicating a submenu) followed by one or more spaces?

For example: We had a report from another user who was returning a string like "- My Menu" for their root menu.  For some reason the space following the hyphen was getting stripped by EA, which then failed on later comparison, resulting in no menu items getting displayed under EA 13.  Deleting the space after the hyphen resolved the problem.

If you are still having problems, please provide a copy of the code for your EA_GetMenuItems method so we can take a closer look.

Just to be clear though, the upcoming webinar is primarily focused on installation of Enterprise Architect itself under WINE.  I don't think it will be covering installation of keystore or cloud services (at least not as far as I know).

Root (Model) packages are a special case.  They do not have an associated Element class and will not have Tagged Values either.

Bugs and Issues / Re: All Add-ins is missing
« on: November 25, 2016, 09:46:42 am »
We have seen some strange problems like this when someone (or something?) has set a default value at the top of the HKEY_CURRENT_USER registry hive.

We have seen cases with other customers where something has set a value there it causes problems when EA tries to query the [HKEY_CURRENT_USER\Software\Sparx Systems\EAAddins] key.  For some reason when the key being requested does not exist, the Windows API returns whatever value was set at the top of HKEY_CURRENT_USER instead.

Try selecting the (Default) value directly under HKEY_CURRENT_USER, then Right-click | Delete it.  (not the HKEY_CURRENT_USER key itself, just it's default value).

The (Default) value should say (value not set) next to it.  If you see a different value, or a blank value, delete the (default).

Usual caveats apply here - be very careful when messing about in the registry or you may kill your Windows installation.

General Board / Re: Is there a VS integration with Cloud Services
« on: October 17, 2016, 12:23:42 pm »
In Enterprise Architect, connect to your cloud server and then save a Shortcut EAP file to this repository.

In Visual Studio, select Attach Existing Model and then browse to this shortcut EAP file.

General Board / Re: EA upgrade to 13 - system requirements
« on: October 14, 2016, 11:18:36 am »
Hi Carsten,

Yes, EA 13 is supported on WINE and actually contains many improvements in regards to Linux/Mac compatibility.  See:

The installation process should still be quite similar to EA 8, except that EA installers are now distributed as a .MSI file rather than a .EXE, so the install command is slightly different now.  The page you mention was recently revised to hopefully make the entire installation process more clear.

Pages: 1 [2] 3 4 ... 58