2013/9/27 Daniel Stone <dan...@fooishbar.org>: > Hi, > > On 27 September 2013 03:30, Ran Benita <ran...@gmail.com> wrote: >> On Thu, Sep 26, 2013 at 06:46:02PM -0500, Jason Ekstrand wrote: >>> Looking at weston's input.c, I am not seeing any evidence that it sends any >>> key events due to an enter. It does resend the modifiers, but that's >>> different. It doesn't make sense to me that you would send the currently >>> depressed keys as an array and then send them again one-at-a-time. >> >> Hi Jason, thanks for looking. >> >> Right, for some reason I misread the loop in notify_keyboard_focus_in() >> to send key events. So there's no undefined behavior here; all the >> better. The enter + key events like I said initially should work well. > > Indeed, if you want to test for those. This was kind of the problem > our primary/secondary modifiers plan was supposed to fix: have a set > of 'first-class' modifiers such as Shift, Control, etc, which were > meaningful for key interpretation, as with today. But then also add a > set of secondary modifiers which are strictly advisory and meaningless > on their own, e.g. LShift, RShift, etc. But I haven't had the time to > implement this. >
If this will be implemented in the future, I think I will handle the *Shift* modifier as *LShift* meanwhile. -- Best Regards, Wander Lairson Costa _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
