@page overview_windowids Window IDs
-@li @ref overview_windowids_intro
-@li @ref overview_windowids_type
-@li @ref overview_windowids_using
-
-@see
-
-@li wxIdManager
-@li wxWindow::NewControlId
-@li wxWindow::UnreserveControlId
-
-
-<hr>
-
-
-@section overview_windowids_intro Introduction
+@tableofcontents
Various controls and other parts of wxWidgets need an ID. Sometimes the ID may
be directly provided by the user or have a predefined value, such as
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
IDs that can possibly be returned by wxWindow::NewControlId. Other IDs are not
reference counted.
+@see wxIdManager, wxWindow::NewControlId(), wxWindow::UnreserveControlId()
+
@section overview_windowids_type Data Types
only be used in the main thread, as it is not thread safe.
*/
-