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 - Guillaume

Pages: [1] 2 3 ... 36

Making progress, I managed getting the addin to be installed on a local folder (appdata, local) and some of the registry values set.
Testing it on a blank PC, I found out that the DLL is not registered i.e. the result from the regasm /codebase is missing.

I wrongly thought that I had fixed it on my main PC since the addin DLL is registered by compiling new versions.

I started looking at running WiX Heat tool on tlb files (see hints on

Bugs and Issues / Re: To rectangle or not to rectangle?
« on: November 21, 2017, 02:41:14 am »

I was looking for thread matching a bug I'm experiencing with SysML and it could match this one.
The issue is quite easy to reproduce :
- create a SysML requirement diagram
- create a few requirements
- create a new diagram (sysml ou uml) + drag drop the existing requirements.
Result: the reqs are displayed with a rectangle notation. I even get an odd side behaviour with a Requirement label appearing underneath...

Experienced with build 1351.

Hi Uffe,

Thanks for your reply. Please note that I have a working Wix installer and I'm looking at a way to publish a portable version as a number of EA users don't have admin rights on their PC (e.g. especially in large/industrial companies).



I started working on a wix setup project version to release a portable edition of my addin.
I read Adrian's link ( however I'm still getting errors (current is ICE57).

I'd like to install the DDL in a user folder such as AppData, and update the registry in the HKCU.

Below is an extract from my wxs files.

Code: [Select]
    <Directory Id="TARGETDIR" Name="SourceDir">
      <Directory Id="LocalAppFolder" Name="AppData">
        <Directory Id="eaUtilsFolder" Name="eaUtils" />
  <DirectoryRef Id="eaUtilsFolder">
      <Component Id="eaUtilsFiles" Guid="xxxxxxxx">
        <RemoveFolder Id="RemoveeaUtilsFolder" Directory="eaUtilsFolder" On="uninstall" />
      + other published files...       
        <RegistryKey Root="HKCU" Key="Software\eaUtils\eautils" ForceCreateOnInstall="yes" ForceDeleteOnUninstall="yes">
          <RegistryValue Type="string" Value="eautils.Main" />

Any comment or suggestion is welcomed!


General Board / Re: menu maps for 13.5 ribbon detail
« on: October 26, 2017, 05:30:40 pm »

I agree that it would be useful to know the ribbon/command location when you use the Find Command (feature request).
You may find the following menu mapping details from EA12.1 to 13 useful:



I like EA 13.5 new "navigation cells" to open a diagram as an alternative to hyperlinks.
Copying the diagram to the clipboard to use e.g. in Powerpoint has a glitch since the embedded images are rendered with a black background.

Automation Interface, Add-Ins and Tools / Re: Scripts submenus
« on: October 11, 2017, 05:30:45 am »
Hi Uffe,

Thank you for the tip. However the reason why we use scripts on this project is to overcome addins installation issues on each user's PC. Scripts are easy to maintain and update via the centralised project.
Hopefully this feature request can be taken into account at some point (for xmas...)

Automation Interface, Add-Ins and Tools / Re: Scripts submenus
« on: October 10, 2017, 05:41:08 pm »
Hi Aaron,

I submitted it as a feature request. Do you see this as a possible/feasible feature to have in EA?


Automation Interface, Add-Ins and Tools / Scripts submenus
« on: October 10, 2017, 12:54:54 am »

We use a number of package and diagram scripts for a project which we prefixed by type.
A right click on a package or diagram displays a big list which I'd like to reduce with an additional level

Is this supported in EA?

Current list:

Needed list:
Type 1
Type 2

Select Type 1:

Great, thanks for the info.

General Board / Settings location for the enabled MDGs and custom toolbar
« on: September 14, 2017, 12:29:31 am »

I'm trying to identify when EA stores local custom data so a team can deploy a fully custom EA configuration throughout the team.
Perspectives and EA 13 ribbons are located in Sparx appdata folder.

I know some details are also located in the registry, however I'm trying to find the following:
- list of enabled/disabled MDG Technologies updated via CONFIGURE > Technology > Manage
- custom toolbars with added commands via START > Workspace > Preferences > Customize > Commands.


General Board / Re: Adding a set of attributes to a large number of elements
« on: September 06, 2017, 06:18:59 pm »
Here is a suggested script to create the same attributes on the classes within the selected package. It can be improved to loop through the subpackages, only update classes with a given criteria such as a tagged value, etc.

Code: [Select]
option explicit
!INC Local Scripts.EAConstants-VBScript   
' Script Name: Populate attributes (package script)
' Author: Guillaume[at]
' Purpose: Create the same set of attributes on each class within the selected package
' Date: 6/09/2017

sub OnProjectBrowserScript()
' Get the type of element selected in the Project Browser
dim treeSelectedType
treeSelectedType = Repository.GetTreeSelectedItemType()
select case treeSelectedType'
case otPackage
dim thePackage as EA.Package
set thePackage = Repository.GetTreeSelectedObject()
dim allObjects as EA.Collection
dim currentElement
set allObjects = thePackage.Elements
dim i
for i = 0 to allObjects.Count - 1
set currentElement = allObjects.GetAt( i )
if currentElement.Type = "Class" then
addAttribute currentElement, "attr1"
addAttribute currentElement, "attr2"
addAttribute currentElement, "attr3"
end if
case else
' Error message
Session.Prompt "This script does not support items of this type.", promptOK
end select
end sub

sub addAttribute(ClassToProcess, attributeName)
dim attributes as EA.Collection
set attributes = ClassToProcess.Attributes
dim newAttribute as EA.Attribute
set newAttribute = attributes.AddNew( attributeName, "" )
end sub


Hope it helps.

Automation Interface, Add-Ins and Tools / Re: Shape script: rotated text
« on: August 17, 2017, 03:46:00 pm »
I think it should be available to all elements without having to go through ShapeScripts.
I recently raised this request here:,38548.0.html.

I don't know the impact on EA but it seems unlikely as it would appear to have been asked numerous times.

Bugs and Issues / Re: SysML prevents using UML use cases
« on: August 10, 2017, 11:15:58 pm »
Thanks for your reply Geert

However it was a different issue which I since managed to sort out: the SysML 1.3 MDG was set as active. This led to replace my UML statechart toolbox for instance with the SysML toolbox.
It can be changed via Extensions > MDG Technologies > select Basic UML and set as active.

Bugs and Issues / SysML prevents using UML use cases
« on: August 10, 2017, 09:08:59 pm »

I use both SysML and UML on various EA projects.
Somehow I must have enabled an option in EA that I need to get rid of:
- in the toolbox view, the SysML Common is always visible (the common is collapsed)
- in a UML use case diagram, I always get the SysML Use Case toolbox!


Pages: [1] 2 3 ... 36