blei42 at gmail.com
Wed Jul 11 02:53:27 PDT 2012
I'm still slowly getting the hang of how wayland works, but I think
I've spotted a problem: only one client at a time should bind to the
input_method global. Else we don't know who we send events to.
This has the consequence that the create_text_model request has to be
moved somewhere else, either a new interface (text_model_manager?
yuck, better names are welcome) or moved to an already existing
interface (no idea which one would be suitable). Thoughts?
On Tue, Jul 10, 2012 at 4:44 PM, Jan Arne Petersen
<jpetersen at openismus.com> wrote:
> On 07/10/2012 03:49 PM, Philipp Brüschweiler wrote:
>> Thanks for your answer. I have finally managed to get something going,
>> using a wl_keyboard_grab. This seems to work, but has the problem that
>> it completely grabs the text_model until the text_model gets
> Yes, that is why the text_model needs to be deactivated when the surface
> looses focus (see my other email).
>> I have looked at wl_keyboard_set_focus a bit, and it
>> seems to me that for further work, the input method system would have
>> to be integrated into wayland so as to make sure that the focused
>> surface doesn't loose focus but the key events still get redirected to
>> the input method.
> I do not really understand in which case the surface should not loose focus?
> Jan Arne
More information about the wayland-devel