From: Glenn Morris <rgm@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 1261@emacsbugs.donarmstrong.com, Stephen Berman <stephen.berman@gmx.net>
Subject: bug#1261: 23.0.60; diary-insert-entry and mouse-autoselect-window
Date: Mon, 03 Nov 2008 17:17:05 -0500 [thread overview]
Message-ID: <98prlcihem.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <4906C864.9020103@gmx.at> (martin rudalics's message of "Tue, 28 Oct 2008 09:08:04 +0100")
I tried to debug this some more.
As I said, it only happens with the GTK toolkit, not athena. The GTK
version seems to call handle_one_xevent many more time than the athena
version (event_handler_gdk?). I tried putting a breakpoint at line
6734 of xterm.c, but it was called so often as to be almost unusable.
When I managed to reach the point of pressing mouse-3 in the calendar
window and brought up the calendar menu, gdb was invoked, but my X
session would no longer accept mouse or keyboard events, so I could
not switch to my gdb window. :(
So then I just printed XWINDOW(last_window) to stderr.
It seems that the GTK toolkit associates a popup menu with the topmost
window in a frame, irrespective of which window the menu actually lies
in front of.
When I repeat the initial experiment with the calendar window in the
_topmost_ (it is normally in the lowest) window of the frame (this
requires making the frame and calendar window tall enough that the
mouse cursor stays inside the calendar when selecting "Insert diary
entry"), there is no problem.
next prev parent reply other threads:[~2008-11-03 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-27 16:18 bug#1261: 23.0.60; diary-insert-entry and mouse-autoselect-window Stephen Berman
2008-10-27 17:25 ` martin rudalics
2008-10-27 20:42 ` Stephen Berman
2008-10-28 1:17 ` Stefan Monnier
2008-10-28 8:08 ` martin rudalics
2008-11-03 22:17 ` Glenn Morris [this message]
2008-11-04 7:36 ` martin rudalics
2008-11-04 18:51 ` Glenn Morris
2008-11-04 20:41 ` Stephen Berman
2008-10-27 21:34 ` Glenn Morris
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=98prlcihem.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=1261@emacsbugs.donarmstrong.com \
--cc=rudalics@gmx.at \
--cc=stephen.berman@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).