procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Document a GDK misdesign interfering with touch screens and menus

Browse source 
* etc/PROBLEMS (Runtime problems specific to PGTK): Document a
misdesign preventing menus from being displayed in response to
touch screen events.
This commit is contained in:
Po Lu 2024-06-02 16:17:34 +08:00
parent 1ea398e8f1
commit 50c4feb132
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
etc/PROBLEMS
View file

@ -3512,6 +3512,22 @@ Compose key to stop working.
On X Windows, users should not use Emacs configured with PGTK, since
this and many other problems do not exist on the regular X builds.
** On occasion, menus cannot be activated by touch screen events.
Menus might not be displayed after a mode-line item, or another command
that produces a menu, is activated by touch screen events. This is the
product of several bugs or misdesigns in the GDK Wayland backend which
cannot be circumvented by Emacs. Specifically, Wayland denies clients
that cannot provide a sufficiently recent event serial number the
ability to display pop-up windows, but GDK only considers the serial
numbers of touch screen events when their touch sequences remain active,
and, as touch screen activity is not registered by Emacs until after the
toolkit's delivery of touch sequences completes, by the time
`x-popup-menu' is called, the only eligible event serials are those of
the last keyboard event and the last mouse event, which will not suffice
if Wayland has received pop-up or drag-and-drop requests from other
clients since their generation.
* Runtime problems specific to Android
** Text displayed in the default monospace font looks horrible.