Remove all trailing spaces

No real changes, just clean up sources by removing trailing spaces from
all the non-generated files.

This should hopefully avoid future commits mixing significant changes
with insignificant whitespace ones.

docs/doxygen/overviews/debugging.h

@@ -21,7 +21,7 @@ debugging. Both assertions and debug logging are also used by wxWidgets itself
 so you may encounter them even if you don't use either of these features
 yourself.
 
-@see wxLog, @ref group_funcmacro_log, @ref group_funcmacro_debug 
+@see wxLog, @ref group_funcmacro_log, @ref group_funcmacro_debug
 
 
 

docs/doxygen/overviews/docview.h

@@ -86,7 +86,7 @@ use Wx ':docview';   # import constants (optional)
 @endcode
 @endWxPerlOnly
 
-@see @ref group_class_docview, 
+@see @ref group_class_docview,
 
 
 

docs/doxygen/overviews/eventhandling.h

@@ -614,7 +614,7 @@ custom event types.
 Finally, you will need to generate and post your custom events.
 Generation is as simple as instancing your custom event class and initializing
 its internal fields.
-For posting events to a certain event handler there are two possibilities: 
+For posting events to a certain event handler there are two possibilities:
 using wxEvtHandler::AddPendingEvent or using wxEvtHandler::QueueEvent.
 Basically you will need to use the latter when doing inter-thread communication;
 when you use only the main thread you can also safely use the former.

docs/doxygen/overviews/log.h

@@ -19,9 +19,9 @@ as well as several standard implementations of it and a family of functions to
 use with them.
 
 First of all, no knowledge of wxLog classes is needed to use them. For this,
-you should only know about @ref group_funcmacro_log "wxLogXXX() functions". 
-All of them have the same syntax as @e printf() or @e vprintf() , i.e. they 
-take the format string as the first argument and respectively a variable number 
+you should only know about @ref group_funcmacro_log "wxLogXXX() functions".
+All of them have the same syntax as @e printf() or @e vprintf() , i.e. they
+take the format string as the first argument and respectively a variable number
 of arguments or a variable argument list pointer. Here are all of them:
 
 @li wxLogFatalError() which is like wxLogError(), but also terminates the program
@@ -161,8 +161,8 @@ works.
 wxWidgets has the notion of a <em>log target</em>: it is just a class deriving
 from wxLog. As such, it implements the virtual functions of the base class
 which are called when a message is logged. Only one log target is @e active at
-any moment, this is the one used by @ref group_funcmacro_log "wxLogXXX() functions". 
-The normal usage of a log object (i.e. object of a class derived from wxLog) is 
+any moment, this is the one used by @ref group_funcmacro_log "wxLogXXX() functions".
+The normal usage of a log object (i.e. object of a class derived from wxLog) is
 to install it as the active target with a call to @e SetActiveTarget() and it
 will be used automatically by all subsequent calls to
 @ref group_funcmacro_log "wxLogXXX() functions".
@@ -263,7 +263,7 @@ GUI is (already/still) available when your log target as used as wxWidgets
 automatically switches to using wxLogStderr if it isn't.
 
 There are several methods which may be overridden in the derived class to
-customize log messages handling: wxLog::DoLogRecord(), wxLog::DoLogTextAtLevel() 
+customize log messages handling: wxLog::DoLogRecord(), wxLog::DoLogTextAtLevel()
 and wxLog::DoLogText().
 
 The last method is the simplest one: you should override it if you simply

docs/doxygen/overviews/propgrid.h

@@ -733,10 +733,10 @@ accomplish the task:
 @code
     // Have property editor focus on Enter
     propgrid->AddActionTrigger( wxPG_ACTION_EDIT, WXK_RETURN );
-    
+
     // Have Enter work as action trigger even when editor is focused
     propgrid->DedicateKey( WXK_RETURN );
-    
+
     // Let Enter also navigate to the next property
     propgrid->AddActionTrigger( wxPG_ACTION_NEXT_PROPERTY, WXK_RETURN );
 

docs/doxygen/overviews/sizer.h

@@ -15,7 +15,7 @@ Sizers, as represented by the wxSizer class and its descendants in the
 wxWidgets class hierarchy, have become the method of choice to define the
 layout of controls in dialogs in wxWidgets because of their ability to create
 visually appealing dialogs independent of the platform, taking into account
-the differences in size and style of the individual controls. 
+the differences in size and style of the individual controls.
 
 The next section describes and shows what can be done with sizers. The
 following sections briefly describe how to program with individual sizer
@@ -211,7 +211,7 @@ window will preserve it is original size, @c wxGROW flag (same as @c wxEXPAND) f
 the window to grow with the sizer, and @c wxSHAPED flag tells the window to change
 it is size proportionally, preserving original aspect ratio.  When @c wxGROW flag
 is not used, the item can be aligned within available space.  @c wxALIGN_LEFT,
-@c wxALIGN_TOP, @c wxALIGN_RIGHT, @c wxALIGN_BOTTOM, @c wxALIGN_CENTER_HORIZONTAL 
+@c wxALIGN_TOP, @c wxALIGN_RIGHT, @c wxALIGN_BOTTOM, @c wxALIGN_CENTER_HORIZONTAL
 and @c wxALIGN_CENTER_VERTICAL do what they say. @c wxALIGN_CENTRE (same as
 @c wxALIGN_CENTER) is defined as (<tt>wxALIGN_CENTER_HORIZONTAL | wxALIGN_CENTER_VERTICAL</tt>).
  Default alignment is <tt>wxALIGN_LEFT | wxALIGN_TOP</tt>.
@@ -267,7 +267,7 @@ MyDialog::MyDialog(wxFrame *parent, wxWindowID id, const wxString &title )
 }
 @endcode
 
-Note that the recommended way of specifying flags to wxSizer is via wxSizerFlags. 
+Note that the recommended way of specifying flags to wxSizer is via wxSizerFlags.
 This class greatly eases the burden of passing flags to a wxSizer.
 
 Here's how you'd do the previous example with wxSizerFlags:
@@ -313,18 +313,18 @@ MyDialog::MyDialog(wxFrame *parent, wxWindowID id, const wxString &title )
 
 @section overview_sizer_types Other Types of Sizers
 
-wxStdDialogButtonSizer is a sizer that creates button layouts in dialogs 
-which conform to the standard button spacing and ordering defined by 
+wxStdDialogButtonSizer is a sizer that creates button layouts in dialogs
+which conform to the standard button spacing and ordering defined by
 the platform or toolkit's user interface guidelines (if such things exist).
 As a convenience, wxDialog::CreateButtonSizer() can be used to create this sizer.
 
-wxWrapSizer is a sizer that lays out its items in a single line, like a box 
-sizer -- as long as there is space available in that direction. Once all available 
-space in the primary direction has been used, a new line is added and items 
-are added there. 
+wxWrapSizer is a sizer that lays out its items in a single line, like a box
+sizer -- as long as there is space available in that direction. Once all available
+space in the primary direction has been used, a new line is added and items
+are added there.
 
 wxGridBagSizer is a rather special kind of sizer which, unlike the other
 classes, allows to directly put the elements at the given position in the
-sizer. 
+sizer.
 
 */