Messages

1

Bugs and Issues / Re: Activity Diagram: Unable to link decision with

« on: March 23, 2011, 12:19:23 am »

Hi Eddie,

well I can't confirm this, at least in build 8.0.864 it works as expected:

Open the activity diagram.
Locate the requirement in the browser.
Drag'n'drop the req onto the decision element on the diagram.

Verify the link in the relationships window or by viewing the properties.


Uncle G.

2

Bugs and Issues / Re: Is that is a bug?

« on: August 11, 2010, 07:08:00 pm »

Well, this is no bug, it is EAUI.
What happens is that EA "recognizes" the types of the return and parameter values whilst scrolling through the methods and then internally "updates" the previously unknown data types to already present data types stored in the repository.
So such methods get the dirty flag and may require saving.

Uncle G.

3

Bugs and Issues / Re: RTF Documentation Issues

« on: June 24, 2010, 09:27:52 pm »

Hi Bruce,

I recommend using a Word Master Document for implementing corporate design issues like header/footer/images and so on.
Also the levels and numbering of the headings can be configured with a Word Document Template being applied to the Word Master Document.

When generating RTF templates in EA you should just concentrate on filling them with the data and diagrams of your model elements.

You then include the generated rtf as client (? don't know how they are called in english) documents into the word master.

So you just have to make changes in on spot and not in every EA template.

Uncle G.

4

Bugs and Issues / Re: C++ generate source parameter as reference

« on: May 28, 2010, 10:16:49 pm »

We are facing the same problem for some years now.
I have tried modifying the code generation templates, but even if code generation works properly then, the next bigger problem which arises then is reverse engineering.
Solution 1: modify template to generate the * or & character if [inout/out] is specified.
Solution 2: specify method/parameter signature something like
func(MyClass &param1)
...
Code generation is no problem then, but pressing F7 will screw up your definition and you end up in func(MyClass& param1), so the classifier info gets lost.
Even worse, pressing F11 after the first generation you will be asked to reassign/delete etc the already existing method. Very annoying.
This seems to be due to a mismatch between code generation and reverse engineering.

What you can do is to omit the reference whilst in the design phase of your project. Then renaming of a class used as parameter or return value (here the same problem occurs) is no problem, EA traces it an renames the referencing places accordingly.
Then, right before code generation you apply the */& characters to your parameter and or return value classifiers.
Of course, just a workaround, but in the coding phase you rarely change class names, if ever.

Uncle G.

5

Bugs and Issues / Re: EA V8.0 - Doc Generation

« on: April 29, 2010, 02:56:22 pm »

Actually I have sent two bug reports.
Both were confirmed as follows:

I have verified that the full data is not rendered for Virtual Document generation.
This has been lodged for correction as issue: 100454

... and ...

I have run this through builds 850 & 855, and yes this does drop the top
table row in build 855.
I have lodged this as issue: 10045479

Well, build 855 is nice to work with. But, for document generation, we are still using build 850, which was the best release so far.

6

Bugs and Issues / Re: EA V8.0 - Doc Generation

« on: April 20, 2010, 05:03:40 pm »

We are facing the same problems.
If lazy loading is turned off the situation improves a little bit.
But ... in our docs for example only the name of the FIRST element gets rendered, other fields (status etc) work as expected. Weird.
I already have sent a bug report.