Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - chrislro

Pages: [1] 2
1
Bugs and Issues / Re: Document generation broken in v16.1
« on: July 25, 2025, 06:08:31 pm »
I use the latest available 17.1.1712 (x64)

2
Bugs and Issues / Re: Document generation broken in v16.1
« on: July 25, 2025, 03:20:15 am »
hm. I just tried it with my template and content I created recently. I just switched from DOCX to PDF output. The generated PDF looks perfect. It seems to take over template defined page margins, etc.

3
Thank you. Still sad. I'll post a feature request ... 

4
Bugs and Issues / Re: Document generation broken in v16.1
« on: July 23, 2025, 01:11:33 am »
Just wanted to post my experience with 17.1:

I started some time ago creating new content in EA 17.0, today I am using the latest available 17.1 (x64). I have no issues with document generation for the newly created content. I try to ensure that the Model is not too complicated (e.g. no elements below elements, just one level with diagrams or embedded elements), and I do not include children when parent is filtered (this caused issues in false chapter generation).

I am not sure whether document generation with old content I created the last years also works with 17.1, but for that I have the fallback of using EA 15.2 just for exporting.

5
Hi all,

I got a diagram showing a component including its embedded provided and required interfaces. It has a lot of them, and I want to show them readable. Also, I have to add "usage" connections to other components in the same diagram. So I need to move and align a lot of elements.

Is there a way in EA 17.1 to move a block of mouse-selected interface on the components surface? I can mouse-select the interfaces as a group and at first glance it looks like I can mouse-drag them to e.g. to the other side of the same component, but nothing happens when releasing the mouse press. Distribute equally works, but not moving around. Also I would love to keyboard-move one or more embedded interfaces on a components surface. Nothing works.

Is this not supported or do I use the wrong keys/means?

6
Thank you for pointing me to it. I never worked with those before, so I need to jump into this rabbit hole.

7
Hi,

I have scripted creation of provided and required interfaces as child elements of a component. By default in a diagram, new "interaction points" are set to not visible. I can tick the boxes (Features > Interaction Points) manually in EA, but how can I script (JScript) setting the newly created provided/required interfaces to "visible"?

8
Bugs and Issues / Re: Document generation broken in v16.1
« on: January 28, 2025, 12:15:02 am »
I still like EA as a tool. I use v17 for editing, but I will still stick with EA15.2.1650 for document generation. You can install both on the same PC: EA15.2 is x86, then install EA17 as 64 bit, so they do not share the same Program Files ... works for me (still a workaround!) [as long as you are not relying on x86 plugins]

9
Bugs and Issues / Re: Document generation broken in v16.1, also 17!?
« on: November 30, 2024, 02:52:06 am »
:-\

I generated with EA17.0.1704 (64bit) a document to test it. Database content, template, styles and document generation settings are unchanged. Document is stored as a resource, output is Word format. The EA17 generated document fails with chapter order (order is mixed up), has duplicate content (some chapters are just present twice at different locations),  and some diagrams are messed up, too: Elements unexpectedly have a different size than shown in EA itself, arrows and connections are missing. Some diagrams are perfect.

As I don't want to review hundreds of pages of all generated documents, I will still stick with EA15.2.1650 for document generation. Maybe EA18 will fix it. But I start losing the hope  :'(

10
Bugs and Issues / Re: Document generation broken in v16.1
« on: July 10, 2024, 12:43:43 am »
Sounds promising ... thank you for reporting!

11
I finally came up with writing a JScript based on multiple inputs seen in this forum. Seems to work, but I just made same quick tests. Just in case someone needs it ...

Code: [Select]
/**
 * Get the package ids of the given package tree (string = like #BRANCH# in search window).
 *
 * https://sparxsystems.com/forums/smf/index.php/topic,46180.msg270523.html#msg270523
 * https://sparxsystems.com/forums/smf/index.php/topic,38987.msg259113.html#msg259113
 */
function GetPackageTreeIDArray(package /* : EA.Package */) // return: Array of descandant PackageIDs
{
if (package == null) return [];
// start with current package
var allPackages = [package.PackageID];
// get all child package IDs
return _GetChildPackageIDs(allPackages, allPackages);
}
function GetPackageTreeIDString(package /* : EA.Package */) // return: String of descandant PackageIDs like #branch#
{
var ids = GetPackageTreeIDArray(package)
return "" ? (ids.length == 0) : ids.join(",");
}
function _GetChildPackageIDs(allPackageIDs /* : Array of PackageIDs */, parentPackageIDs /* : Array of PackageIDs */) // return: Array of PackageIDs
{
// make sure there is at least a 0 is in
if (parentPackageIDs.length == 0)
{
parentPackageIDs.push(0);
}
// get all child package IDs (recursively)
var sqlQuery = "SELECT package.Package_ID FROM t_package package WHERE package.Parent_ID IN (" + parentPackageIDs.join(", ") + ")";
var queryResult = Repository.SQLQuery(sqlQuery);
var childPackageIDs = XMLGetNodeTextArray(XMLParseXML(queryResult), "//Row/Package_ID");
allPackageIDs = allPackageIDs.concat(childPackageIDs);
if ( childPackageIDs.length > 0)
{
allPackageIDs = _GetChildPackageIDs(allPackageIDs, childPackageIDs);
}
return allPackageIDs;
}

12
Quote
In the meantime I made better alternative, see github

Hm, nice, I also like to use an alternative for #Branch# in scripts. Is there also a JScript alternative for this somewhere available? Then I would not need to rewrite it ...

13
Bugs and Issues / Re: Document generation broken in v16.1
« on: July 04, 2023, 12:52:08 am »
True. Just wondering whether we could provide a small database file with some content and a document template to reproduce the issues in document generation on Sparx support side. I "only" have a large database which I cannot export (cannot show my real life content without NDA). I doubt v17 will get better without working on the issues with Sparx. Does someone have something like this we can share with Sparx?

My wishes for V17: perfect and FASTER document generation (Edit:) of large documents + ability to store centrally really ALL settings for document generation in the database (as some settings still seem to depend on settings done by the local user).

14
Bugs and Issues / Re: Document generation broken in v16.1
« on: July 03, 2023, 11:27:44 pm »
I am still using 15.2.1560 for document export, but I saw document generation fixes in v16.1.1626 (06/2023) change log. I have not yet tested the new version, but hopefully there is some movement in this topic.

15
Bugs and Issues / Re: Document generation broken in v16.1
« on: December 13, 2022, 04:08:32 am »
Just wondering: What is at the moment the most stable version for document generation?

v15.2.1560 or v16.0.1605?

Edit:
Just "dual installed" v15.2.1560 and generated the document using the same model with the same template as I used with 16.1.1622 and the headings are OK, but I recognized that I had this ugly "no padding" issue with 15.2 (see https://sparxsystems.com/forums/smf/index.php/topic,46830.msg274729.html#msg274729) ??? :'(

Pages: [1] 2