eadocX Support

[eadocX Support]

At the moment, sadly no.
Creating a ‘edit all sub-elements (constraints being one example of a sub-element) is quite time-consuming, as they all behave differently. It took ages to make the ‘all attributes/operations of all elements’ one work.

[eadocX Support]

Can you describe your steps, and I will investigate

[eadocX Support]

You really as desperate….
sadly, it’s not that simple….eaDocX is designed to work with a UI, so I would need to cleanly separate the UI from the engine.
To get you started,
(in vb.net)

Dim g As New WordGenerator(neweaDocXMain)
g.profile = myProfile ‘Profile is an instance of DgDocumentProfile. I get if from the UI, which it turn got it from the current document.
g.activeDocument = aDoc ‘ This needs to be an instance of Microsoft.Office.Interop.Word.Document
…

‘(4) Generate the document
g.RunDocument()

You might be able to create a new WordGenerator with a null parameter, as that’s just a ref to the current UI, and I seem to check if there really is one.

I can’t help feeling that, without some radical re-factoring from me, this is doomed…

[eadocX Support]

Really? I would have thought that if we are being friendly to the reader, then it should be a hyperlink. Or maybe a Word popup? Never tried those, but I think it’s do-able.
I’ll try – one day…

[eadocX Support]

We used to have function to do this. In fact, in the very first version of eaDocX, before it was even called eaDocX, it used to do this, but it made documents really hard to read, as every use of the term was hyperlinked…
…and I never worked-out a way to make only the first usage of the term get a highlight, but if it’s something you feel strongly about, I can add it to the backlog.
It’ll be a while though, as I’m in the middle of the next Model Expert release 🙁

[eadocX Support]

All the testing I’ve done on this starts with creating a Quick Document. Have you tried that? I never tried manually creating Profiles for each type – most documents will have WAY too many. So try A Quick Doc, and get back to me…

[eadocX Support]

I have not tested Model Expert extensively on PostgreSQL, and it works differently from the others – i think it’s about the case sensitivity of table/column names.
I will investigate for V2. Until then, you’ll have to use MX on a EAPX file, or one of the other DBMSs.

[eadocX Support]

First of all, well done for making any of these cross-references work!
We never designed them to be something which can be created from a script, so I’m not surprised that not all of them work.
One difference between them is that the table bookmark which you are trying to create only gets used by eaDocX for the FIRST column in a table, so this might be important for you.
If you could post an example of your script, a test case XMI and word document which I can use to replicate the issue, then I will take a look at it.
Thanks

[eadocX Support]

The numbering of headings is 100% done in Word.
You need to make sure that the Heading 1, Heading 2 etc in Word, which eaDocX uses by default, are configured to use the numbering style you want.
This style will need to be in the Word template which eaDocX is using: Normal.dot is the default, so the numbered heading paragraph style needs to be in there.
Quite easy to test – just create some new headings manually in Word, and see if they get a heading number. Then save those settings as a new .dot file, as normal.dot, and eaDocX will pick up those styles and use them.

[eadocX Support]

This is only the second time we’ve been asked about this, so we’re sensing there may not be lots of demand for this feature, which would be a biggie.
The snag with using GoogleDocs might be that users might think that it’s ok to edit the document, which would be fatal – doc would be ahead of the model.
If you’d like to use a web-based approach, then have a good look at Prolaborate – excellent way to allow collaboration with non-EA users, and all on the web.

[eadocX Support]

Only thing I can think of is that maybe one of the Alias values has some spaces after the number ?

[eadocX Support]

Please can you send and XMI of this bit of your model to support@eadocx.com, and I will check that I really have fixed this problem in 1.2?
Thanks
Ian

[eadocX Support]

I’ve looked at this, and I think there is an error in Model Expert 1.1, which creates these ‘Classifier’ links, which should not be there. This is causing the validation error.
I’m working on a fix right now – I will update this post when it’s ready.
In the meantime, just delete the ‘classifier’ connectors on the reference model.

[eadocX Support]

We have an un-resolved issue with using eaDocX on screens with more than 96DPI (such as some laptops e.g. Microsoft Surface Pro), and we are still working on a solution. Are you using such a high-res screen?

[eadocX Support]

please can you try again with V4 – this new version is a total re-write of V3, and I think should fix this issue.

[Author]

Posts