Many aspects of wxWidgets programming can be learnt from them, but sometimes it is not simple to just choose the right sample to look at. This overview aims at describing what each sample does/demonstrates to make it easier to find the relevant one if a simple grep through all sources didn't help. They also provide some notes about using the samples and what features of wxWidgets are they supposed to test.
There are currently more than 80 different samples as part of wxWidgets: the list in this page is not complete! You should start your tour of wxWidgets with the Minimal Sample which is the wxWidgets version of "Hello, world!". It shows the basic structure of wxWidgets program and is the most commented sample of all - looking at its source code is recommended.
The next most useful samples are probably Widgets Sample and Controls Sample which show many of wxWidgets native and generic controls, such as buttons, listboxes, checkboxes, comboboxes etc.
Other, more complicated controls, have their own samples. In this category you may find the following samples showing the corresponding controls:
Build Note: You may need to build the wxWidgets library with wxUSE_ACCESSIBILITY
being set to 1 to be able to make it work, please read comments in <wx/setup_inc.h>
for more info.
Location: samples/access
Location: samples/animate
Location: samples/artprov
Location: samples/aui
Location: samples/calendar
Location: samples/caret
Location: samples/collpane
Location: samples/combo
See wxConfig Overview for the descriptions of all features of this class.
Location: samples/config
Location: samples/console
The various controls tested are listed here:
Location: samples/controls
Location: samples/dataview
Location: samples/clipboard
For the report processing part of the sample to work you should make available a Web server accepting form uploads, otherwise wxDebugReportUpload will report an error.
Build Note: You may need to build the wxWidgets library with wxUSE_DEBUGREPORT
and wxUSE_ON_FATAL_EXCEPTION
being set to 1 to be able to make it work, please read comments in <wx/setup_inc.h>
for more info.
Location: samples/debugrpt
Location: samples/dialogs
Using the menu entries, you may also dial or hang up the line if you have a modem attached and (this only makes sense for Windows) list the available connections.
Location: samples/dialup
Location: samples/display
When you run the sample, its screen is split in several parts. On the top, there are two listboxes which show the standard derivations of wxDropTarget: wxTextDropTarget and wxFileDropTarget.
The middle of the sample window is taken by the log window which shows what is going on (of course, this only works in debug builds) and may be helpful to see the sequence of steps of data transfer.
Finally, the last part is used for dragging text from it to either one of the listboxes (only one will accept it) or another application. The last functionality available from the main frame is to paste a bitmap from the clipboard (or, in the case of the Windows version, also a metafile) - it will be shown in a new frame.
So far, everything we mentioned was implemented with minimal amount of code using standard wxWidgets classes. The more advanced features are demonstrated if you create a shape frame from the main frame menu. A shape is a geometric object which has a position, size and color. It models some application-specific data in this sample. A shape object supports its own private wxDataFormat which means that you may cut and paste it or drag and drop (between one and the same or different shapes) from one sample instance to another (or the same). However, chances are that no other program supports this format and so shapes can also be rendered as bitmaps which allows them to be pasted/dropped in many other applications (and, under Windows, also as metafiles which are supported by most of Windows programs as well - try Write/Wordpad, for example).
Take a look at DnDShapeDataObject class to see how you may use wxDataObject to achieve this.
Location: samples/dnd
Location: samples/docview
Location: samples/dragimag
Location: samples/drawing
Location: samples/erase
Location: samples/event
Build Note: You need to build the library with wxUSE_EXCEPTIONS
being set to 1
and compile your code with C++ exceptions support to be able to build this sample.
Location: samples/except
It also shows how to capture the output of the child process in both synchronous and asynchronous cases and how to kill the processes with wxProcess::Kill() and test for their existence with wxProcess::Exists().
Location: samples/exec
The sample comes with 2 Flash files (SWF), showing a simple Flash animation which can be controlled using the "Play", "Stop" and "Back"/"Forward" buttons in the sample as well as a Flash form which shows how Flash and wxWidgets program can exchange data: calling "GetText" function without arguments returns the text of the text control defined inside Flash and calling "SetText" with an argument sets the control contents to the given string. Finally clicking on the button generates an event which is caught by the C++ program.
Location: samples/font
Location: samples/grid
Location: samples/help
Location: samples/html
Location: samples/htlbox
At the bottom of the main frame there is a test for using a monochrome bitmap by drawing into a wxMemoryDC. The bitmap is then drawn specifying the foreground and background colours with wxDC::SetTextForeground() and wxDC::SetTextBackground() (on the left). The bitmap is then converted to a wxImage and the foreground colour (black) is replaced with red using wxImage::Replace().
This sample also contains the code for testing the image rotation and resizing and using raw bitmap access, see the corresponding menu commands.
Location: samples/image
More information about this sample can be found in the readme.txt
file in its directory. Please also see the Internationalization.
Location: samples/internat
Location: samples/ipc
Location: samples/joytest
Location: samples/keyboard
The menu in this sample offers two more tests, one showing how to use a wxBoxSizer in a simple dialog and the other one showing how to use sizers in connection with a wxNotebook class. See also wxSizer.
Location: samples/layout
The sample also provides some timings for adding/deleting/sorting a lot of (several thousands) items into the control.
Location: samples/listctrl
Location: samples/mdi
It replaces the old dynamic
sample.
Location: samples/mediaplayer
Location: samples/memcheck
Build Note: You may need to build the wxWidgets library with wxUSE_MEMORY_TRACING
and wxUSE_DEBUG_CONTEXT
being set to 1 to be able to make it work, please read comments in <wx/setup_inc.h>
for more info.
Location: samples/menu
For build instructions please read IMPORTANT NOTES in mfctest.cpp
.
Location: samples/mfc
Location: samples/minimal
Location: samples/nativdlg
Location: samples/notebook
Location: samples/oleauto
Location: samples/opengl
Location: samples/ownerdrw
Location: samples/popup
Location: samples/power
Build Note: You may need to build the wxWidgets library with
wxUSE_PRINTING_ARCHITECTURE
being set to 1 to be able to make it work, please read comments in <wx/setup_inc.h>
for more info.
Location: samples/printing
This sample demonstrates wxPropertyGrid.
Location: samples/propgrid
Location: samples/regtest
Location: samples/render
Location: samples/richtext
Location: samples/sashtest
This sample demonstrates use of the wxScrolledWindow class including placing subwindows into it and drawing simple graphics. It uses the SetTargetWindow method and thus the effect of scrolling does not show in the scrolled window itself, but in one of its subwindows.
Additionally, this samples demonstrates how to optimize drawing operations in wxWidgets, in particular using the wxWindow::IsExposed() method with the aim to prevent unnecessary drawing in the window and thus reducing or removing flicker on screen.
Location: samples/scroll
Location: samples/shaped
The server binds to the local address, using TCP port number 3000, sets up an event handler to be notified of incoming connection requests (wxSOCKET_CONNECTION events), and sits there, waiting for clients (listening, in socket parlance). For each accepted connection, a new wxSocketBase object is created. These socket objects are independent from the server that created them, so they set up their own event handler, and then request to be notified of wxSOCKET_INPUT (incoming data) or wxSOCKET_LOST (connection closed at the remote end) events. In the sample, the event handler is the same for all connections; to find out which socket the event is addressed to, the GetSocket function is used.
Although it might take some time to get used to the event-oriented system upon which wxSocket is built, the benefits are many. See, for example, that the server application, while being single-threaded (and of course without using fork() or ugly select() loops) can handle an arbitrary number of connections.
The client starts up unconnected, so you can use the Connect... option to specify the address of the server you are going to connect to (the TCP port number is hard-coded as 3000). Once connected, a number of tests are possible. Currently, three tests are implemented. They show how to use the basic IO calls in wxSocketBase, such as wxSocketBase::Read(), wxSocketBase::Write(), wxSocketBase::ReadMsg() and wxSocketBase::WriteMsg(), and how to set up the correct IO flags depending on what you are going to do. See the comments in the code for more information. Note that because both clients and connection objects in the server set up an event handler to catch wxSOCKET_LOST events, each one is immediately notified if the other end closes the connection.
There is also a URL test which shows how to use the wxURL class to fetch data from a given URL.
The sockets sample is work in progress. Some things to do:
Location: samples/sockets
sound
sample shows how to use wxSound for simple audio output (e.g. notifications).
Location: samples/sound
Location: samples/splash
Location: samples/splitter
Here you can see how to recreate the statusbar (with possibly different number of fields) and how to use it to show icons/bitmaps and/or put arbitrary controls into it.
Location: samples/statbar
Location: samples/stc
Location: samples/svg
TAB
key, hence the sample name) between different controls. It shows the use of wxWindow::MoveBeforeInTabOrder() and MoveAfterInTabOrder() methods to change the default order of the windows in the navigation chain and of wxWindow::Navigate() for moving focus along this chain.
Location: samples/taborder
Location: samples/taskbar
Secondly it shows how to intercept a wxKeyEvent in both the raw form using the EVT_KEY_UP
and EVT_KEY_DOWN
macros and the higher level from using the EVT_CHAR
macro. All characters will be logged in a log window at the bottom of the main window. By pressing some of the function keys, you can test some actions in the text ctrl as well as get statistics on the text ctrls, which is useful for testing if these statistics actually are correct.
Thirdly, on platforms which support it, the sample will offer to copy text to the wxClipboard and to paste text from it. The GTK version will use the so called PRIMARY SELECTION, which is the pseudo clipboard under X and best known from pasting text to the XTerm program.
Last not least: some of the text controls have tooltips and the sample also shows how tooltips can be centrally disabled and their latency controlled.
Location: samples/text
There are two fundamentally different ways to use threads in GUI programs and either way has to take care of the fact that the GUI library itself usually is not multi-threading safe, i.e. that it might crash if two threads try to access the GUI class simultaneously.
One way to prevent that is have a normal GUI program in the main thread and some worker threads which work in the background. In order to make communication between the main thread and the worker threads possible, wxWidgets offers the wxQueueEvent function and this sample demonstrates its usage.
The other way is to use a wxMutexGuiEnter and wxMutexGuiLeave functions, but this is not currently shown in the sample.
See also Multithreading Overview and wxThread.
Location: samples/thread
The following things are demonstrated:
EVT_UPDATE_UI
handler for automatically enabling/disabling toolbar buttons without having to explicitly call EnableTool. This is done in MyFrame::OnUpdateCopyAndCut().
If you toggle another toolbar in the sample (using Ctrl-A
) you will also see the radio toolbar buttons in action: the first three buttons form a radio group, i.e. checking any of them automatically unchecks the previously checked one.
Location: samples/toolbar
Adding, inserting and deleting items and branches from the tree as well as sorting (in default alphabetical order as well as in custom one) is demonstrated here as well - try the corresponding menu entries.
Location: samples/treectrl
Location: samples/typetest
Location: samples/validate
Location: samples/vscroll
Location: samples/widgets
Location: samples/wizard
Location: samples/wrapsizer
Location: samples/xrc
![]() |
[ top ] |