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

another batch of topic overviews reviewing (letters e,f)

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@52022 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Francesco Montorsi
2008-02-24 00:47:29 +00:00
parent f3b2b3e920
commit 3b88355f59
8 changed files with 333 additions and 810 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/doxygen/overviews/bufferclasses.h
View File

@@ -19,15 +19,16 @@
Secondly, wxWidgets uses, although only rarely currently, wxMemoryBuffer
for dealing with raw buffers in memory.
@li @ref overview_bufferclasses_wxcb
@li @ref overview_bufferclasses_xcb
<hr>
@section overview_bufferclasses_wxcb wxXCharBuffer Overview
@section overview_bufferclasses_xcb wxXCharBuffer Overview
@subsection overview_bufferclasses_xcb_general General Usage
@b General Usage
As mentioned, wxCharBuffer and its wide character variant wxWCharBuffer deal
with c strings in memory. They have two constructors, one in which you pass
the c string you want them to have a copy of, and another where you specify
@@ -37,7 +38,8 @@
can be used safely to c functions with variable arguments such as printf.
They also contain standard assignment, character access operators and a copy constructor.
@b Destruction
@subsection overview_bufferclasses_xcb_destruct Destruction
It should be noted that on destruction wxCharBuffer and its wide character
variant delete the c string that hold onto. If you want to get the pointer
to the buffer and don't want wxCharBuffer to delete it on destruction,