1999-11-02 22:47:19 +00:00
|
|
|
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
|
|
|
%% Name: tsamples.tex
|
|
|
|
%% Purpose: Samples description
|
|
|
|
%% Author: Vadim Zeitlin
|
|
|
|
%% Modified by:
|
|
|
|
%% Created: 02.11.99
|
|
|
|
%% RCS-ID: $Id$
|
|
|
|
%% Copyright: (c) wxWindows team
|
|
|
|
%% Licence: wxWindows licence
|
|
|
|
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
|
|
|
|
|
|
|
\section{wxWindows samples}\label{samples}
|
|
|
|
|
|
|
|
Probably the best way to learn wxWindows is by reading the source of some 50+
|
|
|
|
samples provided with it. Many aspects of wxWindows 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 wxWindows are they supposed to test.
|
|
|
|
|
2000-01-02 18:13:45 +00:00
|
|
|
\subsection{Checklist sample}\label{samplechecklist}
|
|
|
|
|
|
|
|
This sample demonstrates the use of the \helpref{wxCheckListBox}{wxchecklistbox}
|
|
|
|
class intercepting check, select and double click events. It also tests the
|
|
|
|
use of various methods modifiying the control, such as by deleting items
|
|
|
|
from it or inserting new once (these fucntions are actually implememted in
|
|
|
|
the parent class \helpref{wxListBox}{wxlistbox} so the sample tests that class
|
|
|
|
as well). The layout of the dialog is created using a \helpref{wxBoxSizer}{wxboxsizer}
|
|
|
|
demonstrating a simple dynamic layout.
|
|
|
|
|
|
|
|
\subsection{Config sample}\label{sampleconfig}
|
|
|
|
|
|
|
|
This sample demonstrates the \helpref{wxConfig}{wxconfigbase} classes in a platform
|
|
|
|
indepedent way, i.e. it uses text based files to store a given configuration under
|
|
|
|
Unix and uses the Registry under Windows.
|
|
|
|
|
|
|
|
See \helpref{wxConfig overview}{wxconfigoverview} for the descriptions of all
|
|
|
|
features of this class.
|
|
|
|
|
|
|
|
\subsection{Dialogs sample}\label{sampledialogs}
|
|
|
|
|
|
|
|
This sample shows how to use the common dialogs available from wxWindows. These
|
|
|
|
dialogs are desrcibed in details in the \helpref{Common dialogs overview}{commondialogsoverview}.
|
|
|
|
|
|
|
|
\subsection{Scroll subwindow sample}\label{samplescrollsub}
|
|
|
|
|
|
|
|
This sample demonstrates the use of the \helpref{wxScrolledWindow}{wxscrolledwindow}
|
|
|
|
class including placing subwindows into it and drawing simple graphics. It uses the
|
|
|
|
\helpref{SetTargetWindow}{wxscrolledwindowsettargetwindow} 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 wxWindows,
|
|
|
|
in particular using the \helpref{wxWindow::IsExposed}{wxwindowisexposed} method with
|
|
|
|
the aim to prevent unnecessary drawing in the window and thus reducing or removing
|
|
|
|
flicker on screen.
|
|
|
|
|
1999-11-03 23:51:07 +00:00
|
|
|
\subsection{Font sample}\label{samplefont}
|
|
|
|
|
|
|
|
The font sample demonstrates \helpref{wxFont}{wxfont},
|
|
|
|
\helpref{wxFontEnumerator}{wxfontenumerator} and
|
|
|
|
\helpref{wxFontMapper}{wxfontmapper} classes. It allows you to see the fonts
|
|
|
|
available (to wxWindows) on the computer and shows all characters of the
|
|
|
|
chosen font as well.
|
|
|
|
|
1999-11-03 00:29:20 +00:00
|
|
|
\subsection{DnD sample}\label{samplednd}
|
1999-11-02 22:47:19 +00:00
|
|
|
|
|
|
|
This sample shows both clipboard and drag and drop in action. It is quite non
|
|
|
|
trivial and may be safely used as a basis for implementing the clipboard and
|
|
|
|
drag and drop operations in a real-life program.
|
|
|
|
|
|
|
|
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
|
|
|
|
\helpref{wxDropTarget}{wxdroptarget}:
|
|
|
|
\helpref{wxTextDropTarget}{wxtextdroptarget} and
|
|
|
|
\helpref{wxFileDropTarget}{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 two things: you can drag text from it to
|
|
|
|
either one of the listboxes (only one will accept it) or another application
|
|
|
|
and, also, bitmap pasted from clipboard will be shown there.
|
|
|
|
|
|
|
|
So far, everything we mentioned was implemented with minimal amount of code
|
|
|
|
using standard wxWindows 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 \helpref{wxDataFormat}{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.
|
|
|
|
|
|
|
|
Take a look at DnDShapeDataObject class to see how you may use
|
|
|
|
\helpref{wxDataObject}{wxdataobject} to achieve this.
|
1999-11-04 20:43:52 +00:00
|
|
|
|
1999-12-13 08:43:50 +00:00
|
|
|
|
|
|
|
\subsection{HTML samples}\label{samplehtml}
|
|
|
|
|
|
|
|
Eight HTML samples (you can find them in directory {\tt samples/html})
|
|
|
|
cover all features of HTML sub-library.
|
|
|
|
|
|
|
|
{\bf Test} demonstrates how to create \helpref{wxHtmlWindow}{wxhtmlwindow}
|
|
|
|
and also shows most of supported HTML tags.
|
|
|
|
|
|
|
|
{\bf Widget} shows how you can embed ordinary controls or windows within
|
|
|
|
HTML page. It also nicely explains how to write new tag handlers and extend
|
|
|
|
the library to work with unsupported tags.
|
|
|
|
|
|
|
|
{\bf About} may give you an idea how to write good-looking about boxes.
|
|
|
|
|
|
|
|
{\bf Zip} demonstrates use of virtual file systems in wxHTML. The zip archives
|
|
|
|
handler (ships with wxWindows) allows you to access HTML pages stored
|
|
|
|
in compressed archive as if they were ordinary files.
|
|
|
|
|
|
|
|
{\bf Virtual} is yet another VFS demo. This one generates pages at run-time.
|
|
|
|
You may find it useful if you need to display some reports in your application.
|
|
|
|
|
|
|
|
{\bf Printing} explains use of \helpref{wxHtmlEasyPrinting}{wxhtmleasyprinting}
|
|
|
|
class which serves as as-simple-as-possible interface for printing HTML
|
|
|
|
documents without much work. In fact, only few function calls are sufficient.
|
|
|
|
|
|
|
|
{\bf Help} and {\bf Helpview} are variations on displaying HTML help
|
|
|
|
(compatible with MS HTML Help Workshop). {\it Help} shows how to embed
|
|
|
|
\helpref{wxHtmlHelpController}{wxhtmlhelpcontroller} in your application
|
|
|
|
while {\it Helpview} is simple tool that only pops up help window and
|
|
|
|
displays help books given at command line.
|
|
|
|
|
2000-01-02 21:52:18 +00:00
|
|
|
\subsection{Thread sample}\label{samplethread}
|
|
|
|
|
|
|
|
This sample demonstrates the use of threads in connection with GUI programs.
|
|
|
|
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, wxWindows offers the \helpref{wxPostEvent}{wxpostevent}
|
|
|
|
function and this sample makes use of this function.
|
|
|
|
|
|
|
|
The other way to use a so called Mutex (such as those offered in the \helpref{wxMutex}{wxmutex}
|
|
|
|
class) that prevent threads from accessing the GUI classes as long as any other
|
|
|
|
thread accesses them. For this, wxWindows has the \helpref{wxMutexGuiEnter}{wxmutexguienter}
|
|
|
|
and \helpref{wxMutexGuiLeave}{wxmutexguileave} functions, both of which are
|
|
|
|
used and tested in the sample as well.
|
|
|
|
|
|
|
|
See also \helpref{Multithreading overview}{wxthreadoverview} and \helpref{wxThread}{wxthread}.
|
|
|
|
|
1999-12-14 02:02:09 +00:00
|
|
|
\subsection{Toolbar sample}\label{sampletoolbar}
|
|
|
|
|
|
|
|
The toolbar sample shows the \helpref{wxToolBar}{wxtoolbar} class in action.
|
|
|
|
|
|
|
|
The following things are demonstrated:
|
|
|
|
|
|
|
|
\begin{itemize}
|
|
|
|
|
|
|
|
\item Creating the toolbar using \helpref{wxToolBar::AddTool}{wxtoolbaraddtool}
|
|
|
|
and \helpref{wxToolBar::AddControl}{wxtoolbaraddcontrol}: see
|
|
|
|
MyApp::InitToolbar in the sample.
|
|
|
|
|
|
|
|
\item Using {\tt EVT\_UPDATE\_UI} handler for automatically enabling/disabling
|
|
|
|
toolbar buttons without having to explicitly call EnableTool. This is is done
|
|
|
|
in MyFrame::OnUpdateCopyAndCut.
|
|
|
|
|
|
|
|
\item Using \helpref{wxToolBar::DeleteTool}{wxtoolbardeletetool} and
|
|
|
|
\helpref{wxToolBar::InsertTool}{wxtoolbarinserttool} to dynamically update the
|
|
|
|
toolbar.
|
|
|
|
|
|
|
|
\end{itemize}
|