Diagram Pixels by Size t_diagram.cx & cy

[Paolo F Cantoni]

We autogenerate our Neighborhood diagrams.  We settled on a default of A3 Landscape and determined that the cx and cy values were 1600x1100.  It's been thus for almost a decade.

However, in investigating the Persistent Zoom functionality, I found that creating an A3 landscape diagram manually created a 1622x1138 diagram.  That got us wondering, is the value entered into those fields driver related?

Is there any impact of printing a 1600x1100 onto a printer that expects 1622x1138?

Is there a standard value for A3 Landscape that may have changed over the years?

TIA,
Paolo

[Eve]

Code: [Select]

[ 16.5,11.5 ] x 96 = [ 1584,1123 ]Although those page sizes are only accurate to one decimal place.

ISO 216 which defines those sizes was updated in 2007, so you could be right. But I expect the page size didn't change.

[Paolo F Cantoni]

Code: [Select]

[ 16.5,11.5 ] x 96 = [ 1584,1123 ]Although those page sizes are only accurate to one decimal place.

ISO 216 which defines those sizes was updated in 2007, so you could be right. But I expect the page size didn't change.

Thanks,

But why am I getting 1622x1138?  From vague memory, we were using HP printers then and that's where we got the 1600x1100 from (other printers gave different values).  That's why I think it may be driver specific.

Paolo

[qwerty]

Printing ever since has been black magic since Gutenberg invented it. It just got more black over times.

q.

[Paolo F Cantoni]

Printing ever since has been black magic since Gutenberg invented it. It just got more black over time.

q.

So is there a standardised value I can use to "signal" an A3 vs A4 page?

Paolo

[qwerty]

I'm no Windoze expert, but AFAIK the paper format is stored somewhere in the operating system rather than in the application. The OS figures out which paper format can be set by looking into the selected printer driver. When you actually print something the OS/driver will be supplied with the printing data (not sure here, likely as pixel) and it will scale/place that on the paper (which might be virtual in case of a PDF).

q.

[Glassboy]

But why am I getting 1622x1138?  From vague memory, we were using HP printers then and that's where we got the 1600x1100 from (other printers gave different values).  That's why I think it may be driver specific.

https://docs.microsoft.com/en-us/windows-hardware/drivers/print/standard-options shows you the standard form sizes most printer driver definitions will contain.  An individual driver can have custom forms.

[Paolo F Cantoni]

But why am I getting 1622x1138?  From vague memory, we were using HP printers then and that's where we got the 1600x1100 from (other printers gave different values).  That's why I think it may be driver specific.

https://docs.microsoft.com/en-us/windows-hardware/drivers/print/standard-options shows you the standard form sizes most printer driver definitions will contain.  An individual driver can have custom forms.

Thanks, Glassboy,

But that doesn't solve my problem.  It just says the GPD will understand "A3". Problem is that EA doesn't store an "A3" it stores an A3 analogue via the cy and cy values.  I tried other sections of the site, but they kept leading back to the initial page.

I'll keep looking.

Paolo