Ian Mitchell

[Ian Mitchell]

I’m not in the office at the moment, so I can’t look at this until later this month. I thought I fixed it in 1.3.7.4, but it looks like it still has some issues.
I will update this post when I have created a fix.

[Ian Mitchell]

I have not looked into the ‘print a model view’ use case for quite a while. In fact, I can’t find the test case in the latest release.
I’ll have a look and get back to you
Ian

• This reply was modified 6 months, 2 weeks ago by Ian Mitchell.

[Ian Mitchell]

This looks like an error from EA, so I have no way to investigate this.
I suggest you submit a support request to Sparx at https://sparxsystems.com/support/forms/bug_report.html
Sorry I can’t be of more help
Ian

[Ian Mitchell]

Please can you install the latest version, and try this again. Beta 1.1.2 is quite an old version.
Thanks
Ian

[Ian Mitchell]

Are you using 32 or 64 bit EA?

[Ian Mitchell]

I think this issue arrived with v 1.3.7.3, and was fixed in 1.3.7.5.
Please can you re-test with the latest verison ?
Thanks

[Ian Mitchell]

Change of plan.
I have spent a few days looking into re-implementing Scripting into eaDocX, but it is not possible.
The mechanism we used to use to do this used a 32-bit Microsoft Script Control, which does not work with 64 bit EA.
Sparx have confirmed this as an issue, but there is not out-of-the box fix.
I investigated a third-party solution, but it was very unreliable.
So sadly, there is no solution to this issue.
Sorry

[Ian Mitchell]

Hi Paul,
No way will this ever be fixed using the main functions of eaDocX. Everything works using an (element type + element stereotype) combination, so the whole thing would explode.
But don’t dispair.
There was a feature in v5 which uses little bits of script to basically do anything: print any bit of a Word document, ijn any style, using any bit of EA data, and using any rules you can think of. I have not yet put this into eaTeamWorks (nobody needed it until now) but as you have asked so nicely, I’ll find the code and put it back.
I will also use your example of a secondary stereotype of a <>Class as a test case.
But will take a few days to implement, so go on your holidays, and it will be ready when you get back.

[Ian Mitchell]

I think the left/right justifications of headings are part of the Word paragraph style defintion. Can you check that this is set correctly for your H1 style?

[Ian Mitchell]

Fixed in verion 1.3.7.1, now on the website.
See separate note.

[Ian Mitchell]

We know that the eaTeamWorks installer tries to install un-signed DLLs, which is a problem in some environments.
This has been on the backlog for some time, and increasing a problem, so we will increas it’s priority.
For now, if you are not allowed to install un-signed DLLs, then we are sorry but you can not use eaTeamWorks (or any previous versions of eaDocX)

[Ian Mitchell]

Which version?
All posts on here must say which version you are using, and we will ALWAYS suggest getting the latest verison and trying again.

[Ian Mitchell]

Does this happen with one specific package? Or for any package?

[Ian Mitchell]

I ALWAYS need to know which eaTeamWorks verison you are using.
And I will ALWAYS ask you to check that the problem occurs in the latest verison of eaTeamWorks which is available on the website.

[Ian Mitchell]

Which version?
I can’t replicate this.
Have you tried with other packages ?

[Author]

Posts