Forum Replies Created
-
AuthorPosts
-
eadocX SupportParticipant
This is a really tricky one, since Sparx don’t make available any APIs for manipulating images: we just get to copy it to the clipboard, then paste into the document.
So, the solution is, sadly, partioning the diagrams in smaller bits… 🙁eadocX SupportParticipantShort answer is no.
What you can do is to:
– print each of the Activities in a table
– print each of the decisions in a separate table
– in both tables, print an extra column, with a hyperlink to the next Activity/Action/Decision.
This will then allow readers to click through the flow of your use case.
I thin the relationship type is ‘ControlFlow’, and choose ‘ANY’ as the target element type.eadocX SupportParticipantSorry -no.
The ‘don’t print notes’ indication would have to be in EA itself – like the ‘don’t print this diagramat all’ indication, where we use the “exclude image from RTF document” flag, but there aren’t any obvious ones left for us to use!eadocX SupportParticipantSadly not….
..but it’s on our list of things to look at again.
Doing this means we have to dive deep into MS Word, and make sure we only make a small part of the document go into Landscape, and don’t change the rest. so far, we have not managed to make this reliable enough.
We’ll have another look in V3.1m as v3.0 has closed for new features.eadocX SupportParticipantOK – we’re back in the office now – please send a mail to enquiries@eadocx.com with a number, and I will call you, if that’s convenient
eadocX SupportParticipantI have uploaded the Sample.zip onto the Downloads section of the website (at the bottom, below the latest version of the application)
This has a sample .EAP file, and a set of example document which you can generate from it, whic sow how most of the main features of eaDocX V2 work.eadocX SupportParticipantSorry about this, but the ‘links’ attribute should have been left out of eaDocX V2 builds, as the code to create the link to the linked items was not reliable (caused EA failures!).
This will be fixed in the forthcomming eaDocX v3, which, as an existing eaDocX customer, you’ll be entitled to a free upgrade.
Expect a beta of v3 to be available in 5-10 days (mid May 2012) .eadocX SupportParticipantI’ll answer in order….
(1) Package headings are connected to the H1…Hn headings in word, and you can set the top-level package to start with any heading level – use eaDocX Preview, select the section, use up/down button to increase/decrease the top-level package’s level. All child packages then get lower-level headings.To change how H1…Hn appear, change the Word styles, as normal
(2) To get each class in a para, print ‘class’ elements as Inline.
(2a) To create a table of connectors (not connected elements??) in the Inline definition for Class, create a Relationship Table, and use a connector type of ‘Any’, then print some of the attributes of the connector – all are available
(2b) Also make ‘Class’ elements print their Diagrams, and Children, then define a profile for the ‘State’ element (or import the ‘Classes, dat and State’ profile – it has all this)
(3) Again, just define Activity elements to print Inline (each has it’s own paragraph) then add ‘Diagrams’ and ‘Children’ if needed.
Adding a ‘Children’ attribute is the way to get elements to print their composites, but you need to tell eaDocX how to print each kind of child element.
Most of this is described in the online help., but if you’re really stuck, mail the doc you’d like to see, and your .EAP to enquiries@eadocx, and we’ll sort something out for you
eadocX SupportParticipantQuite right – fixed in 2.2.1.09, available now
eadocX SupportParticipantThanks Dries – problem found, and fixed in 2.2.1.09
ThankseadocX SupportParticipantI believe this error was fixed in 2.2.1.08. Please let us know if you’re running this version and there’s still a problem.
eadocX SupportParticipantIs all this appearing in the same table? If so, the idea of the Relationship table is that you define the relatiopnship once, then print stuff about what we find at the end of that relationship – several attributes of the same kind(s) of element.
Also, in the Relationship Table page, there shouldn’t be the ‘Advanced’ button to allow multi-hop relationships.
Are you printing several tables for each Activity ? Do you have a sample showing what you’d like to see, and what’s appearing ?eadocX SupportParticipantMulti-hop relationships are one of the hardest features in eaDocX, and that’s after we deliberately tried to simplify it!
I guess you’ve found the ‘Advanced’ button on the relationship page, where you can specify the relationship ‘hops’. This page, and the ‘Add Hop’ page which follows, allow you to describe all the relationships between the source element – in your case, ‘Task’, and the target.
We designed this to print single attributes of distant elements – in our case, the distant element was the ‘Release’ to which an element is linked.
This is fine, of you just want to show a single attribute of the distant element.
If you want to show many attributes of the distant element, or – as in your case – the route of how we get to that element, then multi-hop isn’t really suitable. What gets lost is which of the intermediate nodes is linked to which other one.
This is why we developed the ‘relationship table’ idea, where you define the relationship once, then the list of attributes to print at the end of it. This works OK for a single ‘hop’, but not for the multi-hop AND multi attribute situation which yo’re describing.
All I can suuggest is creating your report using more hyperlinks, and fewer multi-hop links. So, create a report with the Tasks and their related Screens, with a hyperlink between the two.
Then, where the Screens are printed, print both attributes, and a link to their related Use Cases. Etc for the other links.
Not as nice as a simple table, but w could never figure out what a ‘simple table’ would look like which did all of this.eadocX SupportParticipantFix is now available as 2.2.1.05
ThankseadocX SupportParticipantI have a fix ready now for the problem of missing-out leading blanks. I assume that the blanks are needed so that your pseudo-code is sensibly indented – but are the chars blanks or tabs? I’ve only done the fix for blanks, as EA doesn’t let us add tab chars into description fields, but if your psedo-code is being copied-in from somewhere else, it might have tabs as well.
If you only have blanks, let me know, and I’ll put the fixed version onto eadocx.com this morning.Thanks
-
AuthorPosts
Download a free trial
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.
Download