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 ... 70 71 [72] 73 74 ... 78
If you are reviewing the version 11 beta release, the new process for dealing with Learning Center pages is not currently documented, but it will be soon.

Automation Interface, Add-Ins and Tools / Re: Tagged values names
« on: February 07, 2014, 09:31:09 am »
What you see at the top of that window is the element type or connector type. It isn't a Tagged Value, it's the reference to the element or connector in which the Tagged Values are set.

You can see a list of standard element and connector types here:

As the topic suggests, you can extend these standard types with stereotypes, so if you look at the Tagged Values window for an extended element or connector, you will see the stereotype name for that element or connector type.

On the other hand: if I write a shape script and place the DrawCompositeDiagram wouldn't I expect to appear that diagram rather to have the user to set the option manually??? That's probably some EAUI as my way of thinking differs from that of the EA developers.

No, because this piece of script is for responding to the user's requirement to show a composite diagram WITHIN A COMPARTMENT OF THE PARENT ELEMENT. The user still has to indicate whether to display the composite diagram separately or within the parent element.

On the Class, you also need to select the context menu option New Child Diagram > Show Composite Diagram in Compartment.

The point is, some Shape Scripts change element display, and if you have a Composite Diagram shown in the compartment the Shape Script would change things so that the diagram would not display. THIS bit of Shape Script honours the Show Composite Diagram In Compartment setting so that the diagram does display. I hate to point it out, but that is explained in the Show Composite Diagram topic in the Help.

I am by no means an expert in Shape Scripts. I sit in my sandpit, plastic spade in one hand and keyboard in the other, and play with the scripts to produce the actual screenshots you see in the Help.  If I can make those work, believe me, there are no hidden pre-requisites or complications! Other than, perhaps, a whack with a plastic spade?

If you are specifying a Requirement, use the Traceability window (View | Traceability, or press Ctrl+Shift+F4).

Another problem here is that you are working on the very latest build of Release 10 (1008) but referring to a document that was written for a much, much earlier release of EA (

Please do as rothnic did: "... instead used the guide in the help file of EA to get through it.". The Help in the installer of your build of EA always supports that build.

What have you attached the linked document to? A Document Artifact element or a Package element? In either case, that element is unlikely to be one of your stereotype B elements, so it won't be included in the report. (A linked document is bound to an element.)

Just to answer qwerty's point - quote from the Scripting topic in the Help:

"This facility is available in the Corporate, Business and Software Engineering, Systems Engineering and Ultimate editions."

Can you run the script from the context menu? (Right click on a script name and select the Run Script menu option.)

You will probably get some help through this User Forum, but you could also try contacting Sparx Systems India, via:

Automation Interface, Add-Ins and Tools / Re: Virtual Diagram
« on: July 19, 2013, 11:34:28 am »

Do you have any administration, Project Management or set-up packages in your project? For example, the element Templates package? You could put such things in a Simple View and also create your Related Elements diagrams in there, if you don't want them in your modeling areas.

Not specifically, as far as I know.

Is there anything in these two Help topics that you can use?

Model Transformation > Write Transformations > Intermediary Language

Model Transformation > Write Transformations > Intermediary Language Debugging

True, by bad

These computer people who work too intently on their programs - they are always getting a code in the nose...

I have also just been copying PACKAGES between models quite easily. You cannot copy diagrams by themselves - perhaps that is where the problem lies. If the source package has too many 'other' things in it, copy the required diagram and its elements to a new package so that they are on their own, and copy that new package entirely from one instance of EA into the other instance of EA. Does it work now?

What release of EA are you using? In the latest build of EA 10 (1007) there are two Help topics for extending non-UML objects - search for Create Stereotypes Extending non-UML Objects and Add Stereotypes and Metaclasses using Profile Helpers.


Pages: 1 ... 70 71 [72] 73 74 ... 78