]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/latex/wx/brush.tex
ODBC updates
[wxWidgets.git] / docs / latex / wx / brush.tex
... / ...
CommitLineData
1\section{\class{wxBrush}}\label{wxbrush}
2
3A brush is a drawing tool for filling in areas. It is used for painting
4the background of rectangles, ellipses, etc. It has a colour and a
5style.
6
7\wxheading{Derived from}
8
9\helpref{wxGDIObject}{wxgdiobject}\\
10\helpref{wxObject}{wxobject}
11
12\wxheading{Remarks}
13
14On a monochrome display, wxWindows shows
15all brushes as white unless the colour is really black.
16
17Do not initialize objects on the stack before the program commences,
18since other required structures may not have been set up yet. Instead,
19define global pointers to objects and create them in \helpref{wxApp::OnInit}{wxapponinit} or
20when required.
21
22An application may wish to create brushes with different
23characteristics dynamically, and there is the consequent danger that a
24large number of duplicate brushes will be created. Therefore an
25application may wish to get a pointer to a brush by using the global
26list of brushes {\bf wxTheBrushList}, and calling the member function
27\rtfsp{\bf FindOrCreateBrush}.
28
29wxBrush uses a reference counting system, so assignments between brushes are very
30cheap. You can therefore use actual wxBrush objects instead of pointers without
31efficiency problems. Once one wxBrush object changes its data it will create its
32own brush data internally so that other brushes, which previously shared the
33data using the reference counting, are not affected.
34
35TODO: an overview for wxBrush.
36
37\wxheading{See also}
38
39\helpref{wxBrushList}{wxbrushlist}, \helpref{wxDC}{wxdc}, \helpref{wxDC::SetBrush}{wxdcsetbrush}
40
41\latexignore{\rtfignore{\wxheading{Members}}}
42
43\membersection{wxBrush::wxBrush}
44
45\func{}{wxBrush}{\void}
46
47Default constructor. The brush will be uninitialised, and \helpref{wxBrush::Ok}{wxbrushok} will
48return FALSE.
49
50\func{}{wxBrush}{\param{const wxColour\&}{ colour}, \param{int}{ style}}
51
52Constructs a brush from a colour object and style.
53
54\func{}{wxBrush}{\param{const wxString\& }{colourName}, \param{int}{ style}}
55
56Constructs a brush from a colour name and style.
57
58\func{}{wxBrush}{\param{const wxBitmap\& }{stippleBitmap}}
59
60Constructs a stippled brush using a bitmap.
61
62\func{}{wxBrush}{\param{const wxBrush\&}{ brush}}
63
64Copy constructor. This uses reference counting so is a cheap operation.
65
66\wxheading{Parameters}
67
68\docparam{colour}{Colour object.}
69
70\docparam{colourName}{Colour name. The name will be looked up in the colour database.}
71
72\docparam{style}{One of:
73
74\begin{twocollist}\itemsep=0pt
75\twocolitem{{\bf wxTRANSPARENT}}{Transparent (no fill).}
76\twocolitem{{\bf wxSOLID}}{Solid.}
77\twocolitem{{\bf wxBDIAGONAL\_HATCH}}{Backward diagonal hatch.}
78\twocolitem{{\bf wxCROSSDIAG\_HATCH}}{Cross-diagonal hatch.}
79\twocolitem{{\bf wxFDIAGONAL\_HATCH}}{Forward diagonal hatch.}
80\twocolitem{{\bf wxCROSS\_HATCH}}{Cross hatch.}
81\twocolitem{{\bf wxHORIZONTAL\_HATCH}}{Horizontal hatch.}
82\twocolitem{{\bf wxVERTICAL\_HATCH}}{Vertical hatch.}
83\end{twocollist}}
84
85\docparam{brush}{Pointer or reference to a brush to copy.}
86
87\docparam{stippleBitmap}{A bitmap to use for stippling.}
88
89\wxheading{Remarks}
90
91If a stipple brush is created, the brush style will be set to wxSTIPPLE.
92
93\wxheading{See also}
94
95\helpref{wxBrushList}{wxbrushlist}, \helpref{wxColour}{wxcolour}, \helpref{wxColourDatabase}{wxcolourdatabase}
96
97\membersection{wxBrush::\destruct{wxBrush}}
98
99\func{void}{\destruct{wxBrush}}{\void}
100
101Destructor.
102
103\wxheading{Remarks}
104
105The destructor may not delete the underlying brush object of the native windowing
106system, since wxBrush uses a reference counting system for efficiency.
107
108Although all remaining brushes are deleted when the application exits,
109the application should try to clean up all brushes itself. This is because
110wxWindows cannot know if a pointer to the brush object is stored in an
111application data structure, and there is a risk of double deletion.
112
113\membersection{wxBrush::GetColour}\label{wxbrushgetcolour}
114
115\constfunc{wxColour\&}{GetColour}{\void}
116
117Returns a reference to the brush colour.
118
119\wxheading{See also}
120
121\helpref{wxBrush::SetColour}{wxbrushsetcolour}
122
123\membersection{wxBrush::GetStipple}\label{wxbrushgetstipple}
124
125\constfunc{wxBitmap *}{GetStipple}{\void}
126
127Gets a pointer to the stipple bitmap. If the brush does not have a wxSTIPPLE style,
128this bitmap may be non-NULL but uninitialised (\helpref{wxBitmap::Ok}{wxbitmapok} returns FALSE).
129
130\wxheading{See also}
131
132\helpref{wxBrush::SetStipple}{wxbrushsetstipple}
133
134\membersection{wxBrush::GetStyle}\label{wxbrushgetstyle}
135
136\constfunc{int}{GetStyle}{\void}
137
138Returns the brush style, one of:
139
140\begin{twocollist}\itemsep=0pt
141\twocolitem{{\bf wxTRANSPARENT}}{Transparent (no fill).}
142\twocolitem{{\bf wxSOLID}}{Solid.}
143\twocolitem{{\bf wxBDIAGONAL\_HATCH}}{Backward diagonal hatch.}
144\twocolitem{{\bf wxCROSSDIAG\_HATCH}}{Cross-diagonal hatch.}
145\twocolitem{{\bf wxFDIAGONAL\_HATCH}}{Forward diagonal hatch.}
146\twocolitem{{\bf wxCROSS\_HATCH}}{Cross hatch.}
147\twocolitem{{\bf wxHORIZONTAL\_HATCH}}{Horizontal hatch.}
148\twocolitem{{\bf wxVERTICAL\_HATCH}}{Vertical hatch.}
149\twocolitem{{\bf wxSTIPPLE}}{Stippled using a bitmap.}
150\end{twocollist}
151
152\wxheading{See also}
153
154\helpref{wxBrush::SetStyle}{wxbrushsetstyle}, \helpref{wxBrush::SetColour}{wxbrushsetcolour},\rtfsp
155\helpref{wxBrush::SetStipple}{wxbrushsetstipple}
156
157\membersection{wxBrush::Ok}\label{wxbrushok}
158
159\constfunc{bool}{Ok}{\void}
160
161Returns TRUE if the brush is initialised. It will return FALSE if the default
162constructor has been used (for example, the brush is a member of a class, or
163NULL has been assigned to it).
164
165\membersection{wxBrush::SetColour}\label{wxbrushsetcolour}
166
167\func{void}{SetColour}{\param{wxColour\& }{colour}}
168
169Sets the brush colour using a reference to a colour object.
170
171\func{void}{SetColour}{\param{const wxString\& }{colourName}}
172
173Sets the brush colour using a colour name from the colour database.
174
175\func{void}{SetColour}{\param{const unsigned char}{ red}, \param{const unsigned char}{ green}, \param{const unsigned char}{ blue}}
176
177Sets the brush colour using red, green and blue values.
178
179\wxheading{See also}
180
181\helpref{wxBrush::GetColour}{wxbrushgetcolour}
182
183\membersection{wxBrush::SetStipple}\label{wxbrushsetstipple}
184
185\func{void}{SetStipple}{\param{const wxBitmap\&}{ bitmap}}
186
187Sets the stipple bitmap.
188
189\wxheading{Parameters}
190
191\docparam{bitmap}{The bitmap to use for stippling.}
192
193\wxheading{Remarks}
194
195The style will be set to wxSTIPPLE.
196
197Note that there is a big difference between stippling in X and Windows.
198On X, the stipple is a mask between the wxBitmap and current colour.
199On Windows, the current colour is ignored, and the bitmap colour is used.
200However, for pre-defined modes like wxCROSS\_HATCH, the behaviour is the
201same for both platforms.
202
203\wxheading{See also}
204
205\helpref{wxBitmap}{wxbitmap}
206
207\membersection{wxBrush::SetStyle}\label{wxbrushsetstyle}
208
209\func{void}{SetStyle}{\param{int}{ style}}
210
211Sets the brush style.
212
213\docparam{style}{One of:
214
215\begin{twocollist}\itemsep=0pt
216\twocolitem{{\bf wxTRANSPARENT}}{Transparent (no fill).}
217\twocolitem{{\bf wxSOLID}}{Solid.}
218\twocolitem{{\bf wxBDIAGONAL\_HATCH}}{Backward diagonal hatch.}
219\twocolitem{{\bf wxCROSSDIAG\_HATCH}}{Cross-diagonal hatch.}
220\twocolitem{{\bf wxFDIAGONAL\_HATCH}}{Forward diagonal hatch.}
221\twocolitem{{\bf wxCROSS\_HATCH}}{Cross hatch.}
222\twocolitem{{\bf wxHORIZONTAL\_HATCH}}{Horizontal hatch.}
223\twocolitem{{\bf wxVERTICAL\_HATCH}}{Vertical hatch.}
224\twocolitem{{\bf wxSTIPPLE}}{Stippled using a bitmap.}
225\end{twocollist}}
226
227\wxheading{See also}
228
229\helpref{wxBrush::GetStyle}{wxbrushgetstyle}
230
231\membersection{wxBrush::operator $=$}\label{wxbrushassignment}
232
233\func{wxBrush\&}{operator $=$}{\param{const wxBrush\& }{brush}}
234
235Assignment operator, using reference counting. Returns a reference
236to `this'.
237
238\membersection{wxBrush::operator $==$}\label{wxbrushequals}
239
240\func{bool}{operator $==$}{\param{const wxBrush\& }{brush}}
241
242Equality operator. Two brushes are equal if they contain pointers
243to the same underlying brush data. It does not compare each attribute,
244so two independently-created brushes using the same parameters will
245fail the test.
246
247\membersection{wxBrush::operator $!=$}\label{wxbrushnotequals}
248
249\func{bool}{operator $!=$}{\param{const wxBrush\& }{brush}}
250
251Inequality operator. Two brushes are not equal if they contain pointers
252to different underlying brush data. It does not compare each attribute.
253
254\section{\class{wxBrushList}}\label{wxbrushlist}
255
256A brush list is a list containing all brushes which have been created.
257
258\wxheading{Derived from}
259
260\helpref{wxList}{wxlist}\\
261\helpref{wxObject}{wxobject}
262
263\wxheading{Remarks}
264
265There is only one instance of this class: {\bf wxTheBrushList}. Use
266this object to search for a previously created brush of the desired
267type and create it if not already found. In some windowing systems,
268the brush may be a scarce resource, so it can pay to reuse old
269resources if possible. When an application finishes, all brushes will
270be deleted and their resources freed, eliminating the possibility of
271`memory leaks'. However, it is best not to rely on this automatic
272cleanup because it can lead to double deletion in some circumstances.
273
274There are two mechanisms in recent versions of wxWindows which make the
275brush list less useful than it once was. Under Windows, scarce resources
276are cleaned up internally if they are not being used. Also, a referencing
277counting mechanism applied to all GDI objects means that some sharing
278of underlying resources is possible. You don't have to keep track of pointers,
279working out when it is safe delete a brush, because the referencing counting does
280it for you. For example, you can set a brush in a device context, and then
281immediately delete the brush you passed, because the brush is `copied'.
282
283So you may find it easier to ignore the brush list, and instead create
284and copy brushes as you see fit. If your Windows resource meter suggests
285your application is using too many resources, you can resort to using
286GDI lists to share objects explicitly.
287
288The only compelling use for the brush list is for wxWindows to keep
289track of brushes in order to clean them up on exit. It is also kept for
290backward compatibility with earlier versions of wxWindows.
291
292\wxheading{See also}
293
294\helpref{wxBrush}{wxbrush}
295
296\latexignore{\rtfignore{\wxheading{Members}}}
297
298\membersection{wxBrushList::wxBrushList}\label{wxbrushlistconstr}
299
300\func{void}{wxBrushList}{\void}
301
302Constructor. The application should not construct its own brush list:
303use the object pointer {\bf wxTheBrushList}.
304
305\membersection{wxBrushList::AddBrush}\label{wxbrushlistaddbrush}
306
307\func{void}{AddBrush}{\param{wxBrush *}{brush}}
308
309Used internally by wxWindows to add a brush to the list.
310
311\membersection{wxBrushList::FindOrCreateBrush}\label{wxbrushlistfindorcreatebrush}
312
313\func{wxBrush *}{FindOrCreateBrush}{\param{const wxColour\& }{colour}, \param{int}{ style}}
314
315Finds a brush with the specified attributes and returns it, else creates a new brush, adds it
316to the brush list, and returns it.
317
318\func{wxBrush *}{FindOrCreateBrush}{\param{const wxString\& }{colourName}, \param{int}{ style}}
319
320Finds a brush with the specified attributes and returns it, else creates a new brush, adds it
321to the brush list, and returns it.
322
323Finds a brush of the given specification, or creates one and adds it to the list.
324
325\wxheading{Parameters}
326
327\docparam{colour}{Colour object.}
328
329\docparam{colourName}{Colour name, which should be in the colour database.}
330
331\docparam{style}{Brush style. See \helpref{wxBrush::SetStyle}{wxbrushsetstyle} for a list of styles.}
332
333\membersection{wxBrushList::RemoveBrush}\label{wxbrushlistremovebrush}
334
335\func{void}{RemoveBrush}{\param{wxBrush *}{brush}}
336
337Used by wxWindows to remove a brush from the list.
338
339