Re: [gtk-vnc-devel] gtk-vnc trouble
- From: Gerd Hoffmann <kraxel redhat com>
- To: "Daniel P. Berrange" <berrange redhat com>
- Cc: gtk-vnc-devel <gtk-vnc-devel lists sourceforge net>
- Subject: Re: [gtk-vnc-devel] gtk-vnc trouble
- Date: Wed, 22 Aug 2007 18:20:20 +0200
Daniel P. Berrange wrote:
> I'm not too familiar with all the horrible details of keycode/keymaps
> wrt to VNC & virt, but sounds like a VNC extension for sending raw
> keycodes might be best approach, pushing off the translation proiblem to
> the remote end ?
That pretty much depends on what level you are operating on ...
For Xvncserver keysyms work perfectly fine because the X apps expect
keysyms from the X-Server anyway.
For something like qemu which operates one level below and needs to send
untranslated keycodes to the guest os raw keycodes obviously work best.
Current approach in qemu is to translate the keysyms back to the
keycodes, which sort-of works. But this back-and-forth translating is a
horrible mess. Just sending us keysyms like I did in my app doesn't
work perfect either because you can't send keys which don't exist on a
us keyboard then.
>> I see it grab all the time and vnc_display_set_*_grab(widget, FALSE)
>> doesn't turn it off.
>
> Oooh - are you running against a QEMU vnc server perhaps ?
Yes.
>> mainloop runs inbetween due to user interaction being needed (there is a
>> "connect ..." menu entry).
>
> Ok that's odd - is your client app code around anywhere public to test with ?
http://dl.bytesex.org/releases/xenwatch/
cheers,
Gerd
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]