From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Mouse click vs drag
Date: Tue, 22 Sep 2020 12:24:32 -0400 [thread overview]
Message-ID: <jwvy2l1wzk0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87pn6dhki7.fsf@iki.fi
> Clicks are difficult to achieve with hires display, because the mouse
> cursor tends to move a couple of pixels or so when pressing and
> releasing mouse buttons. Eg. in Customize buffers it is difficult to
> push "Apply" or "Apply and Save" buttons.
IIRC, the "same position" check is not looking at pixel position but
character position, so either my recollection is faulty or there's
something else at play.
Stefan
next prev parent reply other threads:[~2020-09-22 16:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 15:57 Mouse click vs drag Petteri Hintsanen
2020-09-22 16:24 ` Stefan Monnier [this message]
2020-09-22 17:07 ` Eli Zaretskii
2020-09-22 16:38 ` Eli Zaretskii
2020-09-22 17:08 ` Petteri Hintsanen
2020-09-22 17:12 ` Eli Zaretskii
2020-09-22 17:50 ` Petteri Hintsanen
-- strict thread matches above, loose matches on Subject: below --
2020-09-23 8:09 Anders Munch
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=jwvy2l1wzk0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=help-gnu-emacs@gnu.org \
/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).