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 ... 61
The omg RAAML standard is alredady released.
Sparx contributed in the definition of the standard.

So I assume that sparx intend to support RAAML in future.

Is my assumtion right and if so, when will this happen and to which level of implementation?

Bugs and Issues / Re: V1605 action WriteVariable is missed
« on: August 01, 2022, 05:51:06 pm »
Ok, but what happens with my old models which uses WriteVariable because it was implemented in EA as non abstact before?

Bugs and Issues / V1605 action WriteVariable is missed
« on: July 27, 2022, 10:43:57 pm »
There is no action kind "WriteVariable" in V1605 available at least for SysML Activities.

Suggestions and Requests / Support OMG RAAML Standard
« on: July 25, 2022, 08:14:02 pm »
Please support the OMG RAAML standard.

Due to the fact, that you contributed in defining the RAAML standard I have some hope that EA will provide a Version supporting the standard soon.
If so, it would be nice to provide some indication when RAAML will be supported by EA.

In fact, free sorting helps.
I had always set to free soring and this setting remaind over the EA versions but not for V16.

States in a state machine can be moved up and down to define to order in the project browser, but initial states can not be moved any longer in V1605. Those always stay on the bottom which is the most unlogical place.

Withing V1605 some bugfixes to former V16 versions regarding coping diragrams had been done.
But coping IBD diagrams having ports in ports still not work.

Bugs and Issues / Integrity V1605 does nothing for MSSQL
« on: July 14, 2022, 12:48:35 am »
When I start a DB Integrity check within V1605 for a MSSQL DB nothing seem to happen.
V1428 find integrity problems.

General Board / Re: EA 16 and PTC Integrity
« on: June 07, 2022, 07:31:10 pm »
I use Yakindu from Itemis for that.

I used this feature so many times and I can tell you before the solution was good and now it is very bad..

A typical scenario is a follows:
Within an IBD I have a property with two ports containing sub ports on the right border.
For the upper port e.g. I have already connected all subports.
For the lower port, which is for whatever reasons customizable I add and connect ports step by step.
Each time I add a port I have to resize the parent port.
Former times (befor V16) I resized the lower border of the parent port down to have space for the new port to add. That’s it!!!!!!!!

Now in V16 when is do that, also top parent port border moves up and overlay typically the parent port above. So I have to move the lower parent port down to get rid of the overlapping. Further on, due to that fact that the child ports now stays relative to the parent center, the port resizing leads to a lot of space over the top child port. So I have to move each existing child upwards.
After having done so, I maybe realize that I resized the parent port to much, so I resize it to smaller and all that click and move stuff starts again.
With maybe 20 ports, this is just a nightmare and before V16 it was such simple.

Well I had deal brakers for all V15 as well, so we stay on V14 currently.

Hi Eve,
currently I use build 1428 but in all former versions the port resize behavior was like in this builds.
What I have is a port with ports in IDB's.
My parent port is e.g. on the right edge of the property the parent port belongs too.

My parent port is resizable and when I resize the parent port from its bottom edge the top edge stays fixed. The same happens in the other direction (resize from top-> bottom stays fixed).

No in V16 if I resize either from top or from button the center between top and bottom stays fixed and both edges move.
This is really tricky and time consuming to handle. Because now I always have to position the child ports, the parent port and it is trick to estimate the needed size.

In former versions e.g. if you resized a port on it bottom down it was possible to keep the top position. Now when you resize you always resize in top and bottom. Please go back to the solution of former version.

Bugs and Issues / V16 RC Copy Diagrams still does not include relationships
« on: February 18, 2022, 08:53:35 pm »
As on old versions coping diagrams should copy the whole diagram including relationships and not the elements only (problem seen in SysML IDBs).

PCS General Board / Re: Log4J check
« on: December 15, 2021, 10:32:00 pm »
An official statement regarding this is required from Sparx including Pro Cloud Server is required!

Pages: [1] 2 3 ... 61