V16 RC Resizing ports should allow as before to resize the port only in one dire

[PeterHeintz]

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.

[Eve]

I'm not sure I understand what you mean.

My memory says that ports have always been fixed so that their center is always on the edge of the parent object. That's going to be inconsistent with your assertion if the port is on the top or bottom edge of the parent, but not necessarily if it's on the left or right edge. On the top or bottom a resize like you describe sounds like a bug to me, and I would expect as soon as you move it it's going to reposition the top anyway.

Are you talking about on the top/bottom or the left/right of the parent? Can you provide a build number that exhibits the behavior you are after?

[PeterHeintz]

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.

[Eve]

Well, I can confirm that the behavior is different from 14.1.

It is changing the size symmetrically in both dimensions instead of only aligned with the edge it's on. To me, it's neither better or worse. I don't know the reason for the change, but you'll need to email support to get a better answer.

[qwerty]

I also think that a Port should be "flat" towards the border and not waste space inside the containing frame. A port is meant to be something towards the outside. We currently have not so many ports but their number will increase and that behavior would be a show stopper.

q.

[PeterHeintz]

Hi,
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.