Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#4659 closed defect (invalid)

Wrong scaling of icons in OMEdit diagrams

Reported by: Francesco Casella Owned by: Adeel Asghar
Priority: high Milestone: 1.13.0
Component: OMEdit Version:
Keywords: Cc:

Description

Please consider the PipeExample.System model in the attachment. I created it with Dymola, diagram reported in diagram1.png. When opening the same system in OMC, the pipe model is shorter and appears to be disconnected, see diagram2.png

Attachments (3)

PipeExample.mo (10.4 KB ) - added by Francesco Casella 7 years ago.
diagram1.png (6.0 KB ) - added by Francesco Casella 7 years ago.
diagram2.png (6.5 KB ) - added by Francesco Casella 7 years ago.

Download all attachments as: .zip

Change History (5)

by Francesco Casella, 7 years ago

Attachment: PipeExample.mo added

by Francesco Casella, 7 years ago

Attachment: diagram1.png added

by Francesco Casella, 7 years ago

Attachment: diagram2.png added

comment:1 by Adeel Asghar, 7 years ago

Resolution: invalid
Status: newclosed

The pipe model is drawn correctly and even the connections.

Its Dymola that is not drawing the connections correctly. Look closely at the top left connection i.e., connect(source.f_L, pipe.f_E) annotation (Line(points={{-30,4},{-24,4},{-24,2},{-22,2},{-22,2},{-14.5455,2}}, color={0,0,127})). The connection starts at (30, 4) and finishes at (-22,2). OMEdit starts and finishes the connection correctly. Dymola finishes it at (-14, 2).

Note that once you move the pipe model then OMEdit updates the connections both graphically and textually.

comment:2 by Francesco Casella, 7 years ago

This is weird, though you are absolutely right. I re-loaded the diagram in Dymola, and indeed it automatically added one more point to the connection at (-14,2). I then saved the model, and was afterwards able to recover the right diagram in OMEdit with the extra point. I wonder why Dymola did not save the (-14,2) point in the first place. But that's obviously not OMEdit's problem.

Note: See TracTickets for help on using tickets.