Changes between Initial Version and Version 1 of Ticket #4196


Ignore:
Timestamp:
2016-12-26T09:30:21Z (8 years ago)
Author:
massimo ceraolo
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #4196 – Description

    initial v1  
    12123) Point 1) should be applied considering actual logical DPI’s. For instance with 168 DPI (a win system with 175% magnification) lineThickness=0.25 implies two-pixel lines. This will be useful for 4k display systems
    1313
    14 4) Finally, I propose use lineThickness=0.5 also when making array connections, i.e. "connect constructs referencing arrays of components (having size >1)” as they are defined in definitions and examples of sect. 9.1 of Modelica specifications. To have an idea no how what the appearance of a diagram would be consider also ArrayConn, in which I manually set thicknesses of array connections to show the effect.
     144) Finally, I propose use lineThickness=0.5 also when making array connections, i.e. "connect constructs referencing arrays of components (having size >1)” as they are defined in definitions and examples of sect. 9.1 of Modelica specifications.
    1515
    1616Points 1) and 3) above are actions needed to comply with specifications; the other two imply, IMO, a significant enhancement of the quality of our drawings.
     17In case of need, I can supply screenshots graphically depicting what I mean.
    1718
    1819''Note that when I say that thickness=0.5 means 0.5 mm I refer to Modelica specifications 18.6.1 and 18.6.5.1. I assume that mm’s used in those specs refer to the logical DPI: 25mm=1in=96 pixels at 96DPI, so 0.25mm is one pixel at 96 DPI