<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c38">Comment # 38</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 <a class="email" href="mailto:zeenix@gmail.com" title="Zeeshan Ali <zeenix@gmail.com>"> Zeeshan Ali</a> <pre>(In reply to Marc-Andre Lureau from <a href="show_bug.cgi?id=93249#c37">comment #37</a>) > (In reply to Zeeshan Ali from <a href="show_bug.cgi?id=93249#c36">comment #36</a>) > > (In reply to Pavel Grunt from <a href="show_bug.cgi?id=93249#c35">comment #35</a>) > > > 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. > > > > 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. > > 99% is a bit over-estimated, all input widget allowing you to type is not > 1%... > > > 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. > > Imho it's tricky to change spice-gtk keyboard behaviour at this point > without breaking something, but perhaps something clever could be done, but > it needs careful thinking and testing. I would rather like to see that > behaviour adopted by a few apps before burring it in spice-gtk default > behavour or API. Sure, it could be a behaviour explicitly requested by apps for now. My advice would be a simple boolean property that changes the "keyboard ungrab" to include all keys but I'm open to other API suggestions. I offer Boxes as the first Guinea pig for that. > > > 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>. > > > > That also disables mouse input and that's not at all what I want. > > That's really broken to me. Having mouse input but no keyboard, I would > immediately wonder what is wrong with the VM and how to solve it. Yeah, I realized that later. However, as I said on IRC, that doesn't help me since my event_box can't receive key events unless focus is switched to it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>