added a few missing tree events to the docs

[wxWidgets.git] / docs / latex / wx / upduievt.tex

diff --git a/docs/latex/wx/upduievt.tex b/docs/latex/wx/upduievt.tex
index 2423083c1d734f644156802b09a440a26cdad628..925f4b6ef0fdfb2d58235f07889f4f37cce0ce7f 100644 (file)
--- a/docs/latex/wx/upduievt.tex
+++ b/docs/latex/wx/upduievt.tex
@@ -8,14 +8,19 @@ to give an application the chance to update various user interface elements.
 \helpref{wxEvent}{wxevent}\\
 \helpref{wxObject}{wxobject}
 
+\wxheading{Include files}
+
+<wx/event.h>
+
 \wxheading{Event table macros}
 
-To process a menu event, use these event handler macros to direct input to member
+To process an update event, use these event handler macros to direct input to member
 functions that take a wxUpdateUIEvent argument.
 
 \twocolwidtha{7cm}
 \begin{twocollist}\itemsep=0pt
-\twocolitem{{\bf EVT\_UPDATE\_UI(id, func)}}{Process a wxEVT\_UPDATE\_UI event.}
+\twocolitem{{\bf EVT\_UPDATE\_UI(id, func)}}{Process a wxEVT\_UPDATE\_UI event for the command with the given id.}
+\twocolitem{{\bf EVT\_UPDATE\_UI\_RANGE(id1, id2, func)}}{Process a wxEVT\_UPDATE\_UI event for any command with id included in the given range.}
 \end{twocollist}%
 
 \wxheading{Remarks}
@@ -36,6 +41,10 @@ Instead of directly manipulating the menu or button, you call functions in the e
 object, such as \helpref{wxUpdateUIEvent::Check}{wxupdateuieventcheck}. wxWindows
 will determine whether such a call has been made, and which UI element to update.
 
+These events will work for popup menus as well as menubars. Just before a menu is popped
+up, \helpref{wxMenu::UpdateUI}{wxmenuupdateui} is called to process any UI events for
+the window that owns the menu.
+
 \wxheading{See also}
 
 \helpref{Event handling overview}{eventhandlingoverview}