[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: feature/android a496509ced 1/2: Update Android port
From: |
Po Lu |
Subject: |
Re: feature/android a496509ced 1/2: Update Android port |
Date: |
Wed, 16 Aug 2023 20:21:33 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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.
- Re: feature/android a496509ced 1/2: Update Android port, Stefan Monnier, 2023/08/16
- Re: feature/android a496509ced 1/2: Update Android port,
Po Lu <=
- Re: feature/android a496509ced 1/2: Update Android port, Stefan Monnier, 2023/08/16
- Re: feature/android a496509ced 1/2: Update Android port, Po Lu, 2023/08/16
- Re: feature/android a496509ced 1/2: Update Android port, Stefan Monnier, 2023/08/16
- Re: feature/android a496509ced 1/2: Update Android port, Po Lu, 2023/08/16
- Re: feature/android a496509ced 1/2: Update Android port, Stefan Monnier, 2023/08/16
- Re: feature/android a496509ced 1/2: Update Android port, Po Lu, 2023/08/16
- Re: feature/android a496509ced 1/2: Update Android port, Stefan Monnier, 2023/08/16