I created a class based on your example in Chapter 23 pages 643-646. It all works great when I print to the PrintPreviewDialog (formatting is fine and page breaks are as expected), but as soon as I click the Print button in the dialog or try to print directly, it acts as though it has an infinitely long piece of paper so much of the text is printed "off" the end of the paper.

The code suggests that the MeasureString function will determine the number of characters that can be fitted in the available rectangle below ymin and, even when the layout_rect.Height is a negative number it continues to print the next line. My paragraph collection is mostly single line paragraphs, very few exceed one printed line.

I tried forcing the page break by exiting the loop when ymin exceeded e.MarginBounds.Bottom and that works, but I lose the last paragraph on that page. What is the fundamental difference between the paper page and the print preview that prevents the PrintPage routine from exiting when the layout_rect is too small to print a line and how can I make it break correctly?

Thanks much.

Al Mowbray

I'll take a look, although I don't think I'll have time until tomorrow. Rod

Rod
[email protected]
Author of "Visual Basic 2005 Programmer's Reference"
http://www.vb-helper.com/vb_prog_ref.htm

Just a quick suggestion. It looks like MeasureString returns an incorrect result if the layout rectangle has a negative height. Try something like this after setting the layout rectangle:

    If layout_rect.Height < 0 Then layout_rect.Height = 0

Or you may need to set it to 1 instead of 0. I don't know if it will have the same problem with 0 (and I can't check right now).

Let me know whether that works and I'll try it out tonight.



Rod
[email protected]
Author of "Visual Basic 2005 Programmer's Reference"
http://www.vb-helper.com/vb_prog_ref.htm

You had that statement in your original code and I incorporated it into mine, but that did not fix the problem. It seems that when the layout_rect.Height is less than one line height, the text_size function should return 0 characters_filled and 0 lines. That should make the routine exit and set e.HasMorePages to True. It does work this way for the PrintPreview dialog, but it doesn't work on an actual printer (I tried it on 2). I don't understand why the formatting is correct in the dialog, but incorrect on paper??

I am getting closer to a solution by setting the e.MarginBounds.Bottom to a larger number and it seems to work most of the time. I will keep trying.

Thanks for the reply.

I think this is a bug in the MeasureString method (or perhaps whatever it is talking to). Even if it required the layout rectangle's height to be greater than 1, it should be consistent.

It seems that MeasureString is always allowing you to print at least one line. I think the fact that you are printing lots of single-line paragraphs is relevant.

It seems to work if you compare the available height with the font's m-height before printing like this:

    Dim m_height As Single = e.Graphics.MeasureString("M", the_font).Height
    If e.MarginBounds.Bottom - ymin < m_height Then
        ' There's no room for anything.
        characters_fitted = 0 ' This breaks out of the loop.
    Else
        ' Print as before ...
    End If

You can download a revised project at http://www.vb-helper.com/VbProgRef/U...intBooklet.zip.

Let me know whether it works on your system.

Rod

Rod
[email protected]
Author of "Visual Basic 2005 Programmer's Reference"
http://www.vb-helper.com/vb_prog_ref.htm

(Note that the forum software cleverly included the trailing period in the revised project's link in the previous posting. Copy and paste the link text into your browser and remove the period at the end.)

Rod
[email protected]
Author of "Visual Basic 2005 Programmer's Reference"
http://www.vb-helper.com/vb_prog_ref.htm

That solution worked. The formatting remains different for the Print Preview dialog as compared to the paper, but at least it is generating a new page at the appropriate place and there are no dropped lines or paragraphs. I am sure it has something to do with the single line paragraphs as you mentioned.

Thanks a lot for the help - great book, by the way!

Al Mowbray

> That solution worked.
Excellent!

> The formatting remains different for the Print Preview
> dialog as compared to the paper, ...
Hmm. Why don't you zip up the project and email it to me (RodStephens@vb-helper.com) and I'll take a look to see if I can suggest anything. (Could there be a font difference? Perhaps the system and printer are picking slightly different fonts.)

> Thanks a lot for the help
No problem. Let me know if you have other problems, comments, etc. either here or vis direct email. I'll post any updates on my Web site.

> - great book, by the way!
Thanks! Always nice to hear someone finds this all useful. Post a review on Amazon!

Best wishes,


Rod
[email protected]
Author of "Visual Basic 2005 Programmer's Reference"
http://www.vb-helper.com/vb_prog_ref.htm

This is a wonderful example of many aspects of Object oriented programming for an old VB 6 programmer like myself who is just learning.

However, I think I have found two comment errors (in both the book and the revised downloadabled version) in the "PrintPage" event handler, in the 'if-then-else' statement where the Page # is being printed in the margin. The first comment for "even" pages:

    "'The gutter is on the left"

is incorrect. It should be changed to:

    "'The page # is printed on the left, opposite the gutter on the right"

Similarly, the comment that follows for "odd" pages also needs to be changed.

Truman Byron Thomas

Yes, you're right. I'll post a note on the book's Web page.


Rod
[email protected]
Author of "Visual Basic 2005 Programmer's Reference"
http://www.vb-helper.com/vb_prog_ref.htm