eadocX Support

[eadocX Support]

This is a strange one.
We fixed a bug with the glossary which was picking up abbreviations which were inside other words – e.g if ‘IBBL’ was in the glossary, and you had the word ‘Wibble’ in the document, then the ‘IBBL’ term would print – clearly wrong.
So, we changed the glossary generator to look for spaces before an after the term.
BUT,
it seems like this is missing out terms which SHOULD be there! e.g. when your document contains ‘IBBL.’
Looks like we’ll have to have another go at this, as people seem to be finding auto-Glossaries useful.

[eadocX Support]

We don’t have access to Citrix, so can’t test in that environment.
The key is cached in the application settings, which I guess on a ‘real’ machine ends up in the repository. Guessing again, Citrix may not honour the application settings from session to session, though eaDocX can’t be the only application which does this ? is it perhaps a Citrix setting ?

[eadocX Support]

Matt
Could you mail a little example to support@eadocx.com and I’ll have a look.
Ian

[eadocX Support]

Thanks for the screen-shot- it really helps.
This problem is fixed in the next eaDocX Version: 3.2, which will be available later in the summer of 2012. It’s currently in Alpha testing.

[eadocX Support]

I agree – can you send me your current eaDocX Profile, and I’ll have a look. Send the support@eadocx.com
Thanks

[eadocX Support]

We agree – this is a pain.
We’ve had several tries to fix this one. When you try to open a document in eaDocX which is already opened in Word elsewhere, we tried to take-over to the document, but that seems a bit dangerous – someone else might be using it.
The only advice we can give is to only edit eaDocX documents inside eaDocX: the most common place this occurs is when the same person opens the document in native Word and eaDocX.
We can’t figure out how to make this dialog come to the top, as it’s produced by Word, not eaDocX.

The problem is easily fixed by:
– close eaDocX
– open the file in native Word, which may complain that the document is broken – it usually isn’t
– close the document nicely
– kill-off any dangling winword.exe isnatnces, using task manager
– open in eaDocX, and carry on…

Not simple, but most users seem to get used to only openeing in eaDocX.

[eadocX Support]

So far, I can’t reproduce this error, using 3.0.6 and an Oracle DBMS back-end.
What were the Profile settings before you tried to switch from table to inline (or was it the other way around).

I’m wondering if this is another of your Oracle issues, or one which is independent of DBMS.

• This reply was modified 12 years, 4 months ago by eadocX Support.

[eadocX Support]

We weren’t aware of this.
Will put on the list of future fixes.
Thanks

[eadocX Support]

I think I have fixed this in the current release – 3.0.6.

[eadocX Support]

Send to support@eaDocX.com

[eadocX Support]

Does you Profile for Packages include ‘diagrams’? Otherwise, eaDocX won’t print diagrams. I recommend you look at the eaDocX Online help.

[eadocX Support]

Right-click on the ‘X’ items, then select ‘Show Profile’, answer ‘yes’ to ‘would you like to define formatting…’ then define whether you want table or inline formatting for each element.
OR
Create a document using ‘Quick Document’, which will make sure all element get printed:
– select the Package where the stuff you want is located
– Right Click in EA Project Browser, Extensions | eaDocX | Quick Document, then, once you have a document, just edit the profiles for each kind of element & stereotype to get what you want

[eadocX Support]

We have now had a look at this, as we have had the same request from other customers.
Our first approach is to encourage Sparx to give us access to the code they have already written for their RTF generator. Another of our customers has already placed a request in the Sparx ‘Request a Feature’ section, but if you can please submit one as well, that will realy help – Sparx seem to deal with these on a ‘most requested feature’ basis.
We have also spoken to Sparx separately, to provide additional encouragement.

[eadocX Support]

Difficult for us to fix this one, without access to a machine with exactly the same setup and access rights are yours.
eaDocX needs access to the .NET files, as that what we use for our user interface, so they are quite important!
Can you determine which part of the application is causing the error?
Also, try the Installation Verification test:
EA menu | Extensions | eaDocX | Help | Check installation.
This tests the lowest-level EA and Word interfaces, to make sure they are configured OK. You should get a very simple Word document produced. If this doesn’t work, then there’s no point continuting until the problem is fixed: eaDocX can’t talk to EA or Word.

[eadocX Support]

There is still the ‘close’ (‘X’) at the top right hand corner of the eaDocX window, outside of Word, but inside of EA. It’s directly above the ‘Help’ item on the eaDocX menu strip.

We use this for ‘close’ so that eaDocX gets to hear about the window closing, so that it can do things like saving a current profile & document.

[Author]

Posts