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 - PeterHeintz

Pages: [1] 2 3 ... 65
1
Bugs and Issues / Re: Document generation broken in v16.1
« on: November 15, 2024, 01:53:30 am »
From my perspective the heading issue is now solved within the builds 1704 and 1629.
However the problem that PDF reports do only use ~75% of the page size still exist in both builds above.
And with V17 there is an additional issue with IBD diagrams with in V17 loos very odd.
I will rise a bug report!

2
Bugs and Issues / Re: Build 1703 Problem with “Tagged Values” in nested SysML ports
« on: November 15, 2024, 01:47:57 am »
This problem still exist in build 1704 and 1629 64Bit.
Last version not having this problem I know is build 1560.

3
Automation Interface, Add-Ins and Tools / Re: PDF reports have too wide right and bottom margins
« on: October 07, 2024, 08:43:02 pm »
Yes, same problem here and bug is already reported!

4
Bugs and Issues / Re: Build 1703 „Find Command“ is missed
« on: September 27, 2024, 09:17:55 pm »
I do not say to what Sprax should concentrate anyway!
I just say it is confunsing!😉

5
Bugs and Issues / Re: Build 1703 „Find Command“ is missed
« on: September 26, 2024, 05:24:28 pm »
Anyhow it is a "confuse the users" feature! ;D

6
Bugs and Issues / Re: Build 1703 „Find Command“ is missed
« on: September 25, 2024, 04:09:47 pm »
Ok, I found it in Style Office 2016.
But I think you can admit this is quiet tricky.

7
Bugs and Issues / Build 1703 Problem with “Tagged Values” in nested SysML ports
« on: September 24, 2024, 06:02:17 pm »
A nested port (child port) in a block allows to add tagged values (visible after adding in V14), but is neither shown in the “Tagged Values” window nor in the “Properties” control in build 1703.

8
Bugs and Issues / Build 1703 „Find Command“ is missed
« on: September 24, 2024, 06:01:10 pm »
In build 1703 the „Find Command“ feature is missed (as I assume by mistake).

9
General Board / Re: Can EA use SysML requiremente Text in place of EAs Notes field?
« on: September 13, 2024, 03:36:50 am »
I neither is the "ID" not the "Text" tagged values at all.
As "ID" I use the GUID and the "Text" I use the Note.
Not SysML compliant but much more handy.
As long as you do not wnat to switch to an other tool it does not matter, and if so a simple script could fix that.

10
Bugs and Issues / Re: Document generation broken in v16.1
« on: September 09, 2024, 06:59:43 pm »
Today I tested the PDF generation with build 1702.
Now the PDF report can also be opend with Acrobat Reader.
However still the usage of my A4 page seem to be  "letter" or something else.
In other word only round about 75% of the page size is used for content.
Any ida on this?

11
Bugs and Issues / Re: Document generation broken in v16.1
« on: August 02, 2024, 10:31:39 pm »
I belief for V16 long time ago, but not for V17. Thank you! So it is for sure not a problem of my PC.

12
Bugs and Issues / Re: Document generation broken in v16.1
« on: August 02, 2024, 09:35:09 pm »
A am still trying to find out what my PDF small page usage proble is. No I realized that I get an error when trining to open the PDF with Acrobart Reader I get an error message like:
The root object is missed or invalid.
Any idea on that?

13
Bugs and Issues / Re: Document generation broken in v16.1
« on: August 02, 2024, 04:20:24 pm »
Thank you Modesto Vega!
Exept your point one I managed all with my templates used directly to greate PDF and I intend to stay this way.
My final goal is to deliver in middterm future just the model to outr assessores and I whant to say “Hey if you need a document for whatever reason just go to the package and generate it yourself".

And currenly with PDF I am closer to what I need (less problems). All in common is that in V1701 digrams look odd. What is in PDF worse is that neither uses the horinzontal nor the vertical page space is used right. 

14
General Board / Re: Limiting "Model Search" to package?
« on: August 02, 2024, 12:00:12 am »
Or find here a MSSQL query I use as a MSSQL view on my server which generates for each t_object a "ID Path" an "Name Path" and a GUID Path" which can be used to filter path related elements.



WITH PathBuilder(Parent_ID, Package_ID, Package_Name, GUIDPath, NamePath, IDPath) AS (SELECT        Parent_ID, Package_ID, Name, CAST(ea_guid AS VARCHAR(1000)) AS GUIDPath, CAST(Name AS VARCHAR(1000)) AS NamePath,
                                                                                                                                                                                                                                    CAST(Package_ID AS VARCHAR(1000)) AS IDPath
                                                                                                                                                                                                          FROM            dbo.t_package AS pkg
                                                                                                                                                                                                          WHERE        (Parent_ID = 0)
                                                                                                                                                                                                          UNION ALL
                                                                                                                                                                                                          SELECT        pkg.Parent_ID, pkg.Package_ID, pkg.Name, CAST(pb.GUIDPath + '.' + pkg.ea_guid AS VARCHAR(1000)) AS GUIDPath,
                                                                                                                                                                                                                                   CAST(pb.NamePath + '.' + pkg.Name AS VARCHAR(1000)) AS NamePath,
                                                                                                                                                                                                                                   CAST(pb.IDPath + '.' + CAST(pkg.Package_ID AS VARCHAR(1000)) AS VARCHAR(1000)) AS IDPath
                                                                                                                                                                                                          FROM            dbo.t_package AS pkg INNER JOIN
                                                                                                                                                                                                                                   PathBuilder AS pb ON pkg.Parent_ID = pb.Package_ID)
    SELECT DISTINCT Parent_ID, Package_ID, Package_Name, GUIDPath, NamePath, IDPath
     FROM            PathBuilder AS pb

15
General Board / Re: Limiting "Model Search" to package?
« on: August 01, 2024, 09:03:10 pm »
With SQL queries you can do so as long as you are using a SQL DB supporting the "With" statement. I will look for the SQL statement I use do do that and I will post it.

Pages: [1] 2 3 ... 65