]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/latex/wx/tsamples.tex
Fixed to work with the new wxMacControl system.
[wxWidgets.git] / docs / latex / wx / tsamples.tex
... / ...
CommitLineData
1%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2%% Name: tsamples.tex
3%% Purpose: Samples description
4%% Author: Vadim Zeitlin
5%% Modified by:
6%% Created: 02.11.99
7%% RCS-ID: $Id$
8%% Copyright: (c) wxWidgets team
9%% License: wxWidgets license
10%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
11% NB: please keep the subsections in alphabetic order!
12
13\section{wxWidgets samples}\label{samples}
14
15Probably the best way to learn wxWidgets is by reading the source of some 50+
16samples provided with it. Many aspects of wxWidgets programming can be learnt
17from them, but sometimes it is not simple to just choose the right sample to
18look at. This overview aims at describing what each sample does/demonstrates to
19make it easier to find the relevant one if a simple grep through all sources
20didn't help. They also provide some notes about using the samples and what
21features of wxWidgets are they supposed to test.
22
23There are currently more than 50 different samples as part of wxWidgets and
24this list is not complete. You should start your tour of wxWidgets with the
25\helpref{minimal sample}{sampleminimal} which is the wxWidgets version of
26"Hello, world!". It shows the basic structure of wxWidgets program and is the
27most commented sample of all - looking at its source code is recommended.
28
29The next most useful sample is probably the \helpref{controls}{samplecontrols}
30one which shows many of wxWidgets standard controls, such as buttons,
31listboxes, checkboxes, comboboxes etc.
32
33Other, more complicated controls, have their own samples. In this category you
34may find the following samples showing the corresponding controls:
35
36\begin{twocollist}\itemsep=0pt
37\twocolitem{\helpref{wxCalendarCtrl}{samplecalendar}}{Calendar a.k.a. date picker control}
38\twocolitem{\helpref{wxListCtrl}{samplelistctrl}}{List view control}
39\twocolitem{\helpref{wxTreeCtrl}{sampletreectrl}}{Tree view control}
40\twocolitem{\helpref{wxGrid}{samplegrid}}{Grid control}
41\end{twocollist}
42
43Finally, it might be helpful to do a search in the entire sample directory if
44you can't find the sample you showing the control you are interested in by
45name. Most of wxWidgets classes, occur in at least one of the samples.
46
47
48\subsection{Minimal sample}\label{sampleminimal}
49
50The minimal sample is what most people will know under the term Hello World,
51i.e. a minimal program that doesn't demonstrate anything apart from what is
52needed to write a program that will display a "hello" dialog. This is usually
53a good starting point for learning how to use wxWidgets.
54
55
56\subsection{Art provider sample}\label{sampleartprovider}
57
58The {\tt artprov} sample shows how you can customize the look of standard
59wxWidgets dialogs by replacing default bitmaps/icons with your own versions.
60It also shows how you can use wxArtProvider to
61get stock bitmaps for use in your application.
62
63
64\subsection{Calendar sample}\label{samplecalendar}
65
66This font shows the \helpref{calendar control}{wxcalendarctrl} in action. It
67shows how to configure the control (see the different options in the calendar
68menu) and also how to process the notifications from it.
69
70
71\subsection{Checklist sample}\label{samplechecklist}
72
73This sample demonstrates the use of the \helpref{wxCheckListBox}{wxchecklistbox}
74class intercepting check, select and double click events. It also tests the
75use of various methods modifying the control, such as by deleting items
76from it or inserting new once (these functions are actually implemented in
77the parent class \helpref{wxListBox}{wxlistbox} so the sample tests that class
78as well). The layout of the dialog is created using a \helpref{wxBoxSizer}{wxboxsizer}
79demonstrating a simple dynamic layout.
80
81
82\subsection{Config sample}\label{sampleconfig}
83
84This sample demonstrates the \helpref{wxConfig}{wxconfigbase} classes in a platform
85independent way, i.e. it uses text based files to store a given configuration under
86Unix and uses the Registry under Windows.
87
88See \helpref{wxConfig overview}{wxconfigoverview} for the descriptions of all
89features of this class.
90
91
92\subsection{Controls sample}\label{samplecontrols}
93
94The controls sample is the main test program for most simple controls used in
95wxWidgets. The sample tests their basic functionality, events, placement,
96modification in terms of colour and font as well as the possibility to change
97the controls programmatically, such as adding item to a list box etc. Apart
98from that, the sample uses a \helpref{wxNotebook}{wxnotebook} and tests most
99features of this special control (using bitmap in the tabs, using
100\helpref{wxSizers}{wxsizer} and \helpref{constraints}{wxlayoutconstraints} within
101notebook pages, advancing pages programmatically and vetoing a page change
102by intercepting the \helpref{wxNotebookEvent}{wxnotebookevent}.
103
104The various controls tested are listed here:
105
106\begin{twocollist}\itemsep=0pt
107\twocolitem{\helpref{wxButton}{wxbutton}}{Push button control, displaying text}
108\twocolitem{\helpref{wxBitmapButton}{wxbitmapbutton}}{Push button control, displaying a bitmap}
109\twocolitem{\helpref{wxCheckBox}{wxcheckbox}}{Checkbox control}
110\twocolitem{\helpref{wxChoice}{wxchoice}}{Choice control (a combobox without the editable area)}
111\twocolitem{\helpref{wxComboBox}{wxcombobox}}{A choice with an editable area}
112\twocolitem{\helpref{wxGauge}{wxgauge}}{A control to represent a varying quantity, such as time remaining}
113\twocolitem{\helpref{wxStaticBox}{wxstaticbox}}{A static, or group box for visually grouping related controls}
114\twocolitem{\helpref{wxListBox}{wxlistbox}}{A list of strings for single or multiple selection}
115\twocolitem{wxSpinCtrl}{A spin ctrl with a text field and a `up-down' control}
116\twocolitem{\helpref{wxSpinButton}{wxspinbutton}}{A spin or `up-down' control}
117\twocolitem{\helpref{wxStaticText}{wxstatictext}}{One or more lines of non-editable text}
118\twocolitem{\helpref{wxStaticBitmap}{wxstaticbitmap}}{A control to display a bitmap}
119\twocolitem{\helpref{wxRadioBox}{wxradiobox}}{A group of radio buttons}
120\twocolitem{\helpref{wxRadioButton}{wxradiobutton}}{A round button to be used with others in a mutually exclusive way}
121\twocolitem{\helpref{wxSlider}{wxslider}}{A slider that can be dragged by the user}
122\end{twocollist}
123
124
125\subsection{Database sample}\label{sampledb}
126
127The database sample is a small test program showing how to use the ODBC
128classes written by Remstar Intl. Obviously, this sample requires a
129database with ODBC support to be correctly installed on your system.
130
131
132\subsection{Dialogs sample}\label{sampledialogs}
133
134This sample shows how to use the common dialogs available from wxWidgets. These
135dialogs are described in details in the \helpref{Common dialogs overview}{commondialogsoverview}.
136
137
138\subsection{Dialup sample}\label{sampledialup}
139
140This sample shows \helpref{wxDialUpManager}{wxdialupmanager}
141class. It displays in the status bar the information gathered through its
142interface: in particular, the current connection status (online or offline) and
143whether the connection is permanent (in which case a string `LAN' appears in
144the third status bar field - but note that you may have be on a LAN not
145connected to the Internet, in which case you will not see this) or not.
146
147Using the menu entries, you may also dial or hang up the line if you have a
148modem attached and (this only makes sense for Windows) list the available
149connections.
150
151
152\subsection{DnD sample}\label{samplednd}
153
154This sample shows both clipboard and drag and drop in action. It is quite non
155trivial and may be safely used as a basis for implementing the clipboard and
156drag and drop operations in a real-life program.
157
158When you run the sample, its screen is split in several parts. On the top,
159there are two listboxes which show the standard derivations of
160\helpref{wxDropTarget}{wxdroptarget}:
161\helpref{wxTextDropTarget}{wxtextdroptarget} and
162\helpref{wxFileDropTarget}{wxfiledroptarget}.
163
164The middle of the sample window is taken by the log window which shows what is
165going on (of course, this only works in debug builds) and may be helpful to see
166the sequence of steps of data transfer.
167
168Finally, the last part is used for dragging text from it to either one of the
169listboxes (only one will accept it) or another application. The last
170functionality available from the main frame is to paste a bitmap from the
171clipboard (or, in the case of Windows version, also a metafile) - it will be
172shown in a new frame.
173
174So far, everything we mentioned was implemented with minimal amount of code
175using standard wxWidgets classes. The more advanced features are demonstrated
176if you create a shape frame from the main frame menu. A shape is a geometric
177object which has a position, size and color. It models some
178application-specific data in this sample. A shape object supports its own
179private \helpref{wxDataFormat}{wxdataformat} which means that you may cut and
180paste it or drag and drop (between one and the same or different shapes) from
181one sample instance to another (or the same). However, chances are that no
182other program supports this format and so shapes can also be rendered as
183bitmaps which allows them to be pasted/dropped in many other applications
184(and, under Windows, also as metafiles which are supported by most of Windows
185programs as well - try Write/Wordpad, for example).
186
187Take a look at DnDShapeDataObject class to see how you may use
188\helpref{wxDataObject}{wxdataobject} to achieve this.
189
190
191\subsection{Dynamic sample}\label{sampledynamic}
192
193This sample is a very small sample that demonstrates the use of the
194\helpref{wxEvtHandler::Connect}{wxevthandlerconnect} method. This method
195should be used whenever it is not known at compile time, which control
196will receive which event or which controls are actually going to be in
197a dialog or frame. This is most typically the case for any scripting
198language that would work as a wrapper for wxWidgets or programs where
199forms or similar datagrams can be created by the uses.
200
201See also the \helpref{event sample}{sampleevent}
202
203
204\subsection{Event sample}\label{sampleevent}
205
206The event sample demonstrates various features of the wxWidgets events. It
207shows using dynamic events and connecting/disconnecting the event handlers
208during the run time and also using
209\helpref{PushEventHandler()}{wxwindowpusheventhandler} and
210\helpref{PopEventHandler()}{wxwindowpopeventhandler}.
211
212It replaces the old dynamic sample.
213
214
215\subsection{Except(ions) sample}\label{sampleexcept}
216
217This very simple sample shows how to use C++ exceptions in wxWidgets programs,
218i.e. where to catch the exception which may be thrown by the program code. It
219doesn't do anything very exciting by itself, you need to study its code to
220understand what goes on.
221
222You need to build the library with \texttt{wxUSE\_EXCEPTIONS} being set to $1$
223and compile your code with the C++ exceptions support to be able to build this
224sample.
225
226
227\subsection{Exec sample}\label{sampleexec}
228
229The exec sample demonstrates the \helpref{wxExecute}{wxexecute} and
230\helpref{wxShell}{wxshell} functions. Both of them are used to execute the
231external programs and the sample shows how to do this synchronously (waiting
232until the program terminates) or asynchronously (notification will come later).
233
234It also shows how to capture the output of the child process in both
235synchronous and asynchronous cases and how to kill the processes with
236\helpref{wxProcess::Kill}{wxprocesskill} and test for their existence with
237\helpref{wxProcess::Exists}{wxprocessexists}.
238
239
240\subsection{Font sample}\label{samplefont}
241
242The font sample demonstrates \helpref{wxFont}{wxfont},
243\helpref{wxFontEnumerator}{wxfontenumerator} and
244\helpref{wxFontMapper}{wxfontmapper} classes. It allows you to see the fonts
245available (to wxWidgets) on the computer and shows all characters of the
246chosen font as well.
247
248
249\subsection{Grid sample}\label{samplegrid}
250
251TODO.
252
253
254\subsection{HTML samples}\label{samplehtml}
255
256Eight HTML samples (you can find them in directory {\tt samples/html})
257cover all features of HTML sub-library.
258
259{\bf Test} demonstrates how to create \helpref{wxHtmlWindow}{wxhtmlwindow}
260and also shows most of supported HTML tags.
261
262{\bf Widget} shows how you can embed ordinary controls or windows within
263HTML page. It also nicely explains how to write new tag handlers and extend
264the library to work with unsupported tags.
265
266{\bf About} may give you an idea how to write good-looking about boxes.
267
268{\bf Zip} demonstrates use of virtual file systems in wxHTML. The zip archives
269handler (ships with wxWidgets) allows you to access HTML pages stored
270in compressed archive as if they were ordinary files.
271
272{\bf Virtual} is yet another virtual file systems demo. This one generates pages at run-time.
273You may find it useful if you need to display some reports in your application.
274
275{\bf Printing} explains use of \helpref{wxHtmlEasyPrinting}{wxhtmleasyprinting}
276class which serves as as-simple-as-possible interface for printing HTML
277documents without much work. In fact, only few function calls are sufficient.
278
279{\bf Help} and {\bf Helpview} are variations on displaying HTML help
280(compatible with MS HTML Help Workshop). {\it Help} shows how to embed
281\helpref{wxHtmlHelpController}{wxhtmlhelpcontroller} in your application
282while {\it Helpview} is simple tool that only pops up help window and
283displays help books given at command line.
284
285
286\subsection{Image sample}\label{sampleimage}
287
288The image sample demonstrates the use of the \helpref{wxImage}{wximage} class
289and shows how to download images in a variety of formats, currently PNG, GIF,
290TIFF, JPEG, BMP, PNM and PCX. The top of the sample shows to rectangles, one
291of which is drawn directly in the window, the other one is drawn into a
292\helpref{wxBitmap}{wxbitmap}, converted to a wxImage, saved as a PNG image
293and then reloaded from the PNG file again so that conversions between wxImage
294and wxBitmap as well as loading and save PNG files are tested.
295
296At the bottom of the main frame is a test for using a monochrome bitmap by
297drawing into a \helpref{wxMemoryDC}{wxmemorydc}. The bitmap is then drawn
298specifying the foreground and background colours with
299\helpref{wxDC::SetTextForeground}{wxdcsettextforeground} and
300\helpref{wxDC::SetTextBackground}{wxdcsettextbackground} (on the left). The
301bitmap is then converted to a wxImage and the foreground colour (black) is
302replaced with red using \helpref{wxImage::Replace}{wximagereplace}.
303
304
305\subsection{Internat(ionalization) sample}\label{sampleinternat}
306
307The not very clearly named internat sample demonstrates the wxWidgets
308internatationalization (i18n for short from now on) features. To be more
309precise, it only shows localization support, i.e. support for translating the
310program messages in another language while true i18n would also involve
311changing the other aspects of the programs behaviour.
312
313More information about this sample can be found in the {\tt readme.txt} file in
314its directory. Please see also \helpref{i18n overview}{internationalization}.
315
316
317\subsection{Layout sample}\label{samplelayout}
318
319The layout sample demonstrates the two different layout systems offered
320by wxWidgets. When starting the program, you will see a frame with some
321controls and some graphics. The controls will change their size whenever
322you resize the entire frame and the exact behaviour of the size changes
323is determined using the \helpref{wxLayoutConstraints}{wxlayoutconstraints}
324class. See also the \helpref{overview}{constraintsoverview} and the
325\helpref{wxIndividualLayoutConstraint}{wxindividuallayoutconstraint}
326class for further information.
327
328The menu in this sample offers two more tests, one showing how to use
329a \helpref{wxBoxSizer}{wxboxsizer} in a simple dialog and the other one
330showing how to use sizers in connection with a \helpref{wxNotebook}{wxnotebook}
331class. See also \helpref{wxNotebookSizer}{wxnotebooksizer} and
332\helpref{wxSizer}{wxsizer}.
333
334
335\subsection{Listctrl sample}\label{samplelistctrl}
336
337This sample shows \helpref{wxListCtrl}{wxlistctrl} control. Different modes
338supported by the control (list, icons, small icons, report) may be chosen from
339the menu.
340
341The sample also provides some timings for adding/deleting/sorting a lot of
342(several thousands) items into the control.
343
344
345
346\subsection{Notebook sample}\label{samplenotebook}
347
348This samples shows two controls at once: although initially it was written to
349demonstrate \helpref{wxNotebook}{wxnotebook} only, it can now be also used
350to see \helpref{wxListbook}{wxlistbook} in action. To switch between the two
351controls you need to manually change \texttt{TEST\_LISTBOOK} definition in the
352file \texttt{notebook.h} and rebuild the sample.
353
354
355
356\subsection{Render sample}\label{samplerender}
357
358This sample shows how to replace the default wxWidgets
359\helpref{renderer}{wxrenderernative} and also how to write a shared library
360(DLL) implementing a renderer and load and unload it during the run-time.
361
362
363
364\subsection{Rotate sample}\label{samplerotate}
365
366This is a simple example which demonstrates how to rotate an image with
367the \helpref{wxImage::Rotate}{wximagerotate} method. The rotation can
368be done without interpolation (left mouse button) which will be faster,
369or with interpolation (right mouse button) which is slower but gives
370better results.
371
372
373\subsection{Scroll subwindow sample}\label{samplescrollsub}
374
375This sample demonstrates the use of the \helpref{wxScrolledWindow}{wxscrolledwindow}
376class including placing subwindows into it and drawing simple graphics. It uses the
377\helpref{SetTargetWindow}{wxscrolledwindowsettargetwindow} method and thus the effect
378of scrolling does not show in the scrolled window itself, but in one of its subwindows.
379
380Additionally, this samples demonstrates how to optimize drawing operations in wxWidgets,
381in particular using the \helpref{wxWindow::IsExposed}{wxwindowisexposed} method with
382the aim to prevent unnecessary drawing in the window and thus reducing or removing
383flicker on screen.
384
385
386\subsection{Sockets sample}\label{samplesockets}
387
388The sockets sample demonstrates how to use the communication facilities
389provided by \helpref{wxSocket}{wxsocketbase}. There are two different
390applications in this sample: a server, which is implemented using a
391\helpref{wxSocketServer}{wxsocketserver} object, and a client, which
392is implemented as a \helpref{wxSocketClient}{wxsocketclient}.
393
394The server binds to the local address, using TCP port number 3000,
395sets up an event handler to be notified of incoming connection requests
396({\bf wxSOCKET\_CONNECTION} events), and stands there, waiting for clients
397({\it listening} in the socket parlance). For each accepted connection,
398a new \helpref{wxSocketBase}{wxsocketbase} object is created. These
399socket objects are independent from the server that created them, so
400they set up their own event handler, and then request to be notified
401of {\bf wxSOCKET\_INPUT} (incoming data) or {\bf wxSOCKET\_LOST}
402(connection closed at the remote end) events. In the sample, the event
403handler is the same for all connections; to find out which socket the
404event is addressed to, the \helpref{GetSocket}{wxsocketeventgetsocket} function
405is used.
406
407Although it might take some time to get used to the event-oriented
408system upon which wxSocket is built, the benefits are many. See, for
409example, that the server application, while being single-threaded
410(and of course without using fork() or ugly select() loops) can handle
411an arbitrary number of connections.
412
413The client starts up unconnected, so you can use the Connect... option
414to specify the address of the server you are going to connect to (the
415TCP port number is hard-coded as 3000). Once connected, a number of
416tests are possible. Currently, three tests are implemented. They show
417how to use the basic IO calls in \helpref{wxSocketBase}{wxsocketbase},
418such as \helpref{Read}{wxsocketbaseread}, \helpref{Write}{wxsocketbasewrite},
419\helpref{ReadMsg}{wxsocketbasereadmsg} and \helpref{WriteMsg}{wxsocketbasewritemsg},
420and how to set up the correct IO flags depending on what you are going to
421do. See the comments in the code for more information. Note that because
422both clients and connection objects in the server set up an event handler
423to catch {\bf wxSOCKET\_LOST} events, each one is immediately notified
424if the other end closes the connection.
425
426There is also an URL test which shows how to use
427the \helpref{wxURL}{wxurl} class to fetch data from a given URL.
428
429The sockets sample is work in progress. Some things to do:
430
431\begin{itemize}\itemsep=0pt
432\item More tests for basic socket functionality.
433\item More tests for protocol classes (wxProtocol and its descendants).
434\item Tests for the recently added (and still in alpha stage) datagram sockets.
435\item New samples which actually do something useful (suggestions accepted).
436\end{itemize}
437
438
439\subsection{Sound sample}\label{samplesound}
440
441The {\tt sound} sample shows how to use \helpref{wxSound}{wxsound} for simple
442audio output (e.g. notifications).
443
444
445\subsection{Statbar sample}\label{samplestatbar}
446
447This sample shows how to create and use wxStatusBar. Although most of the
448samples have a statusbar, they usually only create a default one and only
449do it once.
450
451Here you can see how to recreate the statusbar (with possibly different number
452of fields) and how to use it to show icons/bitmaps and/or put arbitrary
453controls into it.
454
455
456\subsection{Text sample}\label{sampletext}
457
458This sample demonstrates four features: firstly the use and many variants of
459the \helpref{wxTextCtrl}{wxtextctrl} class (single line, multi line, read only,
460password, ignoring TAB, ignoring ENTER).
461
462Secondly it shows how to intercept a \helpref{wxKeyEvent}{wxkeyevent} in both
463the raw form using the {\tt EVT\_KEY\_UP} and {\tt EVT\_KEY\_DOWN} macros and the
464higher level from using the {\tt EVT\_CHAR} macro. All characters will be logged
465in a log window at the bottom of the main window. By pressing some of the function
466keys, you can test some actions in the text ctrl as well as get statistics on the
467text ctrls, which is useful for testing if these statistics actually are correct.
468
469Thirdly, on platforms which support it, the sample will offer to copy text to the
470\helpref{wxClipboard}{wxclipboard} and to paste text from it. The GTK version will
471use the so called PRIMARY SELECTION, which is the pseudo clipboard under X and
472best known from pasting text to the XTerm program.
473
474Last not least: some of the text controls have tooltips and the sample also shows
475how tooltips can be centrally disabled and their latency controlled.
476
477
478\subsection{Thread sample}\label{samplethread}
479
480This sample demonstrates the use of threads in connection with GUI programs.
481There are two fundamentally different ways to use threads in GUI programs and
482either way has to take care of the fact that the GUI library itself usually
483is not multi-threading safe, i.e. that it might crash if two threads try to
484access the GUI class simultaneously. One way to prevent that is have a normal
485GUI program in the main thread and some worker threads which work in the
486background. In order to make communication between the main thread and the
487worker threads possible, wxWidgets offers the \helpref{wxPostEvent}{wxpostevent}
488function and this sample makes use of this function.
489
490The other way to use a so called Mutex (such as those offered in the \helpref{wxMutex}{wxmutex}
491class) that prevent threads from accessing the GUI classes as long as any other
492thread accesses them. For this, wxWidgets has the \helpref{wxMutexGuiEnter}{wxmutexguienter}
493and \helpref{wxMutexGuiLeave}{wxmutexguileave} functions, both of which are
494used and tested in the sample as well.
495
496See also \helpref{Multithreading overview}{wxthreadoverview} and \helpref{wxThread}{wxthread}.
497
498
499\subsection{Toolbar sample}\label{sampletoolbar}
500
501The toolbar sample shows the \helpref{wxToolBar}{wxtoolbar} class in action.
502
503The following things are demonstrated:
504
505\begin{itemize}\itemsep=0pt
506\item Creating the toolbar using \helpref{wxToolBar::AddTool}{wxtoolbaraddtool}
507and \helpref{wxToolBar::AddControl}{wxtoolbaraddcontrol}: see
508MyApp::InitToolbar in the sample.
509\item Using {\tt EVT\_UPDATE\_UI} handler for automatically enabling/disabling
510toolbar buttons without having to explicitly call EnableTool. This is done
511in MyFrame::OnUpdateCopyAndCut.
512\item Using \helpref{wxToolBar::DeleteTool}{wxtoolbardeletetool} and
513\helpref{wxToolBar::InsertTool}{wxtoolbarinserttool} to dynamically update the
514toolbar.
515\end{itemize}
516
517Some buttons in the main toolbar are check buttons, i.e. they stay checked when
518pressed. On the platforms which support it, the sample also add a combobox
519to the toolbar showing how you can use arbitrary controls and not only buttons
520in it.
521
522If you toggle another toolbar in the sample (using {\tt Ctrl-A}) you will also
523see the radio toolbar buttons in action: the first three buttons form a radio
524group, that is checking any of them automatically unchecks the previously
525checked one.
526
527
528\subsection{Treectrl sample}\label{sampletreectrl}
529
530This sample demonstrates using \helpref{wxTreeCtrl}{wxtreectrl} class. Here
531you may see how to process various notification messages sent by this control
532and also when they occur (by looking at the messages in the text control in
533the bottom part of the frame).
534
535Adding, inserting and deleting items and branches from the tree as well as
536sorting (in default alphabetical order as well as in custom one) is
537demonstrated here as well - try the corresponding menu entries.
538
539
540\subsection{Wizard sample}\label{samplewizard}
541
542This sample shows so-called wizard dialog (implemented using
543\helpref{wxWizard}{wxwizard} and related classes). It shows almost all
544features supported:
545
546\begin{itemize}\itemsep=0pt
547\item Using bitmaps with the wizard and changing them depending on the page
548shown (notice that wxValidationPage in the sample has a different image from
549the other ones)
550\item Using \helpref{TransferDataFromWindow}{wxwindowtransferdatafromwindow}
551to verify that the data entered is correct before passing to the next page
552(done in wxValidationPage which forces the user to check a checkbox before
553continuing).
554\item Using more elaborated techniques to allow returning to the previous
555page, but not continuing to the next one or vice versa (in wxRadioboxPage)
556\item This (wxRadioboxPage) page also shows how the page may process {\tt
557Cancel} button itself instead of relying on the wizard parent to do it.
558\item Normally, the order of the pages in the wizard is known at compile-time,
559but sometimes it depends on the user choices: wxCheckboxPage shows how to
560dynamically decide which page to display next (see also
561\helpref{wxWizardPage}{wxwizardpage})
562\end{itemize}
563