diff --git a/docs/latex/wx/menu.tex b/docs/latex/wx/menu.tex index debd824d6a..074289b494 100644 --- a/docs/latex/wx/menu.tex +++ b/docs/latex/wx/menu.tex @@ -9,6 +9,12 @@ identify the selection, or to change the menu item in some way. A menu item with a special identifier $-1$ is a separator item and doesn't have an associated command but just makes a separator line appear in the menu. +{\bf NB:} Please note that {\it wxID_ABOUT} and {\it wxID_EXIT} are +predefined by wxWidgets and have a special meaning since entries +using these IDs will be taken out of the normal menus under MacOS X +and will be inserted into the system menu (following the appropriate +MacOS X interface guideline). + Menu items may be either normal items, check items or radio items. Normal items don't have any special properties while the check items have a boolean flag associated to them and they show a checkmark in the menu when the flag is set. diff --git a/docs/latex/wx/menuitem.tex b/docs/latex/wx/menuitem.tex index f9a1408735..5cb61d9bd7 100644 --- a/docs/latex/wx/menuitem.tex +++ b/docs/latex/wx/menuitem.tex @@ -5,7 +5,7 @@ deal with it directly as \helpref{wxMenu}{wxmenu} methods usually construct an object of this class for you. Also please note that the methods related to fonts and bitmaps are currently -only implemented for Windows. +only implemented for Windows and GTK+. \wxheading{Derived from} diff --git a/docs/latex/wx/tprint.tex b/docs/latex/wx/tprint.tex index 8c5c774e71..11f32d2c99 100644 --- a/docs/latex/wx/tprint.tex +++ b/docs/latex/wx/tprint.tex @@ -18,8 +18,8 @@ turning preview pages, calling the print dialog box, creating the printer device context, and so on: the application can concentrate on the rendering of the information onto a device context. -The \helpref{document/view framework}{docviewoverview} creates a default wxPrintout -object for every view, calling wxView::OnDraw to achieve a +The \helpref{document/view framework}{docviewoverview} creates a default +wxPrintout object for every view, calling wxView::OnDraw to achieve a prepackaged print/preview facility. A document's printing ability is represented in an application by a @@ -51,12 +51,34 @@ please look at the printout sample code. frame->Show(true); break; } - case WXPRINT_PRINT_SETUP: - { - wxPrintDialog printerDialog(this); - printerDialog.GetPrintData().SetSetupDialog(true); - printerDialog.Show(true); - break; - } \end{verbatim} +\section{Printing under Unix (GTK+)}\label{unixprinting} + +Printing under Unix has always been a cause of problems as Unix +does not provide a standard way to display text and graphics +on screen and print it to a printer using the same application +programming interface - instead, displaying on screen is done +via the X11 library while printing has to be done with using +PostScript commands. This was particularly difficult to handle +for the case of fonts with the result that only a selected +number of application could offer WYSIWYG under Unix. Equally, +wxWidgets offered its own printing implementation using PostScript +which never really matched the screen display. + +Starting with version 2.8.X, the GNOME project provides printing +support through the libgnomeprint and libgnomeprintui libraries +by which especially the font problem is mostly solved. Beginning +with version 2.5.4, the GTK+ port of wxWidgets can make use of +these libraries if wxWidgets is configured accordingly and if the +libraries are present. You need to configure wxWidgets with the +{\it configure --with-gnomeprint} switch and you application will +then search for the GNOME print libraries at runtime. If they +are found, printing will be done through these, otherwise the +application will fall back to the old PostScript printing code. +Note that the application will not require the GNOME print libraries +to be installed in order to run (there will be no dependency on +these libraries). + +It is expected that the printing code that is currently implemented +in the GNOME print libraries will be moved into GTK+ later.