From: Gerd Hoffmann <kraxel@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 0/4] ui: improve precision of VNC desktop resizing
Date: Fri, 12 Mar 2021 11:36:18 +0100 [thread overview]
Message-ID: <20210312103618.wuddf4iwjcub4zhm@sirius.home.kraxel.org> (raw)
In-Reply-To: <20210311182957.486939-1-berrange@redhat.com>
On Thu, Mar 11, 2021 at 06:29:53PM +0000, Daniel P. Berrangé wrote:
> Currently when resizing the VNC desktop we get a thin black bar down the
> right hand side of the screen 93% of the time, because the VNC server
> rounds up the display to a multiple of 16. This series solves this
> problem by fixing the separation between the server surface dimensions
> (which are important for dirty bitmap tracking) and the client desktop
> size (which is what the client actually renders).
>
> Daniel P. Berrangé (4):
> ui: add more trace points for VNC client/server messages
> ui: avoid sending framebuffer updates outside client desktop bounds
> ui: use client width/height in WMVi message
> ui: honour the actual guest display dimensions without rounding
Added to ui patch queue.
thanks,
Gerd
prev parent reply other threads:[~2021-03-12 10:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 18:29 [PATCH 0/4] ui: improve precision of VNC desktop resizing Daniel P. Berrangé
2021-03-11 18:29 ` [PATCH 1/4] ui: add more trace points for VNC client/server messages Daniel P. Berrangé
2021-03-11 21:12 ` Marc-André Lureau
2021-03-11 18:29 ` [PATCH 2/4] ui: avoid sending framebuffer updates outside client desktop bounds Daniel P. Berrangé
2021-03-11 21:15 ` Marc-André Lureau
2021-03-11 18:29 ` [PATCH 3/4] ui: use client width/height in WMVi message Daniel P. Berrangé
2021-03-11 21:19 ` Marc-André Lureau
2021-03-11 18:29 ` [PATCH 4/4] ui: honour the actual guest display dimensions without rounding Daniel P. Berrangé
2021-03-12 6:48 ` Marc-André Lureau
2021-03-12 10:36 ` Gerd Hoffmann [this message]
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=20210312103618.wuddf4iwjcub4zhm@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=berrange@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).