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 ... 53
Automation Interface, Add-Ins and Tools / Re: report templates
« on: July 15, 2019, 10:39:44 pm »
I am only 99.99% sure, because sometimes I find some tricks to make impossible things possible.
However I remember that I tried it again, but gave it up. What is missed, is that you can not use the template selector for packages as well.

Oh, yes! This is what I was looking for. Thank you KP!

In V15 when you double-click on a diagram element, e.g. to open a composite diagram, the current diagram is closed. By an arrow you can move back to the original diagram.
In former version all diagrams are kept open.
If you navigate/hop to different parts of the "diagram hierarchy", before V15 you might end up with lots of diagrams opened, what is not so nice. Now only one diagram is open, what is nice if you used this hopping just to get to that diagram.

However I use this hopping most frequently to open at least two diagrams. One diagram I want to change and the others to look what I have to do. This more frequent use case (at least more frequent use case for me) worked fine for any version before V15.
To address both use cases, I would prefer a simple way to decide if I want to keep the current diagram open or not before I hop to the next.
If this is not possible for whatever reason, I would very much like if the V15 change would be cancelled.

What is the opinion of other users?

I assume stirring the menus each time around, is not intended to be an improvement of EA, but to be a improvement of us, by finding features you have never missed when searching the features you need.  ;)

Yes, I try to persuade my users to use the GUID as identification of anything (not only requirements). But I admit with no success so far.

When I ask why a requirements number or even different number groups are needed, I always get the answers “to have identification within e.g. PDF reports” and “to provide identification to which part the requirement belongs to”.

However these statement are valid to any element, not only requirements and can e.g. be addressed by the GUID and packages or links.

The GUID is not accepted because it is not "readable". And I admit “Component_Req_0001” is more readable than {EA39C8DE-572B-43b2-80DF-BA76BF19EDFB}.
But the message “This is Requirement 1 of the Component “Component” does not say so much as well. And finally if the requirement number is even used, I only see Copy/Past either to reference it in something else or the do a search.

For the Copy/Past actions it is quiet the same if you copy/paste “Component_Req_0001” or “{EA39C8DE-572B-43b2-80DF-BA76BF19EDFB}.
But we have to have “Component_Req_0001” just because we have to have. ::) ::)

No, this is not supported by EA. You might do that by writing a script.

In build 1505 you can only browse one diagram not more. This is hopefully a bug and not a new feature.

This effect is only there, if you try opening diagrams by double click on diagram elements having composite diagrams assigned to.

Bugs and Issues / Stereotype Dialog is Faulty
« on: June 18, 2019, 09:40:52 pm »
The new stereotype dialog introduced in V14 seem to intend to address a better filtering of many stereotypes. However now setting stereotypes is more often a complex or even impossible search.
Example: In V14 in tried to change an object in an SysML activity diagram to a <<datastore>>, but I had to go to UML instead of SysML1.5 to do that. In build 1503 even in UML the <<datastore>> has gone. I have no idea how I can set my object to be a <<datastore>> in build 1503.

Please validate what is shown in the stereotype list associated to a Perspective/Profile.
Currently it is more or less useless.

Seen in build 1428
The behaviour of an action is not shown in the diagram if the “Show Behaviour in Diagram” checkbox is checked.

Bugs and Issues / V15Beta Behaviour Properties Dialog Lost
« on: June 06, 2019, 08:41:10 pm »
When you double click e.g. on a “do” behaviour of an action in V14 the “Behaviour Properties” dialog opens. In build 1503 nothing happens.

It is possible to define the compartment visibility either on diagram level or on element level. Former times, element level definition had highest priority (what makes sense). Not it seems that diagram level has highest priority (makes no sence).

Several Label like pin name are not resizable to have multiple lines anymore!

Bugs and Issues / Activity Frame; Useless Auto Horizontal Resize
« on: June 05, 2019, 07:07:45 pm »
Seen in Build 1502

In a SysML activity diagram the diagram frame is made bigger in size each time something on the diagram is repositioned in any direction.

Seen in Build 1502 and 1428!

I tried to reduce the height of a SysML state machine frame, having concurrent state regions, a little bit. This caused the concurrent state regions repositioned vertically in a way that the states are not anymore in the right regions. Even worse the regions moved down and finally this diagram frame was higher in size rather than smaller. Each try to fix that, caused the regions to go deeper and deeper and the diagram frame height became higher and higher.

So I tried to fix that, with build 1428, but at the end I got a diagram frame covering over 50 pages in height.

The only way to get that fixed, was using V13, however moving 6 concurrent state regions over 50 pages up is really a imposition.

Bugs and Issues / Diagram Frame SysML IBD Ports are Wrong Placed
« on: May 30, 2019, 12:49:23 am »
When IBD is show in another diagram as diagram frame the ports within the IDB are not shown correctly on the block border but within the block.

Seen in Build 1428 and higher.

Pages: [1] 2 3 ... 53