From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 57020@debbugs.gnu.org
Subject: bug#57020: 29.0.50; Mouse wheel stops working
Date: Mon, 08 Aug 2022 10:36:23 +0800 [thread overview]
Message-ID: <87iln3sbq0.fsf@yahoo.com> (raw)
In-Reply-To: <87zggfv6ma.fsf@web.de> (Michael Heerdegen's message of "Mon, 08 Aug 2022 03:58:21 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Po Lu <luangruo@yahoo.com> writes:
>
>> printf ("%g\n", delta);
>>
>> afterwards? Then, please see if any (and what) values are printed once
>> the mouse wheel stops working.
>
> Short answer: nothing is printed.
>
> Before the issue starts happening, I see -1 and +1 for each wheel
> "click" and lots of 1.79769e+308 values when moving the mouse.
>
> Once scrolling stopped working, mouse wheel turning leads to no output
> any more (but the 1.79769e+308 values are still printed).
>
> What I was also noticing: when turning the mouse wheel over the scroll
> bar, there is a visual feedback: it looks like the scroll bar would lead
> to a scroll (the bar moves), but scrolling is not happening, the buffer
> text stands still. Also that is happening without output for DELTA.
>
> Michael.
Hmm, thanks. Could you also add the following instrumentation to that
code, like such:
device = xi_device_from_id (dpyinfo, xev->deviceid);
if (!device)
{
fprintf (stderr, "device not found, %d\n", xev->deviceid);
goto XI_OTHER;
}
and see if that is ever printed when wheel movement stops working?
next prev parent reply other threads:[~2022-08-08 2:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 22:53 bug#57020: 29.0.50; Mouse wheel stops working Michael Heerdegen
2022-08-07 1:56 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-07 2:07 ` Michael Heerdegen
2022-08-07 2:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-08 1:58 ` Michael Heerdegen
2022-08-08 2:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-09 0:13 ` Michael Heerdegen
2022-08-09 0:24 ` Michael Heerdegen
2022-08-09 0:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-09 3:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-09 3:48 ` Michael Heerdegen
2022-08-09 5:11 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87iln3sbq0.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=57020@debbugs.gnu.org \
--cc=luangruo@yahoo.com \
--cc=michael_heerdegen@web.de \
/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).