Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

removed useless spaces

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@51911 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Francesco Montorsi
2008-02-19 13:28:24 +00:00
parent 4411a6b6b5
commit 36c9828f70
71 changed files with 5417 additions and 5409 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/doxygen/overviews/backwardcompatibility.h
View File

@@ -119,7 +119,8 @@
been supported by wxGTK for UNIX-like platforms. been supported by wxGTK for UNIX-like platforms.
Another practical consideration is that for binary compatibility to work, Another practical consideration is that for binary compatibility to work,
all the applications and libraries must have been compiled with compilers all the applications and libraries must have been compiled with compilers
that are capable of producing compatible code; that is, they must use the that are capable of producing compatible code;
that is, they must use the
same ABI (Application Binary Interface). Unfortunately most different C++ same ABI (Application Binary Interface). Unfortunately most different C++
compilers do not produce code compatible with each other, and often even compilers do not produce code compatible with each other, and often even
different versions of the same compiler are not compatible. different versions of the same compiler are not compatible.
@@ -134,7 +135,8 @@
application packages that will work with all binary compatible versions of application packages that will work with all binary compatible versions of
the shared library starting with, for example @c 2.6.0. the shared library starting with, for example @c 2.6.0.
To do this the developer must, of course, avoid any features not available To do this the developer must, of course, avoid any features not available
in the earlier versions. However this is not necessarily enough; in some in the earlier versions. However this is not necessarily enough;
in some
cases an application compiled with a later version may depend on it even cases an application compiled with a later version may depend on it even
though the same code would compile fine against an earlier version. though the same code would compile fine against an earlier version.
To help with this, a preprocessor symbol @c wxABI_VERSION can be defined To help with this, a preprocessor symbol @c wxABI_VERSION can be defined

6
docs/doxygen/overviews/dnd.h
View File

@@ -59,8 +59,10 @@
switch (result) switch (result)
{ {
case wxDragCopy: /* copy the data */ break; case wxDragCopy: /* copy the data */ break;
case wxDragMove: /* move the data */ break; case wxDragMove: /* move the data */
default: /* do nothing */ break; break;
default: /* do nothing */
break;
} }
@endcode @endcode

4
docs/doxygen/overviews/log.h
View File

@@ -24,6 +24,8 @@
#wxLogNull, #wxLogNull,
#wxLogBuffer,
#wxLogChain, #wxLogChain,
#wxLogInterposer, #wxLogInterposer,
@@ -155,6 +157,8 @@
collects all messages generated by the application and also passes them to the collects all messages generated by the application and also passes them to the
previous active log target. The log window frame has a menu allowing user to previous active log target. The log window frame has a menu allowing user to
clear the log, close it completely or save all messages to file. clear the log, close it completely or save all messages to file.
@b wxLogBuffer This target collects all the logged messages in an
internal buffer allowing to show them later to the user all at once.
@b wxLogNull The last log class is quite particular: it doesn't do @b wxLogNull The last log class is quite particular: it doesn't do
anything. The objects of this class may be instantiated to (temporarily) anything. The objects of this class may be instantiated to (temporarily)
suppress output of @e wxLogXXX() functions. As an example, trying to open a suppress output of @e wxLogXXX() functions. As an example, trying to open a