The Print Preview Components v5.14 has been released. This is a bugfix/maintenance release.

  • [bugfix] The wired bug of TThumbnailPreview on Windows XP fixed.
  • [bugfix] Getting printer’s paper size when paper orientation was landscape, could result in wrong paper orientation.
  • [bugfix] Setting paper size via form name was not considering the current paper orientation.
  • [bugfix] Setting paper size when control’s width was one pixel had no effect. Sounds strange, but it was because of misspelling of a variable name.

Reader's Comments »

  1. 1. By Vasilis Pierros on May 26, 2009 at 17:33

    Let’s test .. sounds very promising

  2. 2. By Johan van Ooijen on November 30, 2009 at 13:30

    Hello Kambiz,

    I am trying to use your TPrintPreview in a C++Builder 2010 runtime environment. I place the component on a panel using:

    PrintPreview= new TPrintPreview(PreviewPanel->Handle);
    PrintPreview->Width = PreviewPanel->ClientWidth;
    PrintPreview->Height= PreviewPanel->ClientHeight;

    and everything seems to work fine, except when the PreviewPanel is resized. After a resize the horizontal scroll bar moves out of sight and the right margin of the vertical scroll bar also moves out of sight. When I investigate the heights of PrintPreview and PreviewPanel, the PrintPreview is usually 26 pixels larger than the PreviewPanel, which explains the problem. I haven’t investigated the widths but something similar but with less pixels difference must be happening there.

    Do you think you can solve this?

    By the way, I found a possible mistake in

    function TPrintPreview.GetSystemDefaultUnits: TUnits;
    function TPrintPreview.GetUserDefaultUnits: TUnits;

    it looks like the calls to GetLocaleInfo() should be interchanged:
    GetSystemDefaultUnits has:
    GetUserDefaultUnits has:


  3. 3. By Kambiz on November 30, 2009 at 14:31

    This issue does not look like a PrintPreview problem. I think if instead of Preview->Handle, you set the object as parent of PrintPreview, the problem is gine.

    You are right about the mistakes in default units functions. Thank you for the hint!

    By the way, the forum is a better place to discuss about these issues.