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