From: Ethan Gardener <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] vncs: some clients report 'bad hextile data' -- workaround found
Date: Sat, 02 Feb 2019 13:14:06 +0000 [thread overview]
Message-ID: <1549113246.2990995.1649262184.54888F5D@webmail.messagingengine.com> (raw)
In-Reply-To: <90792F84B66CE28B8F654484B130BD75@felloff.net>
On Thu, Jan 31, 2019, at 6:04 PM, cinap_lenrek@felloff.net wrote:
> not sure if this is really a issue with the hextile encoding. you could
> comment out the EncHextile case in setencoding() in vncs.c to exclude it.
Did this, it works now. On my LAN there's no perceptible delay or anything, so it can stay like this.
Funnily enough, with hextile disabled, RealVNC 6.19 works better than 6.17. Pale colors disappear in 6.17. Maybe they broke hextile when they fixed that bug, or something.
It's no wonder Unix VNC servers and clients have so many options.
next prev parent reply other threads:[~2019-02-02 13:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 18:04 [9front] vncs: some clients report 'bad hextile data' cinap_lenrek
2019-02-01 9:29 ` Ethan Gardener
2019-02-02 13:14 ` Ethan Gardener [this message]
2019-02-02 13:22 ` [9front] vncs: some clients report 'bad hextile data' -- workaround found Ethan Gardener
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=1549113246.2990995.1649262184.54888F5D@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.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).