Ian Mitchell

[Ian Mitchell]

Hi Rodney,
What version are you using?

[Ian Mitchell]

Thanks for the update.

[Ian Mitchell]

The current version of eaSheets in eaTeamWorks no longer supports the idea of Named Ranges – these were an idea from the days when we used Excel. I guess you must be using quite an old version of eaDocX if it still has Excel support – we discontinued this a few years ago.
You can either continue to use the old version on an ‘as is’ basis, or get the latest eaSheets product, delivered via eaTeamWorks. This is the only version we support.
Thanks
Ian

[Ian Mitchell]

Yes, that eaTeamWorks version is compatible with EA 17. It’s the EA version we run in our test environment.
The challenge here is that when eaTeamworks creats the correct menu items for a right-click, It go into the repository, and we don’t know exactly what we will find there. In your case, something which EA doesn’t like.
I have added some more error checking into version 1.3.7.10, which is now on the website.
This isn’t the smartest way to fix it, but it might work.
If not, I may ask you to try and create the smallest possible repository which still shows the error, then I cna see what EA doesn’t like.
So please, if you can try this new version, let me know what happens.

[Ian Mitchell]

Somehow the Profile and the document have got out of synch.
This error happens when eaDocX looks through the document to find all the eaDocX sections (the bits which start and end with the pink text), but when it looks into the Profile, it can find anything about that section.
Best plan is to delete the section manually from the document (select text from BEFORE the pink bits, to AFTER the end of the ‘end’ pink bits, and delete that from the document. Don’t worry, all the content comes from EA, so you will not lose anything.)
Then just add back a new section, in the right place, and re-generate.

[Ian Mitchell]

If there is no Profile for Pools and Lanes (which are types of ActivityPartion), then these will not print.
Please can you put the Profile for your document into this post, and I will take a look? (should not be confidential).
To so this, open your eaDocX document, and find the ‘SAve’ menu, and choose Profile / Save profile. This will create an XML document whihc you should be able to paste here.
Thanks

[Ian Mitchell]

I think ‘normal’ resolution is up to 96 DPI. Anything more than that, and the application gets confused, because the form sizes and the font sizes don’t match. I’m not in the office yet, so I can’t see the settings on my surface pro, but I think I have to set the screen to 100%, not 125 or 150%. I know this then makes the text really small, which is why I always use an external monitor, and set that to 100%.
I think there are other answers to this question on this forum – please can you search for them?
Thanks

[Ian Mitchell]

Hi Pavel,
Sorry you having problems with eaTeamworks.
I think many of these issues have the same cause. If you are using a high-resolution screen, such as on a SurfacePro laptop, then the screen sizing will not work correctly. This is a known issue, which we are trying to fix.
Please can you try either using an external monitor which has a normal resolution, or switch your laptop monitor to normal resolution.
Thanks
Ian

[Ian Mitchell]

I have made 1.3.7.5 available, which I think fixes this issue.

[Ian Mitchell]

Good question!
The first requirement we had for eaDocX – 13 years ago – was to make documents consistent, so that a use case in one part of a document looked just like a use case somewhere else.
Only later did we understand that sometimes this is not quite enough, so then we allowed different profiles for different stereotypes of elements, which is what we have now. So if your use cases have different stereotypes, then that’s easy.
If you need use cases of the same stereotype to have a different appearances in the same document, you can do this by printing some of the use cases as Element Reports. Each Element Report can have its own profiles, so you can then, for example, have a short form of a use case in one place in the document, then a set of element reports elsewhere with more details.
All this is described in the help – just look into inserting element reports.
If you have any more questions, please add this post.
Thanks
Ian

[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 5 months 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?

[Author]

Posts