1 \section{\class{wxBrush
}}\label{wxbrush
}
3 A brush is a drawing tool for filling in areas. It is used for painting
4 the background of rectangles, ellipses, etc. It has a colour and a
7 \wxheading{Derived from
}
9 \helpref{wxGDIObject
}{wxgdiobject
}\\
10 \helpref{wxObject
}{wxobject
}
12 \wxheading{Include files
}
16 \wxheading{Predefined objects
}
29 wxMEDIUM
\_GREY\_BRUSH\\
30 wxLIGHT
\_GREY\_BRUSH\\
31 wxTRANSPARENT
\_BRUSH\\
37 On a monochrome display, wxWindows shows
38 all brushes as white unless the colour is really black.
40 Do not initialize objects on the stack before the program commences,
41 since other required structures may not have been set up yet. Instead,
42 define global pointers to objects and create them in
\helpref{wxApp::OnInit
}{wxapponinit
} or
45 An application may wish to create brushes with different
46 characteristics dynamically, and there is the consequent danger that a
47 large number of duplicate brushes will be created. Therefore an
48 application may wish to get a pointer to a brush by using the global
49 list of brushes
{\bf wxTheBrushList
}, and calling the member function
50 \rtfsp{\bf FindOrCreateBrush
}.
52 wxBrush uses a reference counting system, so assignments between brushes are very
53 cheap. You can therefore use actual wxBrush objects instead of pointers without
54 efficiency problems. Once one wxBrush object changes its data it will create its
55 own brush data internally so that other brushes, which previously shared the
56 data using the reference counting, are not affected.
58 %TODO: an overview for wxBrush.
61 \helpref{wxBrushList
}{wxbrushlist
},
\helpref{wxDC
}{wxdc
},
\helpref{wxDC::SetBrush
}{wxdcsetbrush
}
63 \latexignore{\rtfignore{\wxheading{Members
}}}
65 \membersection{wxBrush::wxBrush
}
67 \func{}{wxBrush
}{\void}
69 Default constructor. The brush will be uninitialised, and
\helpref{wxBrush::Ok
}{wxbrushok
} will
72 \func{}{wxBrush
}{\param{const wxColour\&
}{ colour
},
\param{int
}{ style
}}
74 Constructs a brush from a colour object and style.
76 \func{}{wxBrush
}{\param{const wxString\&
}{colourName
},
\param{int
}{ style
}}
78 Constructs a brush from a colour name and style.
80 \func{}{wxBrush
}{\param{const wxBitmap\&
}{stippleBitmap
}}
82 Constructs a stippled brush using a bitmap.
84 \func{}{wxBrush
}{\param{const wxBrush\&
}{ brush
}}
86 Copy constructor. This uses reference counting so is a cheap operation.
88 \wxheading{Parameters
}
90 \docparam{colour
}{Colour object.
}
92 \docparam{colourName
}{Colour name. The name will be looked up in the colour database.
}
94 \docparam{style
}{One of:
96 \begin{twocollist
}\itemsep=
0pt
97 \twocolitem{{\bf wxTRANSPARENT
}}{Transparent (no fill).
}
98 \twocolitem{{\bf wxSOLID
}}{Solid.
}
99 \twocolitem{{\bf wxBDIAGONAL
\_HATCH}}{Backward diagonal hatch.
}
100 \twocolitem{{\bf wxCROSSDIAG
\_HATCH}}{Cross-diagonal hatch.
}
101 \twocolitem{{\bf wxFDIAGONAL
\_HATCH}}{Forward diagonal hatch.
}
102 \twocolitem{{\bf wxCROSS
\_HATCH}}{Cross hatch.
}
103 \twocolitem{{\bf wxHORIZONTAL
\_HATCH}}{Horizontal hatch.
}
104 \twocolitem{{\bf wxVERTICAL
\_HATCH}}{Vertical hatch.
}
107 \docparam{brush
}{Pointer or reference to a brush to copy.
}
109 \docparam{stippleBitmap
}{A bitmap to use for stippling.
}
113 If a stipple brush is created, the brush style will be set to wxSTIPPLE.
117 \helpref{wxBrushList
}{wxbrushlist
},
\helpref{wxColour
}{wxcolour
},
\helpref{wxColourDatabase
}{wxcolourdatabase
}
119 \membersection{wxBrush::
\destruct{wxBrush
}}
121 \func{void
}{\destruct{wxBrush
}}{\void}
127 The destructor may not delete the underlying brush object of the native windowing
128 system, since wxBrush uses a reference counting system for efficiency.
130 Although all remaining brushes are deleted when the application exits,
131 the application should try to clean up all brushes itself. This is because
132 wxWindows cannot know if a pointer to the brush object is stored in an
133 application data structure, and there is a risk of double deletion.
135 \membersection{wxBrush::GetColour
}\label{wxbrushgetcolour
}
137 \constfunc{wxColour\&
}{GetColour
}{\void}
139 Returns a reference to the brush colour.
143 \helpref{wxBrush::SetColour
}{wxbrushsetcolour
}
145 \membersection{wxBrush::GetStipple
}\label{wxbrushgetstipple
}
147 \constfunc{wxBitmap *
}{GetStipple
}{\void}
149 Gets a pointer to the stipple bitmap. If the brush does not have a wxSTIPPLE style,
150 this bitmap may be non-NULL but uninitialised (
\helpref{wxBitmap::Ok
}{wxbitmapok
} returns FALSE).
154 \helpref{wxBrush::SetStipple
}{wxbrushsetstipple
}
156 \membersection{wxBrush::GetStyle
}\label{wxbrushgetstyle
}
158 \constfunc{int
}{GetStyle
}{\void}
160 Returns the brush style, one of:
162 \begin{twocollist
}\itemsep=
0pt
163 \twocolitem{{\bf wxTRANSPARENT
}}{Transparent (no fill).
}
164 \twocolitem{{\bf wxSOLID
}}{Solid.
}
165 \twocolitem{{\bf wxBDIAGONAL
\_HATCH}}{Backward diagonal hatch.
}
166 \twocolitem{{\bf wxCROSSDIAG
\_HATCH}}{Cross-diagonal hatch.
}
167 \twocolitem{{\bf wxFDIAGONAL
\_HATCH}}{Forward diagonal hatch.
}
168 \twocolitem{{\bf wxCROSS
\_HATCH}}{Cross hatch.
}
169 \twocolitem{{\bf wxHORIZONTAL
\_HATCH}}{Horizontal hatch.
}
170 \twocolitem{{\bf wxVERTICAL
\_HATCH}}{Vertical hatch.
}
171 \twocolitem{{\bf wxSTIPPLE
}}{Stippled using a bitmap.
}
176 \helpref{wxBrush::SetStyle
}{wxbrushsetstyle
},
\helpref{wxBrush::SetColour
}{wxbrushsetcolour
},
\rtfsp
177 \helpref{wxBrush::SetStipple
}{wxbrushsetstipple
}
179 \membersection{wxBrush::Ok
}\label{wxbrushok
}
181 \constfunc{bool
}{Ok
}{\void}
183 Returns TRUE if the brush is initialised. It will return FALSE if the default
184 constructor has been used (for example, the brush is a member of a class, or
185 NULL has been assigned to it).
187 \membersection{wxBrush::SetColour
}\label{wxbrushsetcolour
}
189 \func{void
}{SetColour
}{\param{wxColour\&
}{colour
}}
191 Sets the brush colour using a reference to a colour object.
193 \func{void
}{SetColour
}{\param{const wxString\&
}{colourName
}}
195 Sets the brush colour using a colour name from the colour database.
197 \func{void
}{SetColour
}{\param{const unsigned char
}{ red
},
\param{const unsigned char
}{ green
},
\param{const unsigned char
}{ blue
}}
199 Sets the brush colour using red, green and blue values.
203 \helpref{wxBrush::GetColour
}{wxbrushgetcolour
}
205 \membersection{wxBrush::SetStipple
}\label{wxbrushsetstipple
}
207 \func{void
}{SetStipple
}{\param{const wxBitmap\&
}{ bitmap
}}
209 Sets the stipple bitmap.
211 \wxheading{Parameters
}
213 \docparam{bitmap
}{The bitmap to use for stippling.
}
217 The style will be set to wxSTIPPLE.
219 Note that there is a big difference between stippling in X and Windows.
220 On X, the stipple is a mask between the wxBitmap and current colour.
221 On Windows, the current colour is ignored, and the bitmap colour is used.
222 However, for pre-defined modes like wxCROSS
\_HATCH, the behaviour is the
223 same for both platforms.
227 \helpref{wxBitmap
}{wxbitmap
}
229 \membersection{wxBrush::SetStyle
}\label{wxbrushsetstyle
}
231 \func{void
}{SetStyle
}{\param{int
}{ style
}}
233 Sets the brush style.
235 \docparam{style
}{One of:
237 \begin{twocollist
}\itemsep=
0pt
238 \twocolitem{{\bf wxTRANSPARENT
}}{Transparent (no fill).
}
239 \twocolitem{{\bf wxSOLID
}}{Solid.
}
240 \twocolitem{{\bf wxBDIAGONAL
\_HATCH}}{Backward diagonal hatch.
}
241 \twocolitem{{\bf wxCROSSDIAG
\_HATCH}}{Cross-diagonal hatch.
}
242 \twocolitem{{\bf wxFDIAGONAL
\_HATCH}}{Forward diagonal hatch.
}
243 \twocolitem{{\bf wxCROSS
\_HATCH}}{Cross hatch.
}
244 \twocolitem{{\bf wxHORIZONTAL
\_HATCH}}{Horizontal hatch.
}
245 \twocolitem{{\bf wxVERTICAL
\_HATCH}}{Vertical hatch.
}
246 \twocolitem{{\bf wxSTIPPLE
}}{Stippled using a bitmap.
}
251 \helpref{wxBrush::GetStyle
}{wxbrushgetstyle
}
253 \membersection{wxBrush::operator $=$
}\label{wxbrushassignment
}
255 \func{wxBrush\&
}{operator $=$
}{\param{const wxBrush\&
}{brush
}}
257 Assignment operator, using reference counting. Returns a reference
260 \membersection{wxBrush::operator $==$
}\label{wxbrushequals
}
262 \func{bool
}{operator $==$
}{\param{const wxBrush\&
}{brush
}}
264 Equality operator. Two brushes are equal if they contain pointers
265 to the same underlying brush data. It does not compare each attribute,
266 so two independently-created brushes using the same parameters will
269 \membersection{wxBrush::operator $!=$
}\label{wxbrushnotequals
}
271 \func{bool
}{operator $!=$
}{\param{const wxBrush\&
}{brush
}}
273 Inequality operator. Two brushes are not equal if they contain pointers
274 to different underlying brush data. It does not compare each attribute.
276 \section{\class{wxBrushList
}}\label{wxbrushlist
}
278 A brush list is a list containing all brushes which have been created.
280 \wxheading{Derived from
}
282 \helpref{wxList
}{wxlist
}\\
283 \helpref{wxObject
}{wxobject
}
285 \wxheading{Include files
}
291 There is only one instance of this class:
{\bf wxTheBrushList
}. Use
292 this object to search for a previously created brush of the desired
293 type and create it if not already found. In some windowing systems,
294 the brush may be a scarce resource, so it can pay to reuse old
295 resources if possible. When an application finishes, all brushes will
296 be deleted and their resources freed, eliminating the possibility of
297 `memory leaks'. However, it is best not to rely on this automatic
298 cleanup because it can lead to double deletion in some circumstances.
300 There are two mechanisms in recent versions of wxWindows which make the
301 brush list less useful than it once was. Under Windows, scarce resources
302 are cleaned up internally if they are not being used. Also, a referencing
303 counting mechanism applied to all GDI objects means that some sharing
304 of underlying resources is possible. You don't have to keep track of pointers,
305 working out when it is safe delete a brush, because the referencing counting does
306 it for you. For example, you can set a brush in a device context, and then
307 immediately delete the brush you passed, because the brush is `copied'.
309 So you may find it easier to ignore the brush list, and instead create
310 and copy brushes as you see fit. If your Windows resource meter suggests
311 your application is using too many resources, you can resort to using
312 GDI lists to share objects explicitly.
314 The only compelling use for the brush list is for wxWindows to keep
315 track of brushes in order to clean them up on exit. It is also kept for
316 backward compatibility with earlier versions of wxWindows.
320 \helpref{wxBrush
}{wxbrush
}
322 \latexignore{\rtfignore{\wxheading{Members
}}}
324 \membersection{wxBrushList::wxBrushList
}\label{wxbrushlistconstr
}
326 \func{void
}{wxBrushList
}{\void}
328 Constructor. The application should not construct its own brush list:
329 use the object pointer
{\bf wxTheBrushList
}.
331 \membersection{wxBrushList::AddBrush
}\label{wxbrushlistaddbrush
}
333 \func{void
}{AddBrush
}{\param{wxBrush *
}{brush
}}
335 Used internally by wxWindows to add a brush to the list.
337 \membersection{wxBrushList::FindOrCreateBrush
}\label{wxbrushlistfindorcreatebrush
}
339 \func{wxBrush *
}{FindOrCreateBrush
}{\param{const wxColour\&
}{colour
},
\param{int
}{ style
}}
341 Finds a brush with the specified attributes and returns it, else creates a new brush, adds it
342 to the brush list, and returns it.
344 \func{wxBrush *
}{FindOrCreateBrush
}{\param{const wxString\&
}{colourName
},
\param{int
}{ style
}}
346 Finds a brush with the specified attributes and returns it, else creates a new brush, adds it
347 to the brush list, and returns it.
349 Finds a brush of the given specification, or creates one and adds it to the list.
351 \wxheading{Parameters
}
353 \docparam{colour
}{Colour object.
}
355 \docparam{colourName
}{Colour name, which should be in the colour database.
}
357 \docparam{style
}{Brush style. See
\helpref{wxBrush::SetStyle
}{wxbrushsetstyle
} for a list of styles.
}
359 \membersection{wxBrushList::RemoveBrush
}\label{wxbrushlistremovebrush
}
361 \func{void
}{RemoveBrush
}{\param{wxBrush *
}{brush
}}
363 Used by wxWindows to remove a brush from the list.