eadocX Support

[eadocX Support]

I have magical powers over your computer….

[eadocX Support]

I can see ‘isConjugated’ in the list of tagged values for a port (but only that one, not the others) but it won’tr print the value.
This will have to wait for v4, as i’m not adding any new features for V3 🙁

[eadocX Support]

I’ve just tried this, and in my configuration, eaDocX uses the order of the elements as in the Model View. I can change the order in the MV, using the up/down button, and eaDocX prints them correctly.
Can you send me an example ?

[eadocX Support]

normally, changing the order in EA using the up/down buttons does the trick, but i have not tried this with a model view. I’ll have a look next week when I’m back in the office

[eadocX Support]

Interesting idea!
There is nothing in native eaDocX to help you, unless the ‘joining’ gateways have a different stereotype, which isn’t normal.
Best option is to write a little script which eaDocX can call to print ‘Gateway’ elements. That script could then look at the directions of the connectors coming into it, and decide what to print based on that.

[eadocX Support]

Good idea – I will add to the backlog for V4.
We don’t have a general a function to cancel generation, because that would mean we would have to make the generator run in a separate thread. We tried that a while back ,and it created a world of problem when talking to Word!

[eadocX Support]

Your timing is excellent – I’ve just put a new release of Model Expert onto the website. I’ll update the release notes shortly, but it fixes this issue, as well as having lots more great stuff.

[eadocX Support]

This is some feedback from another user, who also had problems after upgrading:
What worked was:

* uninstall all Office software (all versions)
* delete normal.dotm template to be sure it was clean
* clean the GAC of Office assemblies
* run registry cleaner in case of remaining cruft
* install VS Tools for Office 2010
https://www.microsoft.com/en-us/download/details.aspx?id=48217

[eadocX Support]

Nothing you’re doing wrong – a bug in Model Expert 1.0 – this is fixed in 1.1, which I’m just finishing-off

[eadocX Support]

Quite right. We don’t know why this happens. We used to have some code which tried to remove the ‘close’ button from Word, but that stopped working with newer versions of Word. We can’t win…
If you just close the EA tab, then eaDocX gets told, and can close Word down nicely.

[eadocX Support]

it seems to happen when Word is taking a long time to open a document, either because its the first time since you machine re-started, or because the document is on a slow server or a slow link. Again, nothing we can do as this message comes from the depths of COM.

[eadocX Support]

i don’t have any examples running with JavaScript, so I can’t say one way or the other.

[eadocX Support]

the problem is that is we save just the name of the script, that isn’t guaranteed to be unique, so that creates its own issues. But i’ll have a look for V4 and see if there is something we can do to help this cross-model re-use.

[eadocX Support]

eaDocX V3 does not support printing embedded documents, only Linked Documents. And these usually have a bad effect on the main document, if they have their own headings. Embedding documents inside other documents causes so many problems that I have no plans to add this feature to eaDocX V4.

[eadocX Support]

Has eaDocX run on this machine before? If so, what changed?

[Author]

Posts