Fix problem with COMDLG_FILTERSPEC declaration with MinGW-w64 4.8.

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

diff --git a/docs/doxygen/overviews/bufferclasses.h b/docs/doxygen/overviews/bufferclasses.h
index f8727c6727c4165f3aa1b030a06105d70c559ab6..0d506d6920a5c1c443b2e79454a1be1354d2dc40 100644 (file)
--- a/docs/doxygen/overviews/bufferclasses.h
+++ b/docs/doxygen/overviews/bufferclasses.h
@@ -2,7 +2,6 @@
 // Name:        bufferclasses.h
 // Purpose:     topic overview
 // Author:      wxWidgets team
 // Name:        bufferclasses.h
 // Purpose:     topic overview
 // Author:      wxWidgets team

-// RCS-ID:      $Id$

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


@@ -10,6 +9,8 @@
 
 @page overview_bufferclasses Buffer Classes
 
 
 @page overview_bufferclasses Buffer Classes
 

+@tableofcontents
+

 wxWidgets uses two classes of classes for dealing with buffers in memory.
 
 The first is one for dealing with character buffers, namely wxCharBuffer for
 wxWidgets uses two classes of classes for dealing with buffers in memory.
 
 The first is one for dealing with character buffers, namely wxCharBuffer for


@@ -19,10 +20,6 @@ wide character c strings.
 Secondly, wxWidgets uses, although only rarely currently, wxMemoryBuffer for
 dealing with raw buffers in memory.
 
 Secondly, wxWidgets uses, although only rarely currently, wxMemoryBuffer for
 dealing with raw buffers in memory.
 

-@li @ref overview_bufferclasses_xcb
-
-
-<hr>

 
 
 @section overview_bufferclasses_xcb wxXCharBuffer
 
 
 @section overview_bufferclasses_xcb wxXCharBuffer


@@ -46,4 +43,3 @@ the buffer and don't want wxCharBuffer to delete it on destruction, use the
 member function release to do so.
 
 */
 member function release to do so.
 
 */

-