summaryrefslogtreecommitdiff
path: root/FL/Fl_Menu_Bar.H
diff options
context:
space:
mode:
Diffstat (limited to 'FL/Fl_Menu_Bar.H')
-rw-r--r--FL/Fl_Menu_Bar.H13
1 files changed, 8 insertions, 5 deletions
diff --git a/FL/Fl_Menu_Bar.H b/FL/Fl_Menu_Bar.H
index 45696a98d..98127e33c 100644
--- a/FL/Fl_Menu_Bar.H
+++ b/FL/Fl_Menu_Bar.H
@@ -41,14 +41,17 @@
submenu, then it acts like a "button" in the menubar. Clicking on it
will pick it. </P>
- When the user picks an item in the menu:
+ When the user clicks a menu item, value() is set to that item
+ and then:
- - The item's callback is done; the menubar is passed as the
- Fl_Widget* argument, along with any userdata configured
- for the callback.
+ - The item's callback is done if one has been set; the
+ Fl_Menu_Bar 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
+ - If the item does not have a callback, the Fl_Menu_Bar's callback
is done instead, along with any userdata configured for the callback.
+ The callback can determine which item was picked using
+ value(), mvalue(), item_pathname(), etc.
<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