Databases
StackOverflow2013
Postsdbo
POSpecifying DPI of a GDI Device Context
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSpecifying DPI of a GDI Device Context
    primarykey
    data
    text
    <p>I have an application that generates metafiles (EMFs). It uses the reference device (aka the screen) to render these metafiles, so the DPI of the metafile changes depending on what machine the code is running on.</p> <p>Let's say my code is intending to create a metafile that is 8.5 in x 11 in. Using my development workstation as a reference, I end up with an EMF that has</p> <ul> <li>an rclFrame of { 0, 0, 21590, 27940 } (dimensions of the metafile, in thousandths of a mm)</li> <li>a szlDevice of { 1440, 900 } (dimensions of the reference device, in pixels)</li> <li>a szlMillimeters of { 416, 260 } (dimensions of the reference device, in mm)</li> </ul> <p>Okay, so the rclFrame tells me that the size of the EMF should be</p> <ul> <li>21590 / 2540 = 8.5 in wide</li> <li>27940 / 2540 = 11 in tall</li> </ul> <p>Right on. Using this information, we can determine the physical DPI of my monitor, too, if my math is right:</p> <ul> <li>(1440 * 25.4) / 416 = 87.9231 horizontal dpi</li> <li>(900 * 25.4) / 260 = 87.9231 vertical dpi</li> </ul> <h3>The problem</h3> <p>Anything that plays back this metafile--an EMF-to-PDF conversion, the "Summary" page when right-click on the EMF in Windows Explorer, etc--seems to truncate the calculated DPI value, displaying 87 instead of 87.9231 (even 88 would be fine).</p> <p>This results in a page that is physically sized as 8.48 in x 10.98 in (using 87 dpi) instead of 8.5 in x 11 in (using 88 dpi) when the metafile is played back.</p> <ul> <li>Is it possible to change the DPI of the reference device so that the information stored in the metafile used to calculate the DPI comes out to a nice integer?</li> <li>Can I create my own device context and specify its DPI? Or do I really have to use a printer to do that?</li> </ul> <p>Thanks for any insight.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USskaffman
    1. USNicholas Piasecki
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSpecifying DPI of a GDI Device Context
      1. USliori
      1. VTFavorite
    2. VO
      singulars
      1. POSpecifying DPI of a GDI Device Context
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POSpecifying DPI of a GDI Device Context
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIs the size on the summary page displayed correctly? Is it 748x968 or 747x967?
      singulars
      1. POSpecifying DPI of a GDI Device Context
      1. USVanuan
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload