aboutsummaryrefslogtreecommitdiff
path: root/vnc.h
diff options
context:
space:
mode:
authorGerd Hoffmann <kraxel@redhat.com>2010-02-26 17:17:39 +0100
committerAnthony Liguori <aliguori@us.ibm.com>2010-03-09 08:47:27 -0600
commit7ffb82ca6e13feeb37b86a8223da691eff5ee922 (patch)
tree8115121a288e7e5fefe74a1e5c95d702b1cc5948 /vnc.h
parentbd87813e8c3adfa1c12f763b35b2dbacc7796f0d (diff)
downloadqemu-7ffb82ca6e13feeb37b86a8223da691eff5ee922.zip
qemu-7ffb82ca6e13feeb37b86a8223da691eff5ee922.tar.gz
qemu-7ffb82ca6e13feeb37b86a8223da691eff5ee922.tar.bz2
kbd keds: vnc
Use led status notification support in vnc. The qemu vnc server keeps track of the capslock and numlock states based on the key presses it receives from the vnc client. But this fails in case the guests idea of the capslock and numlock state changes for other reasons. One case is guest reboot (+ keyboard reset). Another case are more recent windows versions which reset capslock state before presenting the login screen. Usually guests use the keyboard leds to signal the capslock and numlock state to the user, so we can use this to better keep track of capslock and numlock state in the qemu vnc server. Also toggle the numlock and capslock states on keydown events (instead of keyup). Guests do the same. Signed-off-by: Gerd Hoffmann <kraxel@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'vnc.h')
-rw-r--r--vnc.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/vnc.h b/vnc.h
index ff9a699..0fc89bd 100644
--- a/vnc.h
+++ b/vnc.h
@@ -161,6 +161,7 @@ struct VncState
size_t read_handler_expect;
/* input */
uint8_t modifiers_state[256];
+ QEMUPutLEDEntry *led;
Buffer zlib;
Buffer zlib_tmp;