Products

Home Forums Ian Mitchell

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 106 total)
  • Author
    Posts
  • in reply to: Urgent Assistance Required for TeamWorks License Issues #20956
    Ian Mitchell
    Keymaster

    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

    in reply to: Urgent Assistance Required for TeamWorks License Issues #20954
    Ian Mitchell
    Keymaster

    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
    Keymaster

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

    in reply to: multiple object type profiles per document #20921
    Ian Mitchell
    Keymaster

    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
    Keymaster

    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.

    in reply to: Only Diagrams Printed When Using Model Views #20878
    Ian Mitchell
    Keymaster

    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

    in reply to: EA crashes when using right-click after eaDocX installation #20876
    Ian Mitchell
    Keymaster

    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

    in reply to: Problem with french or unicode character #20875
    Ian Mitchell
    Keymaster

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

    in reply to: EA crashes when using right-click after eaDocX installation #20870
    Ian Mitchell
    Keymaster

    Are you using 32 or 64 bit EA?

    Ian Mitchell
    Keymaster

    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

    in reply to: Documenting SysML Blocks #20800
    Ian Mitchell
    Keymaster

    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

    in reply to: Documenting SysML Blocks #20788
    Ian Mitchell
    Keymaster

    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.

    in reply to: HEADING LEVEL 1 #20753
    Ian Mitchell
    Keymaster

    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?

    in reply to: Namespace in heading #20684
    Ian Mitchell
    Keymaster

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

    Ian Mitchell
    Keymaster

    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)

Viewing 15 posts - 1 through 15 (of 106 total)

Compare licence prices

Choose the licence that’s right for you and your team

Prices

Download a free trial

Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.

Download