Messages

1

Bugs and Issues / Re: Out of memory error when debuging Addin (VS 2013)

« on: March 29, 2016, 08:15:38 pm »

Hi together,

I have the same problem since using VS2013, with VS2010 it worked perfectly.
Directly after starting the debug session ea creates the this message "Out of memory" 3 times. After the third time, the message "Failed to create empty document" appears. After clicking "OK", EA quits.

The only alternative is to start EA separately and attach to the process with VS2013.

Any hints on this issue?

EA version 12.1.1229
Win7 64 bit
VS2013 Prof

Jonathan

2

Suggestions and Requests / Re: Difference "Add Element" via Diagram & via Bro

« on: July 02, 2013, 01:48:40 am »

Code: [Select]

select * from t_package p
join usys_system u on u.Value = p.Package_ID
where property = 'TemplatePkg'
Regards

Geert

Thanks Geert! That's what i was looking for.

3

Suggestions and Requests / Re: Difference "Add Element" via Diagram & via Bro

« on: June 26, 2013, 10:18:48 pm »

Okay, so there seems to be no liable reason for this behaviour.

I'll try to do a work-around listening to the EA_OnPostNewElement-event in the automation interface.

Can anybode tell me, where to find the link for the Project Template Package in the .eap-Database? (table name, field name...?)

Thanks!
Jonathan

4

Suggestions and Requests / Difference "Add Element" via Diagram & via Browser

« on: June 18, 2013, 05:11:57 pm »

Hi there,

is there a reason why the two "add"-commands

- drag element from toolbox to a diagram
- add element via symbol/context menu in project browser

do behave different.

Why does the dragging onto a diagram evaluates the project template package and the project browser command does not?

Can anybody explain, otherwise for me this would bring up a change request.

Thanks!
Jonathan

5

General Board / Re: Project Template Package: Connector Line Style

« on: August 27, 2012, 08:11:14 pm »

You could always send in a feature request

Hi Geert,

I just did that. Hopefully it will be available in one of the next builds.

Jonathan

6

General Board / Re: Project Template Package: Connector Line Style

« on: August 24, 2012, 06:04:39 pm »

The default line style is defined in the options.
There's a separate option to use tree style for generalization/realization

Geert,

thanks for the answer, but that is not what I am looking for. When I open the context menu of a connector I can select some more line styles (Tree Style, Lateral, Orthogonal) than the ones selectable in the Tools/Options/Links default line style menu (Direct, Auto Routing, Custom).

Unfortunately it's not a generalization diagram where I want the connectors to have the default style "orthogonal"...

Any other ideas?

Jonathan

7

General Board / Project Template Package: Connector Line Style?

« on: August 23, 2012, 06:59:00 pm »

Hi folks,

is it possible to define the default line style (lateral, orthogonal,... ) of a connector with the project template package?

I tried this currently, but it doesn't work. All the other elements like states or activities behave in the correct way and are created from the templates defined in the project template package?

Thanks!

Jonathan

8

Bugs and Issues / Re: EA 11: EA_OnPreNewElement ParentID always 0

« on: February 02, 2015, 07:05:41 pm »

Hi McMannus,

I also encountered this in EA 11. I must admit, that I never tried this one in older version but for me it would also be helpful If the ID of the parent object is filled correctly.

Did you send a bug report to SPARX?

Jonathan

9

Bugs and Issues / Re: RTF-Report - header/footer on cover page

« on: January 24, 2015, 02:43:59 am »

Thanks Simon,

your post gave me a hint to try if the master document will be correctly generated when setting the master document template to <nothing> and inserting the headers and footers to the model document themselves.

For me this is sufficient.

Jonathan

10

Bugs and Issues / RTF-Report - header/footer on cover page

« on: January 20, 2015, 08:40:13 pm »

Hi,

Is there a change on the usage of headers/footers when NOT using the cover page functionality in EA11?

Until EA10 I added one model document to my master document representing the cover page of my document.
The model document pointed to a template which contains the body of the cover page.

All my headers and footers where set in the master document template where I defined different headers/footers for the first page and different ones for the other pages

Since EA11, the footers and the headers of the other pages are also used for the first page even if they are set differently in the master document template.

Remember: I do not use the new features "Cover page" or "Stylesheets" at the moment.

Is this a bug or a feature?

Thanks!

Jonathan

11

Automation Interface, Add-Ins and Tools / Re: Bookmarks for Elements in Custom Script Templa

« on: November 04, 2015, 12:27:56 am »

You need to set t_object.tagged to 1. (Reminds me to update the section of my Inside book.)

q.

Thanks for that qwerty. For creating hyperlinks I just realised, that the construct for SQL also works in script template fragments (XML tag e.g. "Name-Hyperlink" and custom field "Name.Hyperlink" with value "{GUID}Name")

I try to realize a reference directory for a document. All references are available as "Artifact"-Elements. The script in the template fragment collects all hyperlinks in any package or element note and prints the found artifact-elements to the return string (-> result: a list of elements). The entries of this list shall be the jump targets of the hyperlinks throughout the document.

If printing Elements with normal document templates within the Content range "Element", the bookmarks will automatically be generated and the jump targets for the hyperlink are valid.

Now I need a construct for a script template fragment to realise hyperlink jump targets to elements gathered by the script in the template fragment.

I tried

Code: [Select]

var xmlName = xmlDOM.createElement( "Name" );
xmlName.text = oArtifact.Name;
xmlName.setAttribute("tagged", "1");
xmlRow.appendChild(xmlName);

