[Spice-devel] [patch 0/2] vdagent KEYVAL extension
Marc-André Lureau
mlureau at redhat.com
Thu Oct 10 16:59:24 CEST 2013
----- Original Message -----
> > Ok, so I will add more space for scancodes. I have further optimized my
> > patch,
> > and I currently use:
> >
> > message {
> > uint32 keysym;
> > uint32 scancode_down;
> > uint32 scancode_up;
> > } @ctype(SpiceMsgcKeyX11Keysym) key_x11_keysym;
If you really want to send scancode, do it the same way as "Data key_scancode" for arbitrary sequence.
Why did you drop the flags in the end?
> Another advantage is that a client could request scancode generation at
> server side.
> This is useful for the javascript/java client, because they do not have
> access to scancodes.
>
> The server (qemu) can synthesize the scancode from the keysym (code for that
> already
> exists in qemu for vnc).
I think I understand what you mean, even though I think it becomes weird server cases...
More information about the Spice-devel
mailing list