X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/526954c5968baa29218c994ec48e476ae2bd4b9f..3fb8a2bcfb362fa35dadd142b0569059a784fbb3:/docs/doxygen/overviews/windowids.h diff --git a/docs/doxygen/overviews/windowids.h b/docs/doxygen/overviews/windowids.h index 59e90287e8..169383f473 100644 --- a/docs/doxygen/overviews/windowids.h +++ b/docs/doxygen/overviews/windowids.h @@ -10,21 +10,7 @@ @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 - - -
- - -@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 @@ -36,7 +22,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 -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 @@ -50,6 +36,8 @@ one another. This is accomplished by keeping a reference count for each of the 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 @@ -85,4 +73,3 @@ This is done already for windows, menu items, and tool bar items. It should only be used in the main thread, as it is not thread safe. */ -