Implement hatched/stippled pens/brushes in wxGraphicsContext for Cairo.

[wxWidgets.git] / docs / doxygen / overviews / customwidgets.h

diff --git a/docs/doxygen/overviews/customwidgets.h b/docs/doxygen/overviews/customwidgets.h
index 471abd035f56f49cfa67615c2f89131ca273b1b8..d427746e825f9f7f5f12d6edc950cf32442d5f96 100644 (file)
--- a/docs/doxygen/overviews/customwidgets.h
+++ b/docs/doxygen/overviews/customwidgets.h
@@ -3,7 +3,7 @@
 // Purpose:     topic overview
 // Author:      wxWidgets team
 // RCS-ID:      $Id$
 // Purpose:     topic overview
 // Author:      wxWidgets team
 // RCS-ID:      $Id$

-// Licence:     wxWindows license
+// Licence:     wxWindows licence

 /////////////////////////////////////////////////////////////////////////////
 
 /**
 /////////////////////////////////////////////////////////////////////////////
 
 /**


@@ -26,7 +26,7 @@ and is obviously easier and faster.
 However there are situations where you need to show some particular kind of data
 which is not suited to any existing control.
 In these cases rather than hacking an existing control for something it has not
 However there are situations where you need to show some particular kind of data
 which is not suited to any existing control.
 In these cases rather than hacking an existing control for something it has not

-been coinceived for, it's better to write a new widget.
+been conceived for, it's better to write a new widget.

 
 
 @section overview_customwidgets_how How to write the custom widget
 
 
 @section overview_customwidgets_how How to write the custom widget


@@ -47,7 +47,7 @@ implementations and thus more work.
 
 In both cases you'll want to better explore some hot topics like:
 - @ref overview_windowsizing
 
 In both cases you'll want to better explore some hot topics like:
 - @ref overview_windowsizing

-- @ref overview_eventhandling_custom to implement your custom widget's events.
+- @ref overview_events_custom to implement your custom widget's events.

 You will probably need also to gain some familiarity with the wxWidgets sources,
 since you'll need to interface with some undocumented wxWidgets internal mechanisms.
 
 You will probably need also to gain some familiarity with the wxWidgets sources,
 since you'll need to interface with some undocumented wxWidgets internal mechanisms.
 


@@ -135,7 +135,7 @@ The organization used by wxWidgets consists in:
 - declaring the real widget class inheriting from the Base version in
   platform-specific headers; see for example the wxWidgets' @c "wx/gtk/button.h" file.
 
 - declaring the real widget class inheriting from the Base version in
   platform-specific headers; see for example the wxWidgets' @c "wx/gtk/button.h" file.
 

-- separing the different implementations in different source files, putting
+- separating the different implementations in different source files, putting

   all common stuff in a separate source.
   See for example the wxWidgets' @c "src/common/btncmn.cpp", @c "src/gtk/button.cpp"
   and @c "src/msw/button.cpp" files.
   all common stuff in a separate source.
   See for example the wxWidgets' @c "src/common/btncmn.cpp", @c "src/gtk/button.cpp"
   and @c "src/msw/button.cpp" files.