Commit 28a88153 authored by Chong Yidong's avatar Chong Yidong
Browse files

* frames.texi (Pop-Up Menus): Document where menu title comes from (Bug#7684).

parent 4d265b4d
2011-01-22 Chong Yidong <cyd@stupidchicken.com>
* frames.texi (Pop-Up Menus): Document where menu title comes
from (Bug#7684).
2011-01-22 Glenn Morris <rgm@gnu.org> 2011-01-22 Glenn Morris <rgm@gnu.org>
* display.texi (Making Buttons): Mention limitation of text buttons. * display.texi (Making Buttons): Mention limitation of text buttons.
......
...@@ -1715,9 +1715,13 @@ without actually displaying or popping up the menu. ...@@ -1715,9 +1715,13 @@ without actually displaying or popping up the menu.
The argument @var{menu} says what to display in the menu. It can be a The argument @var{menu} says what to display in the menu. It can be a
keymap or a list of keymaps (@pxref{Menu Keymaps}). In this case, the keymap or a list of keymaps (@pxref{Menu Keymaps}). In this case, the
return value is the list of events corresponding to the user's choice. return value is the list of events corresponding to the user's choice.
(This list has more than one element if the choice occurred in a This list has more than one element if the choice occurred in a
submenu.) Note that @code{x-popup-menu} does not actually execute the submenu. (Note that @code{x-popup-menu} does not actually execute the
command bound to that sequence of events. command bound to that sequence of events.) On toolkits that support
menu titles, the title is taken from the prompt string of @var{menu}
if @var{menu} is a keymap, or from the prompt string of the first
keymap in @var{menu} if it is a list of keymaps (@pxref{Defining
Menus}).
Alternatively, @var{menu} can have the following form: Alternatively, @var{menu} can have the following form:
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment