Document.Printer.PaperHeight doesn't match PageSettings.PaperHeight
ActiveReports for .NET 3.0 Support
Document.Printer.PaperHeight doesn't match PageSettings.PaperHeight
04-23-2009, 8:12 AM
I'm trying to figure out why the dymo labels I'm generating expand to a second page. After some testing it looks to me like
Document.Printer.PaperHeight
is for some reason becoming smaller than
PageSettings.PaperHeight
and the
DetailHeight.
I'm using
PageSettings.PaperKind = Custom
and
Document.Printer.PrinterName = ""
The weird thing is it matches fine when my height is 2.15 but not 2.11.
when PageSettings.PaperHeight = 2.11 then Printer.PaperHeight = 2.10
when PageSettings.PaperHeight = 2.10 then Printer.PaperHeight = 2.09
when PageSettings.PaperHeight = 2.15 then Printer.PaperHeight = 2.15
I have attached a test application so you can see the problem I'm having.
Re: Document.Printer.PaperHeight doesn't match PageSettings.PaperHeight
04-24-2009, 10:51 AM
After testing this issue at our end, this issue has been identified as a bug. I have opened a new Case 129376 to get this issue addressed. I have also added your E-mail address as an affected user to this case.
In the meantime you may want to register to our announcement forums to know about the upcoming builds and releases over the following link:
http://www.datadynamics.com/forums/54/ShowForum.aspx
Re: Document.Printer.PaperHeight doesn't match PageSettings.PaperHeight
04-24-2009, 1:30 PM
Might want to double check your release announcements if your going to recommend looking there. Looks like your last announcement is for
Build 5.2.1132 (SP2, Hotfix 6) but the latest is
Build 5.2.1178 (SP2, Hotfix 7) .
Re: Document.Printer.PaperHeight doesn't match PageSettings.PaperHeight
04-27-2009, 4:40 AM
Hi there,
We've recently begun a series of maintenance releases that target only a handful of issues with each release. These releases are tested and made available to everyone however because of the limited scope and the frequency of these releases we felt it was ideal to avoid being spammy and post to the announcement forum -- which sends an email to thousands of users -- only when a significant build is released.
Customers affected by issues that were addressed should still be contacted regarding their issue being addressed.
If you have any additional questions please feel free to ask.
James