[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-openjfx-dev
Subject:    Re: enableInputMethodEvents
From:       Thiago_Milczarek_SayĆ£o <thiago.sayao () gmail ! com>
Date:       2022-06-29 16:40:12
Message-ID: CAAP_wuk070tm0YNqb11qDS86Z31nT8nBFC0NYikac-rVVZ-piA () mail ! gmail ! com
[Download RAW message or body]

For information, "XIM" got removed from gtk

https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1195

I took a look at it, and it's a really odd api as compared to modern
options such as Xinput2.

There are the original "X input methods", then Xinput then Xinput2, the
later supports touch devices and it's "modern".

It also explains why some things break on some distros - it may be using
older input method handling. It affects mouse (pointer), keyboard and touch
events.

Xinput2 dates October, 2009.
https://www.x.org/releases/X11R7.7/doc/inputproto/XI2proto.txt

Cheers



Em sex., 17 de jun. de 2022 =C3=A0s 10:37, Thiago Milczarek Say=C3=A3o <
thiago.sayao@gmail.com> escreveu:

> Hi,
>
> View.java has this method (enableInputMethodEvents) with no documentation=
.
>
> On Linux it uses X input method events.
>
> But I can't figure out why exactly it must be enabled. When it's not
> enabled, there are input method events anyway....
> And it seems (at least on Linux) to do the same thing for keyboard events=
,
> but using Xlib directly instead of GDK.
>
> It seems to touch composition - that is when multiple keypresses are
> needed to generate a symbol, for example, accented characters.
>
> Why does it exist?
>
> -- Thiago.
>
>
>
>

[Attachment #3 (text/html)]

<div dir="ltr">For information, &quot;XIM&quot; got removed from gtk  \
<div><br></div><div><a \
href="https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1195">https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/1195</a></div><div><br></div><div>I \
took a look at it, and it&#39;s a really odd api as compared to modern options such \
as Xinput2.</div><div><br></div><div>There are the original &quot;X input \
methods&quot;, then Xinput then Xinput2, the later supports touch devices and \
it&#39;s &quot;modern&quot;.</div><div><br></div><div>It also explains why some \
things break on some distros - it may be using older input method handling. It \
affects mouse (pointer), keyboard and touch events.</div><div><br></div><div>Xinput2 \
dates October, 2009.</div><div><a \
href="https://www.x.org/releases/X11R7.7/doc/inputproto/XI2proto.txt">https://www.x.or \
g/releases/X11R7.7/doc/inputproto/XI2proto.txt</a><br></div><div><br></div><div>Cheers</div><div><div><br></div><div><br></div></div></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">Em sex., 17 de jun. de 2022 Ć s \
10:37, Thiago Milczarek SayĆ£o &lt;<a \
href="mailto:thiago.sayao@gmail.com">thiago.sayao@gmail.com</a>&gt; \
escreveu:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div \
dir="ltr">Hi,<br><div><br></div><div>View.java has this method \
(enableInputMethodEvents) with no documentation.</div><div><br></div><div>On Linux it \
uses X input method events.</div><div><br></div><div>But I can&#39;t figure out why \
exactly it must be enabled. When it&#39;s not enabled, there are input method events \
anyway....</div><div>And it seems (at least on Linux) to do the same  thing for \
keyboard events, but using Xlib directly instead of GDK.</div><div><br></div><div>It \
seems to touch composition - that is when multiple keypresses are needed to generate \
a symbol, for example, accented characters.</div><div><br></div><div>Why does it \
exist?</div><div><br></div><div>-- \
Thiago.</div><div><br></div><div><br></div><div><br></div></div> </blockquote></div>



[prev in list] [next in list] [prev in thread] [next in thread]