eadocX Support

[eadocX Support]

This was not a known issue – bit it’s known now! Thanks
I will fix in V4, which I’m currently testing. No estimate for completion – it’s complete when the quality is good enough for you all to use!

[eadocX Support]

what happens with other plugins? Is this uniquely an eaDocX issue?

[eadocX Support]

eaDocX does not intercepts any of the messages which EA creates when making diagrams. It MAY be that EA is creating other messages, which we do intercept, and which eaDocX doesn’t understand.
Probably one for the EA forums…

[eadocX Support]

do you have eaDocX Corporate Edition?
If you enable the eaDocX Technical Trace (see help for details), what does it say?

[eadocX Support]

The whole style-override mechanism if very fragile – it uses some bits of the Word API which I’m fairly sure never got tested, as they deliver contently inconsistent results.
If I were you, I’d find a way to work around this, and avoid style-overrides completely.

[eadocX Support]

Sorry, but the eaDocX Relationship Matrix report doesn’t support multi-hop relationships – yet.
It’s on the backlog, but I can’t figure out the UI bit of it – the technicals work just fine.
No expected date for delivery…

[eadocX Support]

This brings-up an interesting wider point.

Is it ever OK to print some data twice in the same document?

In a manually written document, the answer is clearly NO!
But if it only happens occasionally, and the reader can see that it’s an duplicate (it’s formatted the same way), and the model+generator approach makes 100% sure its exactly the SAME data, that where’s the harm? It’s something we try hard to avoid when writing the eaDocX generator, but maybe something which we should educate our readers to expect, once in a while.

[eadocX Support]

Yes.
Though, as a modeller, I think this isn’t a great way to do things, but hey, that’s just my view.
Look under ‘Sub-elements’ pull-down in the Inline Profile page.

[eadocX Support]

In a meeting of the EA user group a few years ago in Netherlands, I did a talk about ‘which bits of EA do people really use?’.
And, based on a non-scientific, but probably representative sample of 150 EA users from all over Europe, almost nobody used the Element resource, element issues ideas: people who do Project Management seemed to use MS Project, or similar tools. And those who do issue tracking overwhelmingly use Jira (see recent announcements from Sparx and Proaborate)
They din’t use EA.
For that time on, we changed our development approach to concentrate on core EA function, and stopped trying to support do all the strange stuff which Sparx build into EA.

I understand this is no help to you, but we have a finite amount of development time, and we want to help the majority of our users.
So for this reason, we have not, and don’t propose to, make Element Issues, -Resources, -Risks, or -Effort a priority for either eaDocX or eaXL development. So there will be nothing new on those areas in eaDocX V4.
I’m saying this because we are 100% driven by what our users tell us they need from eaDocX and eaXL, and this sadly means that everyone can’t have everything they need.

Even if they really need it.

Thanks for your understanding.

Ian M

[eadocX Support]

If you send an XMI of the bit of the model, and a little document with the Profile, to support@, I’ll have a look.

[eadocX Support]

In a word, no.
I’m still working through 4.0, and it’s taking a while. That won’t be done for many weeks yet, then I think I’m due some time off…

[eadocX Support]

Hi John,
My bad – somehow I missed-out ‘Priority’ attribute for Issue elements. Probably because some EA elements have a Priority, and other don’t, and I’ve never figured out the pattern.
Not that it helps you right now, but I’ve fixed this in V4, which I’m working on at the moment, but I can’t put this fix back into V3, so I’m really sorry you’ll have to wait for V4. Should be ready in a few weeks.

[eadocX Support]

Hi Dina,
(i think this problem has my name on it…)
It looks like eaDocX inserts a comma, then a space, then a CRLF character between the elements: makes it look sensible when put into a Word doc.
CRLF = ASCII chr(13) & chr(10), so a find/replace on this character sequence should fix it.

[eadocX Support]

no – no fix planned. I have looked into this before, and can’t find a solution/

[eadocX Support]

What are the differences between the computers? Do they have the same text size ?

[Author]

Posts