A
Alex Clark
Hi All,
I have a print preview form in my app which consists of a PrintDocument
which is tied into a Print Preview Control, a Printer Dialog component, and
a Printer Setup Dialog component. The document property has been set on all
of the latter of those 3.
I can't seem to get my Print Setup dialog to correctly update its changes on
the Print Document however. If I change from Landscape to portrait, the
document just stays at landscape, and when I got back into the settings, I
see that it's reverted back to landscape again.
The margins are also very odd, in that I initially set a margin of 42 (in
100ths of an inch) all round. The setup dialog displays this as 4.2mm
however, and when I OK that the margins then shrink on my print document. I
then go back into the Print Setup dialog to find that all margins have
dropped to 1.7!
I had thought I recalled this being a well known bug in 1.0 of the
framework, however I can't seem to find anything about a current issue.
Plus I'm on 1.1 SP1, so if it was a bug I assume it would've been fixed
anyway. What am I doing wrong?
Cheers,
Alex Clark
I have a print preview form in my app which consists of a PrintDocument
which is tied into a Print Preview Control, a Printer Dialog component, and
a Printer Setup Dialog component. The document property has been set on all
of the latter of those 3.
I can't seem to get my Print Setup dialog to correctly update its changes on
the Print Document however. If I change from Landscape to portrait, the
document just stays at landscape, and when I got back into the settings, I
see that it's reverted back to landscape again.
The margins are also very odd, in that I initially set a margin of 42 (in
100ths of an inch) all round. The setup dialog displays this as 4.2mm
however, and when I OK that the margins then shrink on my print document. I
then go back into the Print Setup dialog to find that all margins have
dropped to 1.7!
I had thought I recalled this being a well known bug in 1.0 of the
framework, however I can't seem to find anything about a current issue.
Plus I'm on 1.1 SP1, so if it was a bug I assume it would've been fixed
anyway. What am I doing wrong?
Cheers,
Alex Clark