eadocX Support

[eadocX Support]

Mark – sorry I missed this.
Yet again, my lack of knowledge of EA lets me down 🙁
How does one create FlowProperties? Once I can create some, I’ll have a look at how to document them!
BTW – is this a SysML thing? Do I need the SysML add-in installed ?

[eadocX Support]

The Brains Trust have met again, as you used the magic words ‘manually write’, which always encourages us to think harder: we don’t like ‘manual’:-)

How about:
1 – create a H1 heading in your document
2 – Add an Element Report, H2, listing the Child packages and their descriptions
I’ve tried this, and in my version (eaDocX 2.2) it does work
3 – Add the main section describing the Parent package, children, use cases etc, also has a H2.

OR
When you print your package diagram which has the child packages, make it show the contents of the packages (which you probably already do) AND tell the diagram to print the Notes field of the Packages. Then you’ll have all the info you need, albeit on a diagram rather than on a table.

[eadocX Support]

Sorry for the long delay…
Good idea !
I’ve added it to the ‘to do’ list for the next release (2.3)

[eadocX Support]

Ok – I think I’ve got it.
Short answer is – you can’t.
The most fundamental idea of eaDocX is that you define how a ‘thing’ gets printed, then wherever that ‘thing’ appears, it gets printed in the same way.
What I think you’re asking for is for, in one part of the document, Package things to print in a table, then later in the same section, for them to print Inline, with ll their children & child diagrams.
The only exception to this rule is for Element Reports, where we allow the formatting of the results to be different. This could give yo a bit of what you want – a list of the Child packages – but in a separate section.

We’ve had a long discussion about this, and decided that what you’re asking for is so different from the way that eaDocX works, at the very lowest level, that we can’t fix this for you.

[eadocX Support]

OK – I’m clear now that I’m not clear about what you need 🙂

Perhaps you could attach a fragment of you model (screenshot will be fine) and a little example of what you’d like eaDocX to generate for you. Then I’ll hve a look. Doesn’t sound too impossible.

[eadocX Support]

Pat,
You’ve sent me into a dark place: Word Table Styles. There be dragons.
It seems that there is an ‘interesting’, though largely deterministic, interaction between the table settings which eaDocX is allowed to specify(via the HTML into Word interrace we use) and the Word Table Settings which may already exist in your Word document.
What I’m going to try out is removing some settings which we currently allow you to change in eaDocX (colours, borders etc) and allow you to change those only in Word – these are the ones which DO work in Word.
BUT, keep some of the options which DON’T work in Word (border collapse, vertical alignment) in eaDocX, and force Word to do what we want.
Would you be able to do quick beta test of this for me, once there is a 2.3 Beta?
Also, which Word version are you using – 2010 would be useful, as most of my test VMs are 2007.

[eadocX Support]

This is an EA ‘feature’. For elements which are just created in a package, EA doesn’t save their order: they seem to be able somehow get them in the right order in their UI, but at the API which we have to use, the order isn’t fixed.
BUT, all you have to do is select one item in the package, move it up or down one, then move it back to wehere it was, and EA suddely remembers the order of ALL the elements in the package.

[eadocX Support]

You’re right – it’s a hard-coded value in eaDocX at the moment.
If we were to include this as a user-settable option (probably in Options | Tables) then it would apply to all tables in the document, not per-element type.
Would that do the trick ?

[eadocX Support]

2 possibilities:
1 – give each of your Child packages a stereotype, then create an Element Report listing them, with a simple list of their children
2 – create a differernt kind of Word table-of-contents?

not tried either of these myself, but it might work

[eadocX Support]

Could you elaborate?
There was a problem with not appying the Advanced filtering to Element cross-reference reports, which will be fixed in the next 2.2 Beta. Have go with that.

[eadocX Support]

eaDocX only uses the Headings which are present in the Word document: Heading 1…Heading 10.
If the Headings don’t look right, it will probably be the style settings in Word which have gone wonky.

[eadocX Support]

Are you doing anything between the first and second ‘generates’ ?

[eadocX Support]

Are you using the 2.2 Beta?
In the GUIElement, get it to print it’s Element Features (a Standard Attribute). this will follow any kind of connector which has an attribute or method at the other end.
Versions of eaDocX prior to 2.2 can’t do this.

[eadocX Support]

Does the document contain an error message like ‘unable to insert linked document..’ ?
To insert LinkedDocuments, we have to save them in a temporary file in the same directory as the document (called temp.rtf) then insert that into your document. This is the only way we can get the LD content out of EA in a sensible way. Perhaps eaDocX can’t create the temp.rtf file due to permissions?

[eadocX Support]

I remember now why I didn’t do it before: our web server doesn’t like .ZIP and .EAP files – if you send an email address to support@eadocx then I will mail you the eaDocX Sample.EAP
Thanks

[Author]

Posts