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

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

diff --git a/docs/doxygen/overviews/windowids.h b/docs/doxygen/overviews/windowids.h
index 45898dc587ecef199e45b8c917bbb7b84b41e02c..7bfc294d06bcb3d1c0fb14ec0aaa95cf28b00850 100644 (file)
--- a/docs/doxygen/overviews/windowids.h
+++ b/docs/doxygen/overviews/windowids.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

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


@@ -36,7 +36,7 @@ There are two ways to generate an ID.  One way is to start at a negative
 number, and for each new ID, return the next smallest number.  This is fine for
 systems that can use the full range of negative numbers for IDs, as this
 provides more than enough IDs and it would take a very very long time to run
 number, and for each new ID, return the next smallest number.  This is fine for
 systems that can use the full range of negative numbers for IDs, as this
 provides more than enough IDs and it would take a very very long time to run

-out and wrap around.  However, some systems can not use the full range of the
+out and wrap around.  However, some systems cannot use the full range of the

 ID value. Windows, for example, can only use 16 bit IDs, and only has about
 32000 possible automatic IDs that can be generated by wxWindow::NewControlId.
 If the program runs long enough, depending on the program itself, using this
 ID value. Windows, for example, can only use 16 bit IDs, and only has about
 32000 possible automatic IDs that can be generated by wxWindow::NewControlId.
 If the program runs long enough, depending on the program itself, using this