From: "David Vanderschel" <DJV4@Austin.RR.com>
Subject: elisp, mouse-tracking: gracefully NOT handling events
Date: Tue, 08 Jun 2004 19:38:14 GMT [thread overview]
Message-ID: <GAoxc.57584$mQ4.54216@fe2.texas.rr.com> (raw)
I have a program in which I am using track-mouse. It
turns out that mouse events are not the only events
you can get in a track-mouse loop. My program is not
prepared to handle all of them. (I don't know how
many other potential event types there are in this
context, but I am sure that I do not want to learn how
to properly treat all of them.) In the face of an
event my program does not understand, it can and does
abort its current operation with no difficulty.
(Indeed, that is a normal sort of occurrence for other
reasons as well.) However, it may be that such an
unrecognized event could occur, the event is
significant, and failure to deal with it could be
harmful to the 'system'. It seems to me that I need a
system function to call when I don't know what to do
with an event. The idea is, "Take this event. I did not
know what to do with it, so please do with it
whatever you would have done with it had I not been in
a track-mouse loop." Is there such a function?
(Failing that, it seems like there ought to be a way
to tell the system which types of events you are
prepared to handle in a track-mouse loop so you won't
get events you don't understand.)
Regards,
David V.
next reply other threads:[~2004-06-08 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-08 19:38 David Vanderschel [this message]
2004-06-08 21:52 ` elisp, mouse-tracking: gracefully NOT handling events David Kastrup
2004-06-09 16:36 ` David Vanderschel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='GAoxc.57584$mQ4.54216@fe2.texas.rr.com' \
--to=djv4@austin.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).