unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Petteri Hintsanen <petterih@iki.fi>
To: help-gnu-emacs@gnu.org
Subject: Re: Mouse click vs drag
Date: Tue, 22 Sep 2020 20:50:12 +0300	[thread overview]
Message-ID: <875z85snll.fsf@iki.fi> (raw)
In-Reply-To: <837dslwxa3.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 22 Sep 2020 20:12:36 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> What did you try?  For a mouse-movement NOT to be interpreted as a
> mouse-drag, the movement must be smaller than double-click-fuzz AND
> the mouse pointer should stay on the same buffer position.

I did:

  $ emacs -Q

  C-h v double-click-fuzz RET

  {click on "customize"}

  {change "Double Click Fuzz" to 30}

  {click on "Apply", verify that State changes to "SET for current
   session only."}

  {click on "Revert...", slightly moving the mouse [less than 30 px]
   between button press and release}

Expected result: "Reset settings" popup appears.

Actual result: Nothing happens.




But you’re right, increasing double-click-fuzz has the desired effect in
other "clickable" places like Speedbar and Gnus Summary buffer.  This is
great and just what I was looking for.  Maybe widgets do not respect
double-click-fuzz for some reason?

I see this behaviour is explained in double-click-fuzz docstring ("This
variable is also the threshold for motion of the mouse to count as a
drag").  Too bad I couldn’t find that myself.

Thanks for your time.
Petteri



  reply	other threads:[~2020-09-22 17:50 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
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 [this message]
  -- 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=875z85snll.fsf@iki.fi \
    --to=petterih@iki.fi \
    --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).