wxMessageBox off the main thread lost result code.

[wxWidgets.git] / docs / doxygen / overviews / unixprinting.h

diff --git a/docs/doxygen/overviews/unixprinting.h b/docs/doxygen/overviews/unixprinting.h
index 2a03eab76bdb4f01d7c598d660be52b211092729..151e57444cbdc9024014f5e5f8cd27a3939ce761 100644 (file)
--- a/docs/doxygen/overviews/unixprinting.h
+++ b/docs/doxygen/overviews/unixprinting.h
@@ -2,7 +2,6 @@
 // Name:        unixprinting.h
 // Purpose:     topic overview
 // Author:      wxWidgets team
 // Name:        unixprinting.h
 // Purpose:     topic overview
 // Author:      wxWidgets team

-// RCS-ID:      $Id$

 // Licence:     wxWindows licence
 /////////////////////////////////////////////////////////////////////////////
 
 // Licence:     wxWindows licence
 /////////////////////////////////////////////////////////////////////////////
 


@@ -19,28 +18,13 @@ 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.
 
 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 <tt>configure --with-gnomeprint</tt> switch and your 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).
-
-In version GTK+ 2.10, support for printing has been added to GTK+ itself.
-Beginning with version wxWidgets 2.9.X, the GTK+ port of wxWidgets can make use
-of this feature if wxWidgets is configured accordingly and if the GTK+ version
-is = 2.10. You need to configure wxWidgets with the
-<tt>configure --with-gtkprint</tt> switch and your application will then search
-for the GTK+ print support at runtime. If it is found, printing will be done
-through GTK+, otherwise the application will fall back to GNOME printing
-support if it is available or, if it isn't, to the old PostScript printing
-code. Note that the application will not require a GTK+ version = 2.10 to be
-installed in order to run (there will be no dependency on this version).
+Since GTK+ 2.10, support for printing has been added to GTK+ itself and
+beginning with wxWidgets 2.9, GTK+ printing is used by default (i.e. unless
+<tt>--without-gtkprint</tt> was explicitly used when configuring the library).
+Support for GTK+ print is detected dynamically, i.e. during the run-time: if it
+is found, printing will be done through GTK+, otherwise the application will
+fall back to the old PostScript printing code. This allows the applications
+built with wxWidgets to still work on the very old systems using GTK+ earlier
+than 2.10.

 
 */
 
 */

-