<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - key event going to display even with keyboard ungrabbed"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93249#c36">Comment # 36</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - key event going to display even with keyboard ungrabbed"
href="https://bugs.freedesktop.org/show_bug.cgi?id=93249">bug 93249</a>
from <span class="vcard"><a class="email" href="mailto:zeenix@gmail.com" title="Zeeshan Ali <zeenix@gmail.com>"> <span class="fn">Zeeshan Ali</span></a>
</span></b>
<pre>(In reply to Pavel Grunt from <a href="show_bug.cgi?id=93249#c35">comment #35</a>)
<span class="quote">> I think Marc-Andre mentioned it and made it clear. When you press the ungrab
> combo the keys does not go to the guest, they go to the app which has the
> focus.</span >
Yes he did but I also pointed out that this rule is not so set in stone.
Spice-gtk is a bit special:
1. You normally want *all* keyboard events to go to guest. If you compare it to
99% of widgets out there, they don't eat all keyboard events even if they are
focused.
2. SpiceGtk already has this concept of keyboard-ungrab and I don't know of any
gtk+ widget (except for vnc which is the same case) that has this concept. I'm
not asking for a new state but rather extending the idea of this
keyboard-ungrab to include all keys, as users would expect it to be, not just
system keys.
Since users will be expecting that in all UIs, I strongly recommend this be
solved by spice-gtk, rather than be done separately in every app that uses
spice-gtk.
<span class="quote">> If you want to stop receiving the keys, just use the disable inputs
> property [0], as Marc-Andre said in the <a href="show_bug.cgi?id=93249#c4">comment 4</a>.</span >
That also disables mouse input and that's not at all what I want.
I looked into implementing it in Boxes yesterday and it's doable by switching
focus to event_box that contains the SpiceGtk widget on keyboard ungrab and
undoing that on receiving ungrab keys so it's not really a matter of "if Boxes
can do it" but rather "Whether Boxes should do it".</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>