Messages

1

General Board / Re: Replace an element in a diagram with another element

« on: February 04, 2025, 11:55:31 pm »

Found a semi-easy way

1) Open the imported diagram in the target project
2) Dump the elements to be used as replacement on the diagram
3) Switch to 'Relation Matrix View'
For each connector connecting imported elements:
4) right-click->advanced->Set Source and Target..
5) Set source and target of the connector to the same elements in the target project.

2

General Board / Replace an element in a diagram with another element

« on: February 04, 2025, 11:27:33 pm »

Is there a way to replace an element in a diagram with another element of the same type - including all connectors?

I've created a rather complicated sequence diagram I would like to use in another project - so I would like to do something similar to:
1) export part of the model with the diagram to reuse to XMI
2) import the XMI in the other project (target project)
3) Replace imported elements in the imported diagrams with elements from the target project.
4) Delete the imported elements no longer used.

3

Bugs and Issues / Not able to set stereotype 'struct' on C++ class

« on: December 03, 2024, 06:48:53 pm »

I have a class with the language setting 'C++'. I'm not able to set the stereotype 'struct'. I can see it the C++ profile, but when I select it it's not applied. Any ideas?

4

Automation Interface, Add-Ins and Tools / C++ Code generation and folders

« on: October 11, 2024, 05:55:21 pm »

The default C++ code generator in EA places header and body files in the same location.
Is there a way to configure EA to separate the two while maintaining the tree structure in the model - i.e.

In the EA model:

<Namespace root package>
  |___Class1
  |
  |_Child_Package
             |
             |__Class2

The wanted structure of the generated code with destination folder <Source Root>->Inc:

<Source Root>
  |__Inc
  |      |_Package     
  |           |_Class1.hpp
  |           |_Child_Package
  |                     |__Class2.hpp
  |__Src     
          |_Class1.cpp
          |_Child_Package
                    |__Class2.cpp

If I set the 'Source Path' property for C++ to '../Src' under preferences the tree structure works for the header files (hpp) but the body files are generated under 'Inc->Src' and the tree structure is removed - i.e. the structure of the generated code becomes (the location of 'Class2.cpp' is wrong):

<Source Root>
  |__Inc
  |      |_Class1.hpp
  |      |_Child_Package
  |      |           |__Class2.hpp
  |      |_Src
  |           |_Class2.ccpp         
  |__Src       
         |_Class1.cpp
 

Any suggestions?

5

Automation Interface, Add-Ins and Tools / Re: PDF reports have too wide right and bottom margins

« on: October 04, 2024, 09:53:58 pm »

The same problem occurs when printing a diagram using 'Print to PDF...' in the ea-menu (Upper left drop down).

6

Automation Interface, Add-Ins and Tools / PDF reports have too wide right and bottom margins

« on: October 04, 2024, 09:14:23 pm »

When I generate a PDF report in A4 format an extra wide right margin is shown.  The bottom margin is also too wide.

The page size in Adobe Reader is reported as A4 and everything looks fine in Word. Any ideas?

7

Automation Interface, Add-Ins and Tools / Import of word document changes field categories

« on: September 17, 2024, 09:37:37 pm »

We would like to use a Word document as an EA template. It has a field 'HS_Item' in the category 'DocProperty', which is used by an external system (we would like to export from EA and have this other system detect the HS_Item field).

After import in EA the field appears in the category 'MergeField'. Is there a way to avoid this?
Thanks.

8

Automation Interface, Add-Ins and Tools / Re: Is there a way to neutralize unused profiles/technologies

« on: August 16, 2024, 10:41:12 pm »

Thanks for the response. Disabling the technologies under 'Settings'->'Options'->'MDG Technologies' fixes the issue.

9

Automation Interface, Add-Ins and Tools / Is there a way to neutralize unused profiles/technologies

« on: August 16, 2024, 10:16:45 pm »

I've created a profile with a stake holder requirement stereotype. For some reason this is confused with the BABOK::stakeholder requirement. Is there a way to avoid this?

10

Bugs and Issues / Re: C++ body contains "empty string" include

« on: August 15, 2024, 04:37:14 pm »

Update - the class, which correctly includes the header contains a custom tag with the includes. This tag is used in the code generation.

This solves my problem.

11

Bugs and Issues / C++ body contains "empty string" include

« on: August 15, 2024, 04:30:03 pm »

Hi all,

I have to seemingly identical classes. When I generate C++ code I see the following in the body file in one of the body files (cpp):

#include ""

The other correctly contains:

#include "./ConfigureSledResponse.hpp"

Any ideas?

12

Automation Interface, Add-Ins and Tools / Re: Stereotyped relationships between stereotypes in different profiles

« on: May 07, 2024, 07:52:09 pm »

Works like a charm.

Dropped a metaclass element and selected the stereotype from the other profile.

13

Automation Interface, Add-Ins and Tools / Stereotyped relationships between stereotypes in different profiles

« on: May 07, 2024, 07:15:14 pm »

I have a two profiles where I would like to enforce valid relationships between a stereotype in the first and one if the second. Is this possible with stereotyped relationships?

14

Automation Interface, Add-Ins and Tools / Re: Section break - problem removing

« on: May 02, 2024, 05:07:12 pm »

The 'Export->Fix in Word->Import' did the trick:

1) Export to Word using 'Edit->File->Save As (Export to File)'
2) Fix the break in Word.
3) Clear the template in EA using 'Edit->File->New (Clear Document)'
4) Import to EA using 'Edit->File->Import File'

15

Automation Interface, Add-Ins and Tools / Section break - problem removing

« on: May 01, 2024, 11:21:41 pm »

I have a section break in a report template, which can't be removed.

I can insert and remove new section breaks but for some reason this one is can't be touched. Any suggestions?