eadocX Support

[eadocX Support]

I tried it, waited a while until it loaded, then just played the video.
It uses a gadget called Popcorn maker, but the resulting video is a simple MP4.
Perhaps it makes a difference which Web browser you’re using? I used Chrome.

[eadocX Support]

eaDocX doesn’t allow for mixtures of different EA Element Types to be documented together. It will always try to group similar element types into groups, and document them at the same place in the document, using the formatting described in the Profile for that element type. This is how it makes sure that you don’t get, for example, a 1-line table with one element type, then anther element of a different type, then another 1-line table of the first type.
We realize that, in your case, this isn’t what you want, but it’s fundamental to the whole way that eaDocX works, so sadly not something we can imagine changing.

[eadocX Support]

The glossary can only be generated on a ‘full’ generate of the document.

[eadocX Support]

Would you are to elaborate? (aka “I’m not sure I understand….:-) “)

[eadocX Support]

I was once fortunate enough to be the ‘bag carrier’ for Tom Love, inventor of Objective C. He did a pitch on “the 7 deadly sins of OO”. One of them was Multiple Inheritance. His suggestion was that, if you want to know why it’s a bad idea, just spend a while debugging some code which uses MI.

[eadocX Support]

I think you can get the StereotypesEX attribute from eaDocX: have you tried to create conditional formatting on that?
Personally, I’m not a fan of multiple-stereotypes. Seems like but a short step away from multiple inheritance, and that’s the top of a steep, slippery slope down to deep badness…..

[eadocX Support]

It took me a while, but i finally remembered the difference.
‘Children’ is just what is says: the immediate children of an element.
‘All Children’ was created at a customer’s request, and returns all the chilred, their children recursively to the bottom of the tree..
…except that it wan’t working properly in the latest release, and it didn’t seem to be in test case anywhere:-(
So, it will be fixed in the next maintenance release (3.4.4) which will be available shortly.

[eadocX Support]

Ah yes.
We decided that EVERYONE will want to print children of a Package, so it’s built-in, but that’s not the case for other kinds of Elements: with them, you have to explicitly say you’d like the children to print.

[eadocX Support]

Should be set.

[eadocX Support]

I’m assuming that the eaDocX Profile for the parent is set to print ‘children’?
Can you send an example XMI to support@eadocx

[eadocX Support]

There are some on the eaDocX.com website

[eadocX Support]

Another great use for an eaDocX Script. Just write a few lines of EA script to check that the name is not blank, then create a simple HTML string formatting the Decision exactly the way you want it.

[eadocX Support]

We have finally figured out where this ‘Invalid character in a base 64 String’ message comes from.
It is created – in error – by the Crypto routines which we use, and you should ignore it.
The REAL error code should just say simply ‘no more floating licences are available’.
Next code version (3.4.4) will hide this silly error, and just correctly say ‘no more licences’.

[eadocX Support]

eaDocX adds data to Word via its HTML interface, and ‘Heading rows repeat’ isn’t an HTML option, but tables usually get this by default.
I’m using Word 2013 at the moment, and the option to repeat rows seems to work OK for the matrix table in my current document, but like you, I seem to have to set it manually.
I wonder if Word doesn’t recognize the top row as a ‘header’? I’ll have a look at the generator.

[eadocX Support]

Excellent – this s exactly why we introduced the Scripting idea, so in the 1% case, you can get exactly what you need.
Are you able to send me a little write-up of this, to put onto the website ?

[Author]

Posts