[Bug 93249] key event going to display even with keyboard ungrabbed
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Dec 9 09:11:43 PST 2015
https://bugs.freedesktop.org/show_bug.cgi?id=93249
--- Comment #22 from Zeeshan Ali <zeenix at gmail.com> ---
(In reply to Marc-Andre Lureau from comment #21)
> (In reply to Zeeshan Ali from comment #20)
> > I'm sure, you completely misunderstood me. In the quoted context that you
> > didn't paste, I was talking about showing some UI to ensure user knows
> > keyboard is grabbed not wonder if keyboard is not working after (potentially
> > accidently) hitting the keyboard ungrab combo. I doubt SPICE does that
> > already.
>
> I fail to understand that.
I'm not sure about the relevance of the quoted text above to what you are
saying below.
> spice-gtk input behaviour is rather simple:
> - has no focus -> no input
> - has focus -> gtk input is handled by the widget
And this is normal for most widget which do not need the concept of 'keyboard
grab'.
> - has focus + grab -> all keyboard input (including "system keys", except
> vt-switch) is handled by the widget
That is fine too.
The issue here is has_focus + ungrabbed case. Like I said before, If user
explicitly requested keyboard ungrab (and provided spice and/or App does make
sure user knows keyboard in ungrabbed currently), all key events should really
go to client/host and none to guest.
> When the widget has the focus, there is no handling of focus chain built-in
> the widget, but like any other accelerator, you can set one in your app.
I don't know what you mean. Boxes has accelerators for display state but they
currently don't work even when keyboard is ungrabbed and that's the issue here.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/spice-bugs/attachments/20151209/67033b81/attachment.html>
More information about the spice-bugs
mailing list