summaryrefslogtreecommitdiff
path: root/documentation/Fl_Menu_Button.html
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/Fl_Menu_Button.html')
-rw-r--r--documentation/Fl_Menu_Button.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/documentation/Fl_Menu_Button.html b/documentation/Fl_Menu_Button.html
index b1df98060..b073b4dd3 100644
--- a/documentation/Fl_Menu_Button.html
+++ b/documentation/Fl_Menu_Button.html
@@ -26,10 +26,10 @@ below the button as shown in the picture. However an <TT>Fl_Menu_Button</TT>
may also control a pop-up menu. This is done by setting the <TT>type()</TT>
, see below. </P>
<P>The menu will also pop up in response to shortcuts indicated by
-putting a ''character in the <TT>label()</TT>. </P>
+putting a '&amp;' character in the <TT>label()</TT>. </P>
<P>Typing the <TT>shortcut()</TT> of any of the menu items will cause
callbacks exactly the same as when you pick the item with the mouse.
- The ''character in menu item names are only looked at when the menu is
+ The '&amp;' character in menu item names are only looked at when the menu is
popped up, however. </P>
<P>When the user picks an item off the menu, the item's callback is
done with the menu_button as the <TT>Fl_Widget*</TT> argument. If the
@@ -59,7 +59,7 @@ its menu items.
shortcut key. The menu appears, it waits for the user to pick an item,
and if they pick one it sets <TT>value()</TT> and does the callback or
sets <TT>changed()</TT> as described above. The menu item is returned
-or <TT>NULL</TT>if the user dismisses the menu.
+or <TT>NULL</TT> if the user dismisses the menu.
<H4><A name=Fl_Menu_Button.type>void Fl_Menu_Button::type(uchar)</A></H4>
If <TT>type()</TT> is zero a normal menu button is produced. If it is
nonzero then this is a pop-up menu. The bits in <TT>type()</TT>