Hi Matt,

Thanks for your answers. I solved the problems by looking into the code of the PrintManager, thats hidden in the Report class. looks like my old code had some mistakes in the calculation of the scalingfactors and some other strange statements.

The only actions i had to do:

0.Set PrinterSettings of PrintDocument (from PrintDialog)

1.GetPage

2.Scale graphics depending on property landscape

3.Draw to Graphics

nothing more ;)

Best Regards,

Ali

Ali,

1) Unfortunately, the only solution is to submit a feature request, since this would require the adding, and testing of new functionality and I can't really come up with a good workaround to this that you're not already aware of, since there is an internal PrintDocument.  Basically all this code does is use an Infragistics.Documents.Graphics.Graphics class to draw each ProjectionPage; the Graphics object wraps the graphics object provided by the PrintPageEventArgs, then scales it to the available size per page.  If you have access to the source code, you can look at the Infragistics.Documents.Report.PrintManager class' PrintPage method to see exactly how it does this.

2) So what I gather here is that you can either print to a printer, or publish the report to PDF, but you can't do both with the same method?  I'm not sure how you're trying to publish something to PDF/XPS after you have a PrintDocument, since at this point you're directly rendering an image of each page to the PrintDocument, thereby losing any of the PDF/XPS/Report objects that you originally had.  Perhaps the method I outlined above, with using the Infragistics Graphics class, might help you with this but I can't really say for certain.  Since you're losing the Document's engine to write to native PDF/XPS by converting an image, there may be no way to accomplish this short of publishing the report twice, once to a file (that you could even keep in a MemoryStream), and the other through your PrintDocument.

-Matt

Hi Matt,

Thanks for the reply. The given options in the Report are too few. I could try a feature request, but this would take to long, because i have to finish the project. so i try to describe my situation/problem better.

My original problem was, that its is not possible to customize the print options (only few) in the print method of the report. Normally i would use a PrintDialog and get the PrinterSettings/PageSettings. I had expected that the report can take PrinterSettings/PageSettings as a parameter.

This problem caused me to use the IProectionPageCollection  inside the PrintPage-Events of the PrintDocument. That way i can use the PrinterSettings of the PrintDialog.

Here my 2 Situations:

1. The Pdf that was printed with Print-method of Report looked well. Both in Pdf/XPS and Print.

Missing Feature: the possibility to use a PrinterSettings object (for number of sites on one page, duplex print, colored ...).

2. When i use the PrintPage-Event of the PrintDocument to draw the ProjectionPage to the Page i have the PrinterSettings and can print the PrintDocument.

But when i want to print to PDF or XPS the results are not what i expect. And i dont understand why this happens. Could it be that the Draw-method of IProjectionPage has some limitations or bugs? Opening a PDf generated that way cause often errors and the the XPS version is a blank page.

And thats the real problem: I dont want to explain the user why he needs twice the number or buttons for his print-jobs because i cant unite the features of Report and PrintDocument ;) So i need a hint to find the problems with the Draw-method of IProjectionPage or a Report with PrinterSettings-Support.

I will be hard to put that much code in here but if you need some part of my code to help me that i will try.

Best Regards,

Ali