Small doc mods to Fl_Menu_Bar to clarify how callbacks
are invoked. (STR #3172) git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@10512 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
This commit is contained in:
parent
5cfa1ac706
commit
8fe94273ff
@ -40,9 +40,16 @@
|
||||
<P>If there is an item in the top menu that is not a title of a
|
||||
submenu, then it acts like a "button" in the menubar. Clicking on it
|
||||
will pick it. </P>
|
||||
<P>When the user picks an item off the menu, the item's callback is
|
||||
done with the menubar as the Fl_Widget* argument. If the item
|
||||
does not have a callback the menubar's callback is done instead. </P>
|
||||
|
||||
When the user picks an item in the menu:
|
||||
|
||||
- The item's callback is done; the menubar is passed as the
|
||||
Fl_Widget* argument, along with any userdata configured
|
||||
for the callback.
|
||||
|
||||
- If the item does not have a callback, the menubar's callback
|
||||
is done instead, along with any userdata configured for the callback.
|
||||
|
||||
<P>Submenus will also pop up in response to shortcuts indicated by
|
||||
putting a '&' character in the name field of the menu item. If you put a
|
||||
'&' character in a top-level "button" then the shortcut picks it. The
|
||||
|
Loading…
Reference in New Issue
Block a user