or adding the EABOOKMARK element (see http://www.sparxsystems.com/enterprise_architect_user_guide/12.1/report_generation/custom_query_fragments.html)

Code: [Select]

var xmlName = xmlDOM.createElement( "EABOOKMARK" );
xmlRow.appendChild(xmlName);

but all these solutions don't work  

Thanks!

Jonathan

12

Automation Interface, Add-Ins and Tools / Bookmarks for Elements in Custom Script Templates

« on: November 03, 2015, 09:17:00 pm »

Hi together,

is there a way to create bookmarks for elements printed with the script template fragment similar to the solution usable in SQL template fragments?

See help for EA 12.1:

You can also make your column entries into hyperlinks to the element entries in the generated document. The column header field (in the template text itself, in the 'Custom' panel) must contain the suffix '- Hyperlink'; for example:

     Elements-Hyperlink      (Elements.Hyperlink is also valid for non-Jet repositories)

The column entries, or values, must have the format:

     {guid}LABEL

In this format, {guid} is the GUID of the element to link to and LABEL is the hyperlink text (such as the element name), either manually inserted or returned from another command. For example:

     {123-456-7890}Class2

In the generated report this displays as Class2, which links to the description of Class2 in the document.

Taken from
http://www.sparxsystems.com/enterprise_architect_user_guide/12.1/report_generation/custom_sql_fragments.html

Thanks!

Jonathan

13

Automation Interface, Add-Ins and Tools / Re: Add-In Search running in EA but not in RTF Rep

« on: February 12, 2015, 02:55:31 am »

Hi TroyMcClure,

You are correct I was referring to the DocumentPackage method. I'd agree that it might only return the top level package info. But I have a package with three diagrams in it. The report only ends up with the first one.

I just tried generating a document with the DocumentPackage-method on my own machine with the "Model Report" system template. I got a report with the package details and ALL diagrams with are children of this package. I cannot say, why this is not working on your machine.

When I run a ModelDocument that has a package using the EA Doc Generation I get what I expect. Then I run the add-in with DocumentPackage method. Then I go back and rerun the same ModelDocument and get the same reduced results as the add-in. I have to restart EA.

That behaviour I cannot reproduce on my machine. Sorry. I would ask Sparx, if this is a known bug.

I must not be using the ModelSearch(SearchName and SearchTerm) correctly. It returns all of the elements in a package and not reducing to SQL results. Update: I figured this out I can't have a package and modelsearch as they will conflict.

Yes, you are right, this is not possible. You can either use a model search OR a package as source for the data. But you can exclude packages by using the SQL exclude feature of the model template or you can use the SQL template fragments to use SQL selections.

Regards,
Jonathan

14

Automation Interface, Add-Ins and Tools / Re: Add-In Search running in EA but not in RTF Rep

« on: February 11, 2015, 11:57:26 pm »

Hi TroyMcClure,

I have some questions to understand your questions correctly:

Thanks for tips. I've written an add-in and ran into a problem with DocumentPackage in the generator. It runs on the package and returns successful, but the document only contains the package title and first diagram and excludes the rest of the package.

So you are using the "DocumentGenerator" of the EA API and thereof the "DocumentPackage" method?

This method is able to document all package data, but not the data of elements or child packages and so on...
If you want to print the contents for e.g. the sub-elements of the package, you will have to iterate the elements by using the Package.Elements-collection and calling "DocumentElement" on these elements. There are different methods for each type of item (DocumentElement, DocumentPackage, DocumentDiagram...).
With the document generator class you have the ability to fully customise the structure of your generated document by using the API calls.

I am using the "Model Report" Template so it should return almost everything. When I run a ModelDocument it returns what I expect.

The internal document generator combines these calls to the "Document..."-methods according to the template given in the model document tagged values.

But if I run the same ModelDocument in EA after the add-in I get the same results as the add-in. Seems there is another bug?

What do you mean with "...after the add-in"? Do you first run the report with your add-in and then with the internal document generator?
You should get equal reports if you run the ModelDocument with the internal document generator as well as with the API-call "Repository.GetProjectInterface().RunReport()".

Our master document contains some Model Documents that have ModelSearches. I was trying to generate one document that has model documents of normal templates and model searches. Is this possible?

My master document also contains some ModelDocuments with model searches. This is working fine as long as you are not using an "add-in search" (certain type of the model search). This is not possible as you can see from recent posts here in this thread.
What do you mean with "normal templates"? Are you talking about using packages as source for the data instead of model search?

I hope this information helps.

Jonathan

15

Automation Interface, Add-Ins and Tools / Re: Add-In Search running in EA but not in RTF Rep

« on: February 02, 2015, 06:50:33 pm »

querty, MrSnrub,

I have tried it in the recent version EA 11.1112 and it doesn't work either. Over the past 2 years I developed a C#-add-in which partly replaces the EA-integrated document generator.

Main features of my add-in:
- The add-in main function is called with an parameter "GUID of master document package"
- Parsing of all model documents
- Calling the document generator with the API call "Repository.GetProjectInterface().RunReport()" for the normal templates (with packages as attributes)
- Calling the document generator with the API call "RepositoryCreateDocumentGenerator()" as well as the relevant item functions "DocumentGenerator().Document<...>().
- The source for the "Document<...>()" method I get from my add-in search which I identify by the "Search" and "Search-Term" tagged-values in the model document.

That's my way of getting the add-in search to work. But this may not work for everyone  

It's sad, that Sparx has no roadmap for this - IMHO - BUG!


If there is need for more explanation on my solution, I can post more on request.

Jonathan