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

Pages: [1]
1
General Board / Re: Moving Node Elements
« on: September 17, 2007, 11:35:59 pm »
I have reported this as a bug to Sparx.

2
General Board / Re: Moving Node Elements
« on: September 16, 2007, 12:11:42 pm »
This happens on new projects as well.  I have tried this on my PC as well as on a colleague's PC.  In both cases, I started with completely new projects and didn't copy any diagrams or packages.    

3
General Board / Re: Moving Node Elements
« on: September 13, 2007, 03:49:00 pm »
I did a project integrity check, and it did indicate that there were 'invalid diagram parents'.  However, the recover/clean option doesn't solve the problem and the integrity issues keep on coming back when I move diagrams and/or nodes.  

It happens on new projects as well, so it appears to be EA that corrupts the project.

I think it has something to do with the fact that I made the nodes composite elements and dropped the parent node element (incl. related nodes) onto the child diagram.

4
General Board / Moving Node Elements
« on: September 13, 2007, 12:39:01 pm »
I am experiencing a problem where EA automatically moves the node elements from the package where I put them into another package that contains a diagram including these nodes. This appears to happen after I close and re-open the project file.  I'd like the node element to remain in its original package.

Does anyone know how to resolve this?


5
 :) Received some helpful information from the EA support team (thanks Dermot!), as follows:

In the Diagram Properties | Document options tick the option:
 

  • Document each contained element in RTF:

    This sets the RTF generators to include details of elements that are defined  external to the package for this diagram.  This varies between the two RTF generators:

    -      In the old RTF report generator this sets the document to contain the external element details.
     
    -      In the New RTF generator this sets the generator to process this element but it requires that the Diagram::Elements section has been set.

    To create a section to generate the external element details; In the RTF editor  select from the sections area: Package | Diagrams | Element (The standard element details are in Package | Element).

    This will create the following text in the Content section.

    element >
    ...insert Element content here...
    < element

    You can then set this to blank (delete: ...insert Element content here...)to reproduce the layout used in the Package::Element section, or define the layout differently for external elements by adding a detail between Element> and <Element.

    There is a full section covering this in the RTF report generator whitepaper - see:
    http://www.sparxsystems.com.au/resources/whitepapers/



6
I am currently trying to create a RTF template to be used to generate documentation for use case realisations.  Each use case realisation contains one or more sequence diagrams (flow of events) and a view of participating classes (VOPC).  The VOPC is basically a class diagram containing references to classes that are part of one of more packages located outside the use case realisation package.  These 'external' packages contain more classes than are relevant to the use case realisation and I want to include only the relevant classes in the document.

The RTF template generator doesn't appear to allow me to include documentation of these 'external' classes in the document.  I know I could create a 'Virtual Document' to achieve this, but that would include documention of all classes, even the classes that are not relevant to the use case realisation.

The legacy RTF dialog has an "Document Linked Elements" option, which is a handy feature when the classes in a class diagram are located in another package.  It basically does exactly what I want to achieve with RTF templates.  Does anyone know how I can achieve this with RTF templates?


7
I have a sequence diagram containing messages with sequence numbers.  I'd like to include these numbers in the RTF documentation that I am generating.  I have tried the {DiagramMsgs.Sequence} tag to achieve this, but it doesn't seem to work.

Does anyone know how to do this?

Pages: [1]