2013/9/26 Ran Benita <ran...@gmail.com>: [snip]
> > The information you need, if you want to use the key-down approach > (which is the only one I can think of), is whether e.g. the Left Shift > key is down at any given moment. This keys-state information is kept on > the compositor, but now you need to reconstruct it on the client. The > way to do it is as I outlined above, i.e. wl_keyboard.enter event, which > gives you a wl_array of all the keys which are pressed + > wl_keyboard.key events, which allow you to keep this array in sync. > This is what I was thinking about. > (Though by a quick look at the Weston code, it might be that it sends > key-down events for all the keys which are down when the focus is > changed, that is, it replays what happened to get to the current state. > So maybe you don't need the information in the wl_keyboard.enter after > all, only the key events with an initial empty array. It should be easy > to check which way is it). > But this is an weston implementation detail, I guess, other compositors may not have the same behavior. -- Best Regards, Wander Lairson Costa _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel