Don't lie about wxImageList in XRC format spec.
[wxWidgets.git] / docs / doxygen / overviews / bufferclasses.h
1 /////////////////////////////////////////////////////////////////////////////
2 // Name: bufferclasses.h
3 // Purpose: topic overview
4 // Author: wxWidgets team
5 // Licence: wxWindows licence
6 /////////////////////////////////////////////////////////////////////////////
7
8 /**
9
10 @page overview_bufferclasses Buffer Classes
11
12 @tableofcontents
13
14 wxWidgets uses two classes of classes for dealing with buffers in memory.
15
16 The first is one for dealing with character buffers, namely wxCharBuffer for
17 char pointer or multi-byte c strings and wxWCharBuffer for wchar_t pointer or
18 wide character c strings.
19
20 Secondly, wxWidgets uses, although only rarely currently, wxMemoryBuffer for
21 dealing with raw buffers in memory.
22
23
24
25 @section overview_bufferclasses_xcb wxXCharBuffer
26
27 @subsection overview_bufferclasses_xcb_general General Usage
28
29 As mentioned, wxCharBuffer and its wide character variant wxWCharBuffer deal
30 with c strings in memory. They have two constructors, one in which you pass
31 the c string you want them to have a copy of, and another where you specify the
32 size of the buffer in memory in characters you want.
33
34 wxCharBuffer and its variant only contain the c string as a member, so they can
35 be used safely to c functions with variable arguments such as printf. They also
36 contain standard assignment, character access operators and a copy constructor.
37
38 @subsection overview_bufferclasses_xcb_destruct Destruction
39
40 It should be noted that on destruction wxCharBuffer and its wide character
41 variant delete the c string that hold onto. If you want to get the pointer to
42 the buffer and don't want wxCharBuffer to delete it on destruction, use the
43 member function release to do so.
44
45 */