| commit | 53762ddb277c690e486d0e17b10591774248c8cf | |
| author | malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162> | |
| Mon, 1 Dec 2008 20:57:52 +0000 (1 20:57 +0000) | ||
| committer | malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162> | |
| Mon, 1 Dec 2008 20:57:52 +0000 (1 20:57 +0000) | ||
| tree | 8cf2c6c6971a39e5d08ae6570e16d149f9421c48 | treesnapshot (tar.gz zip) |
| parent | 429a8ed3844b04dd5d8a8eb88f021ed335dff1fa | commitdiff |
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
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
| vnc.c | diffblobblamehistory |