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] 4 5 ... 58
32
In build 1526 there is strange behavior of ports intended to be located on the right frame border when the frame border is selectable.

The ports jump from the frame border into the frame inside pane, and when you try to fix it, the frame border moves more to the right but the ports remain within the frame inside panes. It is even somehow possible to locate the ports to the right border but having the containing ports not on the border of the containing port but somewhere within the IDB frame inside pane.
In other words the rendering of ports on the right hand side of an IDB frame is absolutely broken.

33
Hi philchudley,
thank you for your response!
I withdraw this issue.
I just forgot that I have to create a block first and thought that the feature is gone in 1526.

34
Can anyone help me how to do that please.

35
Bugs and Issues / Re: Build 1525 causes OLE Waring for MSSQL
« on: January 23, 2020, 08:46:04 pm »
It is gone in 1526, but I have some other problems with that build!

36
General Board / Re: Can a component diagram show components AND classes?
« on: January 22, 2020, 11:03:58 pm »
From my UML standard interpretation, you can put anything on any diagram kind. Of cause what you mix up should make some sense.
This interpretation comes from this note in the standard:
NOTE. This taxonomy provides a logical organization for the various major kinds of diagrams. However, it does not
preclude mixing different kinds of diagram types, as one might do when one combines structural and behavioral
elements (e.g., showing a state machine nested inside an internal structure). Consequently, the boundaries between the
various kinds of diagram types are not strictly enforced.
Or see here:
https://www.uml-diagrams.org/uml-25-diagrams.html
For a long time EA had almost no diagram restrictions, unfortunately now Sparx started to implement some restrictions, but what is restricted up to now, just makes modeling for me just more difficult.
I do not say that EA should not have more UML compliant restrictions, but Sparx should not implement diagram restrictions not demanded by the UML standard.


37
Well new users do not have the problem now, but might get the problem in future, as long as the GUI commands continue to hop around each version.

38
Well, all those GUI changes form version to version are done to make EA radical better!

Some while ago in needed some seconds to find features I even use rarely, now I need more and more minutes.

A good thing needs some time and a better thing need more time. ;)

39
Bugs and Issues / Re: Build 1525 causes OLE Waring for MSSQL
« on: January 14, 2020, 12:54:51 am »
No I did not switch! Todays 1514 build (V15.0) does not have the problem.

40
Bugs and Issues / Build 1525 causes OLE Waring for MSSQL
« on: January 09, 2020, 08:21:49 pm »
When using build 1525 with my MSSQL Repository I get frequently the following OLE Warning:

Microsoft OLE DB Provider for SQL Server [0x80040e14]
The data types nvarchar and ntext are incompatible in the equal to operator.
E.g. each time I click on an item of a diagram.

41
If you are using an SQL DB supporting the SQL “With” statement, you could use something like this below to get your name space path on the fly.
Not “super fast” because it is  recursive, but if you only use is once in a query it works fine.

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

42
Bugs and Issues / Re: Generate Documentation; Scaling problem within Win10
« on: December 18, 2019, 11:46:32 pm »
Ok! I found the problem!
It is a kind of Windows issue, maybe not related to Win10 at all.

In Windows under "system" "display I changed the scaling which caused this issue. In may case a reboot fixed the problem, but maybe a logout/login cycle might fix it as well.

43
Bugs and Issues / Generate Documentation; Scaling problem within Win10
« on: December 18, 2019, 11:29:26 pm »
Hi,
Up to now I used my report templates under Win7 and all worked fine. Now I needed to switch to Win10 and I am facing scaling problems causes my reports to miss information on the right hand side as well as my footer is missed.

Any idea on that?

44
General Board / Re: New RAS Baselines!?
« on: December 17, 2019, 01:51:58 am »
Yes, right!

45
General Board / New RAS Baselines!?
« on: December 16, 2019, 10:22:41 pm »
Is there a way to migrate from model repository base lines to RAS baselines.
Once you have configured the new RAS baselines the old baselines within the repository seem to be not visible any more, what is bad.

Further on is there a way to transfer the repository baselines into RAS baselines?

Pages: 1 2 [3] 4 5 ... 58