Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to achieve the same image printing quality as windows default printing?
    primarykey
    data
    text
    <p>I am handling the <code>PrintPageEventHandler</code> of the <code>PrintDocument</code> in order to draw an image to the <code>Graphics</code> device using the <code>Image.FromFile</code> Method.</p> <p>I tried to set the dpi values up to 600 and also</p> <pre><code>graphics.InterpolationMode = InterpolationMode.HighQualityBicubic; graphics.SmoothingMode = SmoothingMode.HighQuality; graphics.CompositingQuality = CompositingQuality.HighQuality; graphics.PixelOffsetMode = PixelOffsetMode.HighQuality </code></pre> <p>As suggested <a href="https://stackoverflow.com/questions/1440396/how-can-i-process-an-image-in-net-for-a-full-page-print-with-a-quality-like-win">here</a> but the printed image looks still pixeled and rough compared to printing the same file with e.g. Windows Photo Viewer , which gives a excellent result (tested on Windows 7).</p> <p>I noticed that Paint.net uses WIA Printing Dialog - does this mean the Imagequality is a .NET limitation or am i just doing it wrong?</p> <p>the complete method is here:</p> <pre><code>private void pd_PrintPage(object sender, PrintPageEventArgs ev) { // Draw a picture. ev.Graphics.InterpolationMode = InterpolationMode.HighQualityBicubic; ev.Graphics.SmoothingMode = SmoothingMode.HighQuality; ev.Graphics.CompositingQuality = CompositingQuality.HighQuality; ev.Graphics.PixelOffsetMode = PixelOffsetMode.HighQuality; ev.Graphics.DrawImage(Image.FromFile(Global.APPDATA_PATH+ @"tmp\print.png"), ev.Graphics.VisibleClipBounds); // Indicate that this is the last page to print. ev.HasMorePages = false; } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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