From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, Frediano Ziglio <fziglio@redhat.com>
Subject: [Qemu-devel] [PULL 1/5] vnc: send cursor when a new client is connecting
Date: Wed, 9 Mar 2016 10:04:33 +0100 [thread overview]
Message-ID: <1457514277-32408-2-git-send-email-kraxel@redhat.com> (raw)
In-Reply-To: <1457514277-32408-1-git-send-email-kraxel@redhat.com>
From: Frediano Ziglio <fziglio@redhat.com>
If you have hardware cursor and you are reconnecting the VNC client
you need to send the cursor. Failing to do so make the cursor invisible
till is changed.
Signed-off-by: Frediano Ziglio <fziglio@redhat.com>
Message-id: 1456929142-14033-1-git-send-email-fziglio@redhat.com
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
ui/vnc.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/ui/vnc.c b/ui/vnc.c
index 6cd6314..729f630 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -2046,6 +2046,9 @@ static void set_encodings(VncState *vs, int32_t *encodings, size_t n_encodings)
break;
case VNC_ENCODING_RICH_CURSOR:
vs->features |= VNC_FEATURE_RICH_CURSOR_MASK;
+ if (vs->vd->cursor) {
+ vnc_cursor_define(vs);
+ }
break;
case VNC_ENCODING_EXT_KEY_EVENT:
send_ext_key_event_ack(vs);
--
1.8.3.1
next prev parent reply other threads:[~2016-03-09 9:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 9:04 [Qemu-devel] [PULL 0/5] ui: add linux evdev support, vnc and console fixes Gerd Hoffmann
2016-03-09 9:04 ` Gerd Hoffmann [this message]
2016-03-09 9:04 ` [Qemu-devel] [PULL 2/5] input: linux evdev support Gerd Hoffmann
2016-03-09 9:04 ` [Qemu-devel] [PULL 3/5] input-linux: add option to toggle grab on all devices Gerd Hoffmann
2016-03-09 9:04 ` [Qemu-devel] [PULL 4/5] input-linux: add switch to enable auto-repeat events Gerd Hoffmann
2016-03-09 9:04 ` [Qemu-devel] [PULL 5/5] ui/console: add escape sequence \e[5, 6n Gerd Hoffmann
2016-03-10 5:00 ` [Qemu-devel] [PULL 0/5] ui: add linux evdev support, vnc and console fixes Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1457514277-32408-2-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=fziglio@redhat.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).