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

Pages: 1 ... 72 73 [74] 75 76 ... 78
Automation Interface, Add-Ins and Tools / Re: Printing/Exporting to PDF
« on: January 23, 2012, 03:06:09 pm »
I think the incantation is "upgrade to release 9.0, build 904", but you can add your favourite flourish of the wand if you like. That build is when that option was introduced. However, the option is not documented (yet) - next release, I hope.

It just copies the diagram as a single image into a PDF file in a location of your choosing. You might have to manipulate the image and/or print properties in the PDF file to get it to print out within the page margins.

In the EA Help, the documentation is under:

Modeling Basics > Elements > Element Tasks > Composite Elements

In the UML Superstructure Specification the icon is displayed in Figure 15.34. However, they are called 'Hidden decomposition indicator icons' in the figure title.

If you do not know that these elements are called Composite Elements, I'm not sure how you would chase them down on the EA Help. There are various icons representing spectacles for executing view or search functions; indexing the composite element icon under 'spectacle icon inside element' might not be specific enough, but I have just put it into the index anyway. Any other suggestions?

Automation Interface, Add-Ins and Tools / Re: Use of AddIn search
« on: September 13, 2011, 09:38:41 am »
Do you mean these two topics?


Automation Interface, Add-Ins and Tools / Re: Key store permissions
« on: April 05, 2011, 11:47:14 am »
And told to shut up.

But before you do shut up, you only have another 5300-odd postings to catch up with Midnight, who now appears to be back and upping the ante (welcome back David!). So come on lad, hop to it!

Automation Interface, Add-Ins and Tools / Re: information flow in EA
« on: March 29, 2011, 09:40:00 am »
Kris (and anyone else interested)

Please submit this as a Feature Request (or, if you prefer, a bug report) directly to Sparx Support using the links in the Support column at the foot of this page.


Automation Interface, Add-Ins and Tools / Re: Stupid RTF Question
« on: December 08, 2010, 04:57:18 pm »
Yes, weird. I have given the Element.Notes field a good workout, adding it, deleting it, shifting it around, saving the template and all that. Whenever I wanted to delete it, it went without a problem.

If you have this problem again, please send a bug report in to sparx support with a copy of the template.  Thanks.

Automation Interface, Add-Ins and Tools / Re: Stupid RTF Question
« on: December 08, 2010, 02:29:27 pm »
Well, the sections are protected, so you can't delete them (or either of the start or end portions thereof). You just turn them off in the Sections panel (deselect the check box). I suspect that the start of your section is a long way in advance of the end, so it just looks as if the end is an orphan.

As for fields, I can delete text with no background, and I can delete text with a grey background as long as I delete the whole string between (and including) the brackets. I don't have 'bits' left floating around.

Perhaps you could tell us exactly which section and which field value you are having problems with.

Automation Interface, Add-Ins and Tools / Re: Stupid RTF Question
« on: December 08, 2010, 10:02:54 am »
Not sure what you mean by an orphaned tag. Is it a section tag, listed in the Sections panel on the left? Can you deselect the check box for that tag in the Sections panel? If it is a field tag, perhaps there is more to it than you have highlighted; you need to get the whole thing, including the brackets.

I seem to be able to clean up the experimental work in my sandbox template, but as I said, I'm not sure what actual item you are trying to remove.

In the Help, this is called the Legacy RTF Generator. The 'new' generator has been around for a long time, but we have found that there are still some people who are using the Legacy Generator. We don't maintain the Legacy Generator, but we have not excommunicated it either. Yet.

Automation Interface, Add-Ins and Tools / Re: MDG Link vs. MDG Integration
« on: November 09, 2010, 09:12:03 am »
Both products are compatible with VS 2005 and VS 2008.

For any more-detailed discussion of the products, I suggest you contact Sparx Support or Sparx Marketing ( and This is a user forum, and the participation of Sparx employees in forum discussions is casual. We cannot guarantee to give full responses, or indeed any response at all, on the forum. The official channels do respond as completely and as quickly as they are able.

Automation Interface, Add-Ins and Tools / Re: MDG Link vs. MDG Integration
« on: November 08, 2010, 11:21:46 am »
Not a point-by-point comparison, no. However, you can read the following product descriptions to see the differences.

What release of Enterprise Architect are you using?

This is the latest Help for Release 8.0, build 864. There are one or two small improvements.

Automation Interface, Add-Ins and Tools / Re: Where is "Alias"
« on: November 08, 2010, 11:08:40 am »
The point is actually mentioned in the Enterprise Architect User Guide, but it is now a lot clearer and is indexed. The change will be seen in the documentation for the next release of Enterprise Architect.

A couple of points.

A Document Artifact is nothing to do with Virtual Documents. In the Toolbox, it coincidentally shares a page with the Model Document and Master Document elements, but they have different purposes.

The Document Artifact is a mechanism for adding a relatively large quantity of formatted descriptive text to a specific element, in the form of a linked document. In the past it was the only means of adding a linked document, and for the Desktop and Professional editions of Enterprise Architect it still is the only means of adding a linked document to an element. For the Corporate and 'suite' editions you can add a linked document to an element directly, and that is a better mechanism.

A linked document is a container for a relatively large quantity of formatted descriptive text about a specific element. If you have a linked document on a Package, it is to document the Package element rather than to document the content of the Package. It is not intended to create either skeleton or boilerplate text for a report - you put that text in the RTF template you are using, whether it be used in a Master Document element or a Model Document element, or in a 'normal' RTF report.

I'm not sure what you want to acheive with the "manual content", but if nobody else chips in with some help on the forum, please send a support request to Sparx Support and they can work through the process and help you develop a solution.

Pages: 1 ... 72 73 [74] 75 76 ... 78