From c732a4d635e8b6fe2765bb18bb8e8ef19cbaf2f2 Mon Sep 17 00:00:00 2001 From: Greg Ercolano Date: Sat, 10 Jan 2015 22:05:15 +0000 Subject: Documentation clarification for all menu oriented widgets regarding callbacks. git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@10513 ea41ed52-d2ee-0310-a9c1-e6b18d33e121 --- FL/Fl_Choice.H | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) (limited to 'FL/Fl_Choice.H') diff --git a/FL/Fl_Choice.H b/FL/Fl_Choice.H index 8146f9476..1f93fb40a 100644 --- a/FL/Fl_Choice.H +++ b/FL/Fl_Choice.H @@ -38,10 +38,17 @@ often to control a single variable rather than do individual callbacks, some of the Fl_Menu_Button methods are redescribed here in those terms. - When the user picks an item off the menu the value() is set to that item - and then the item's callback is done with the menu_button as the - \c Fl_Widget* argument. If the item does not have a callback the - menu_button's callback is done instead. + When the user clicks a menu item, value() is set to that item + and then: + + - The item's callback is done if one has been set; the + Fl_Choice is passed as the Fl_Widget* argument, + along with any userdata configured for the callback. + + - If the item does not have a callback, the Fl_Choice widget's + callback is done instead, along with any userdata configured + for it. The callback can determine which item was picked using + value(), mvalue(), item_pathname(), etc. All three mouse buttons pop up the menu. The Forms behavior of the first two buttons to increment/decrement the choice is not implemented. This -- cgit v1.2.3