At 11:45 AM 11/28/01 +0900, Stephen J. Turnbull wrote:
Not according to the docs:
------------------------------------------------------------------------
`get-popup-menu-response' is a compiled Lisp function
-- loaded from "/home/steve/Projects/XEmacs/Builds/21.4/lisp/menubar.elc"
(get-popup-menu-response MENU-DESC &optional EVENT)
Documentation:
Pop up the given menu and wait for a response.
This blocks until the response is received, and returns the misc-user
event that encapsulates the response. To execute it, you can do
(funcall (event-function response) (event-object response))
If no response was received, nil is returned.
Right, but the way it acomplishes this is that the popup-menu enqueues the
event and then get-popup-menu-response dequeues the event from
unread-command-events relying on being able to get to it before the event
was processed. Unfortunately, I think some of the modal loop code (or
something) in mswindows can cause events to get processed in the meantime.
andy