Re: [9front] vncs: some clients report 'bad hextile data'

Re: [9front] vncs: some clients report 'bad hextile data'

[cinap_lenrek]

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.

to really fix it you need to understand what realvnc's problem is... so
look there. then you can come up with a proper work arround.

--
cinap

Re: [9front] vncs: some clients report 'bad hextile data'

[Ethan Gardener]

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.

I could try that.

> to really fix it you need to understand what realvnc's problem is... so
> look there. then you can come up with a proper work arround.

Yeess, but it's closed source. :<  

Ah!  I could run TightVNC on my new laptop, it's open source.  It's a little clunkier but it will do.  Just tried it, it works.  I think I'll stick with TightVNC because A: I won't be using it much, and B: RealVNC no longer have a link to download their viewer on their front page.

Anecdotally, I haven't been using TightVNC on my desktop because Windows makes it fuzzy.  If you tell Windows to increase font size, it blurrily scales the display of programs which don't support it.  (KHM, are you laughing? :)  My desktop is Win7 so I can mitigate the problem by selecting a theme that looks like Windows 95 *eye-roll* :) but that doesn't work for TightVNC.  My laptop is Win10, they cleaned up the theming, so I've just set the font scale to 100% and settled for having to peer at menus.  It won't be too bad because I won't be using it as much as the desktop.

Re: [9front] vncs: some clients report 'bad hextile data' -- workaround found

[Ethan Gardener]

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.

Re: [9front] vncs: some clients report 'bad hextile data' -- workaround found

[Ethan Gardener]

On Sat, Feb 2, 2019, at 1:14 PM, Ethan Gardener wrote:
> 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.

My mistake, both viewer versions default to 8-bit without hextile.  Easily fixed with an option.