From 8fe94273fffb5b968c0ac2dcf13d829de449ae0a Mon Sep 17 00:00:00 2001 From: Greg Ercolano Date: Sat, 10 Jan 2015 17:58:54 +0000 Subject: 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 --- FL/Fl_Menu_Bar.H | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/FL/Fl_Menu_Bar.H b/FL/Fl_Menu_Bar.H index bc7f98b8b..45696a98d 100644 --- a/FL/Fl_Menu_Bar.H +++ b/FL/Fl_Menu_Bar.H @@ -40,9 +40,16 @@

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.

-

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.

+ + 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. +

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 -- cgit v1.2.3