9front - general discussion about 9front
 help / color / mirror / Atom feed
From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] vnc: fix farsi key symbols
Date: Thu, 18 May 2023 20:32:15 -0700	[thread overview]
Message-ID: <8B2B0619A13B0AC8D362E6511C865916@smtp.pobox.com> (raw)
In-Reply-To: <C62AAED1F5A16AA0BAFC302324B84C80@eigenstate.org>

Quoth ori@eigenstate.org:
> Quoth unobe@cpan.org:
> > Oh, sorry for misunderstanding; that makes sense.  I was looking at
> > the RFB protocol and saw there is a way to specify the desktop size,
> > so I think it can be set from the client-side too. 
> 
> We already do this -- see MSetDesktopSize in
> /sys/src/cmd/draw.c:/^requestupdate
> 
> 

Thanks ori.

Indeed, I saw that.  However, it only occurs if the server lets the
client resize the frame buffer and the dimensions of the rc window is
not equal to the server's frame buffer.  In the case of OS X's stock
VNC server, I confirmed that the server doesn't allow resizing (it
doesn't send the ExtendedDesktopSize message), so apparently that
won't work for my situation.

Maybe I want vncv to have a vertical and horizontal scroller to view
different areas of the frame buffer, or some other mechanism to view
different portions of the screen.  Or perhaps scale the raw buffer to
a pre-determined dimension (which I think might be more complicated).
Anyway, one other thing on the ever-growing todo/wish list, and which
will be a learning experience.


  reply	other threads:[~2023-05-19  3:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  0:43 unobe
2023-05-17  2:08 ` Jacob Moody
2023-05-17  2:38   ` unobe
2023-05-17  4:31     ` Jacob Moody
2023-05-17 19:37       ` unobe
2023-05-17 14:35     ` ori
2023-05-17 19:38       ` unobe
2023-05-17 20:15         ` ori
2023-05-17 20:40           ` unobe
2023-05-18 10:27             ` ori
2023-05-19  3:32               ` unobe [this message]
2023-05-24 13:34 ` mkf9

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=8B2B0619A13B0AC8D362E6511C865916@smtp.pobox.com \
    --to=unobe@cpan.org \
    --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).