added workaround for GTK+ focus_out bug (and removed Vaclav's mouse capture stack...

[wxWidgets.git] / docs / symbols.txt

diff --git a/docs/symbols.txt b/docs/symbols.txt
index 1b2865d1cf8cd49680309865a622ac07acf3b1e9..d79695390bf17479f396edde633e1f0310aa6462 100644 (file)
--- a/docs/symbols.txt
+++ b/docs/symbols.txt
@@ -9,7 +9,9 @@ __WXXT__        Xt; mutually exclusive with WX_MOTIF (?)
 __WXGTK__       GTK
 __WXGTK12__     GTK 1.2 or higher
 __WXMSW__       Any Windows
 __WXGTK__       GTK
 __WXGTK12__     GTK 1.2 or higher
 __WXMSW__       Any Windows

+__WXWINE__      WINE (i.e. Win32 on Unix)

 __WXMAC__       MacOS
 __WXMAC__       MacOS

+__WXPM__        OS/2 native Presentation Manager

 __UNIX__        any Unix
 __WINDOWS__     any Windows
 __WIN95__       GUI for Windows 95 and above; NT 4.0 and above.
 __UNIX__        any Unix
 __WINDOWS__     any Windows
 __WIN95__       GUI for Windows 95 and above; NT 4.0 and above.


@@ -18,7 +20,7 @@ __NT__          Windows NT
 __WXCURSES__    CURSES
 __WXSTUBS__     Stubbed version ('template' wxWin implementation)
 
 __WXCURSES__    CURSES
 __WXSTUBS__     Stubbed version ('template' wxWin implementation)
 

-In fact, they should better all start with __WX instead of __ only. 
+In fact, they should better all start with __WX instead of __ only.

 The only GUIs implemented for 2.0 are __WXGTK__, __WXMSW__ and __WXMOTIF__
 yet. Any new ones, please start the define with __WX.
 
 The only GUIs implemented for 2.0 are __WXGTK__, __WXMSW__ and __WXMOTIF__
 yet. Any new ones, please start the define with __WX.
 


@@ -57,6 +59,6 @@ __XLC__         ?? compiler
 wxWindows modes:
 ----------------
 
 wxWindows modes:
 ----------------
 

-__WXDEBUG__       usage: #ifdef __WXDEBUG__ (=> debug mode, else => release)
+__WXDEBUG__     usage: #ifdef __WXDEBUG__ (=> debug mode, else => release)

 WXDEBUG         usage: #if DEBUG (0: release, 1: minimal debug code, ...)
 
 WXDEBUG         usage: #if DEBUG (0: release, 1: minimal debug code, ...)