Lines Matching refs:to
14 The printing framework relies on the application to provide classes whose member
15 functions can respond to particular requests, such as `print this page' or `does
16 this page exist in the document?'. This method allows wxWidgets to take over the
21 In most cases, the only class you will need to derive from is
27 printing backends have to be offered, please have a look at the
33 wxPrintout class. This class prints a page on request, and can be passed to the
34 Print function of a wxPrinter object to actually print the document, or can be
35 passed to a wxPrintPreview object to initiate previewing. The following code
36 (from the printing sample) shows how easy it is to initiate printing, previewing
63 your subclass's overrides) writes requested pages to a \helpref{wxDC}{wxdc} that
64 is passed to it. This wxDC could be a \helpref{wxMemoryDC}{wxmemorydc} (for
70 wxPrintout object for every view, calling wxView::OnDraw to achieve a
73 If your window classes have a Draw(wxDC *dc) routine to do screen rendering,
74 your wxPrintout subclass will typically call those routines to create portions
76 calls to its wxDC to draw headers, footers, page numbers, etc.
78 The scaling of the drawn image typically differs from the screen to the preview
81 used to set the user scale and origin of the wxPrintout's DC so that your class
82 can easily map your image to the printout withough getting into the details of
89 interface. In most cases, you will not need to derive a class from wxPrinter;
95 constructs the wxDCs that get passed to your wxPrintout subclass for printing
98 subclass, for example, to change the layout or contents of the preview window.
104 and Mac. During printing, an object of this class will be passed to your derived
105 wxPrintout object to draw upon. The size of the wxPrinterDC will depend on the
129 be passed to your derived wxPrintout object to draw upon. The size of the
130 wxPostScriptDC will depend upon the \helpref{wxPrintData}{wxprintdata} used to
134 paper rectangle in a wxPostScriptDC; both rectangles are taken to represent the
139 Class wxPrintDialog puts up the standard print dialog, which allows you to
141 may vary from platform to platform). You provide an object of type
142 \helpref{wxPrintDialogData}{wxprintdialogdata} to the wxPrintDialog at
143 construction, which is used to populate the dialog.
147 Class wxPrintData is a subset of wxPrintDialogData that is used (internally) to
150 wxPrintData contains those bits of information from the two dialogs necessary to
152 might wish to create a global instance of this object to provide call-to-call
153 persistence to your application's print settings.
159 In most cases, you won't need to access this information; the framework takes
166 to specify the orientation, paper size, and related settings. You provide it
167 with a wxPageSetupDialogData object at intialization, which is used to populate
172 that allow you to change the page margins. You can use the Mac-specific class
174 wxPageSetupDialogData object in its constructor) to provide this capability; see
187 wxPrintDialog or the wxPageSetupDialog, you pass these data structures to
188 initialize the dialog values and to be updated by the dialog. The framework then
189 queries these data structures to get information like the printed page range
197 does not provide a standard way to display text and graphics
198 on screen and print it to a printer using the same application
200 via the X11 library while printing has to be done with using
201 PostScript commands. This was particularly difficult to handle
212 libraries are present. You need to configure wxWidgets with the
216 application will fall back to the old PostScript printing code.
218 to be installed in order to run (there will be no dependency on
221 In version GTK+ 2.10, support for printing has been added to GTK+
222 itself. Support for this has been added to wxWidgets in the