diff options
author | malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162> | 2008-12-01 20:57:52 +0000 |
---|---|---|
committer | malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162> | 2008-12-01 20:57:52 +0000 |
commit | 53762ddb277c690e486d0e17b10591774248c8cf (patch) | |
tree | 8cf2c6c6971a39e5d08ae6570e16d149f9421c48 /vnc.c | |
parent | 429a8ed3844b04dd5d8a8eb88f021ed335dff1fa (diff) | |
download | qemu-53762ddb277c690e486d0e17b10591774248c8cf.zip qemu-53762ddb277c690e486d0e17b10591774248c8cf.tar.gz qemu-53762ddb277c690e486d0e17b10591774248c8cf.tar.bz2 |
Reset the key modifiers upon client connect
VNC should not maintain modifer state upon reconnects With some window
managers/vnc clients it will only see a key down event for a modifier
followed by immediate disconnect(think Alt-F4), with a net effect of
subsequently connected clients operating as if the modifier was never
released.
git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5851 c046a42c-6fe2-441c-8c8c-71466251a162
Diffstat (limited to 'vnc.c')
-rw-r--r-- | vnc.c | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -2246,6 +2246,7 @@ static void vnc_connect(VncState *vs) vs->has_hextile = 0; vs->ds->dpy_copy = NULL; vnc_update_client(vs); + reset_keys(vs); } static void vnc_listen_read(void *opaque) |