Mercurial > hg > xemacs-beta
view man/lispref/dialog.texi @ 5745:f9e4d44504a4
Document #'events-to-keys some more, use it less.
lisp/ChangeLog addition:
2013-07-10 Aidan Kehoe <kehoea@parhasard.net>
* minibuf.el (get-user-response):
* cmdloop.el (y-or-n-p-minibuf):
No need to call #'events-to-keys in these two functions,
#'lookup-key accepts events directly.
* keymap.el:
* keymap.el (events-to-keys):
Document this function some more.
Stop passing strings through unexamined, treat them as vectors of
characters.
Event keys are never integers, remove some code that only ran if
(integerp (event-key ce)).
Event keys are never numbers, don't check for that.
Don't create (menu-selection call-interactively function-name)
keystrokes for menu choices, #'character-to-event doesn't
understand that syntax, so nothing uses it.
Don't ever accept mouse events, #'character-to-event doesn't
accept our synthesising of them.
src/ChangeLog addition:
2013-07-10 Aidan Kehoe <kehoea@parhasard.net>
* keymap.c:
* keymap.c (key_desc_list_to_event):
Drop the allow_menu_events argument.
Don't accept lists starting with Qmenu_selection as describing
keys, nothing generates them in a way this function
understands. The intention is reasonable but the implementation
was never documented and never finished.
* keymap.c (syms_of_keymap):
Drop Qmenu_selection.
* events.c (Fcharacter_to_event):
* keymap.h:
Drop the allow_menu_events argument to key_desc_list_to_event.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Wed, 10 Jul 2013 14:14:30 +0100 |
parents | 576fb035e263 |
children | 9fae6227ede5 |
line wrap: on
line source
@c -*-texinfo-*- @c This is part of the XEmacs Lisp Reference Manual. @c Copyright (C) 1990, 1991, 1992, 1993 Free Software Foundation, Inc. @c See the file lispref.texi for copying conditions. @setfilename ../../info/dialog.info @node Dialog Boxes, Toolbar, Menus, Top @chapter Dialog Boxes @cindex dialog box @menu * Dialog Box Format:: * Dialog Box Functions:: @end menu @node Dialog Box Format @section Dialog Box Format A dialog box description is a list. @itemize @bullet @item The first element of the list is a string to display in the dialog box. @item The rest of the elements are descriptions of the dialog box's buttons. Each one is a vector of three elements: @itemize @minus @item The first element is the text of the button. @item The second element is the @dfn{callback}. @item The third element is @code{t} or @code{nil}, whether this button is selectable. @end itemize @end itemize If the callback of a button is a symbol, then it must name a command. It will be invoked with @code{call-interactively}. If it is a list, then it is evaluated with @code{eval}. One (and only one) of the buttons may be @code{nil}. This marker means that all following buttons should be flushright instead of flushleft. The syntax, more precisely: @example form := <something to pass to `eval'> command := <a symbol or string, to pass to `call-interactively'> callback := command | form active-p := <t, nil, or a form to evaluate to decide whether this button should be selectable> name := <string> partition := 'nil' button := '[' name callback active-p ']' dialog := '(' name [ button ]+ [ partition [ button ]+ ] ')' @end example @node Dialog Box Functions @section Dialog Box Functions @defun popup-dialog-box dbox-desc This function pops up a dialog box. @var{dbox-desc} describes how the dialog box will appear (@pxref{Dialog Box Format}). @end defun @xref{Yes-or-No Queries}, for functions to ask a yes/no question using a dialog box.