all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: feature/android a496509ced 1/2: Update Android port
Date: Wed, 16 Aug 2023 20:21:33 +0800	[thread overview]
Message-ID: <87il9fjhyq.fsf@yahoo.com> (raw)
In-Reply-To: <jwv5y5fkxa4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Wed, 16 Aug 2023 08:12:25 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Could you explain why for touchscreen events you made `event-end` and
> `event-start` return "posn-at-point" (which seems positively useless),
> forcing you in turn to add ad-hoc handling in `widget-event-point` and
> to introduce a new `widget-event-start`?

Actually, the cdadr of a touchscreen-begin or touchscreen-end event is
its mouse position list.

> I understand that touchscreen events may have multiple posns, but it
> seems that making `event-end` and `event-start` do what
> `widget-event-point` and `widget-event-start` do would be better than
> what we have now, no?

I recall moving the code for processing touch screen events from
widget.el to subr.el.  I probably neglected to remove the old code from
widget.el in the process.

Thanks.




  reply	other threads:[~2023-08-16 12:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <167413804086.19235.17391196197706660128@vcs2.savannah.gnu.org>
     [not found] ` <20230119142043.05B19C00613@vcs2.savannah.gnu.org>
2023-08-16 12:12   ` feature/android a496509ced 1/2: Update Android port Stefan Monnier
2023-08-16 12:21     ` Po Lu [this message]
2023-08-16 12:35       ` Stefan Monnier
2023-08-16 12:41         ` Po Lu
2023-08-16 13:44           ` Stefan Monnier
2023-08-16 14:15             ` Po Lu
2023-08-16 15:03               ` Stefan Monnier
2023-08-17  0:30                 ` Po Lu
2023-08-17  3:02                   ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87il9fjhyq.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.