On Tue, Jan 08, 2008 at 10:20:50AM -, James Weatherall wrote:
In practice desktop names are currently ASCII-only, but new standard RFB
protocol elements all use UTF-8 for string data. I'd recommend that
third-party encodings, etc also use UTF-8 for string data for consistency.
So, Peter,
On Tue, Jan 08, 2008 at 10:20:50AM -, James Weatherall wrote:
In practice desktop names are currently ASCII-only, but new standard RFB
protocol elements all use UTF-8 for string data. I'd recommend that
third-party encodings, etc also use UTF-8 for string data for
consistency.
So,
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Peter Cstrand
Sent: 07 January 2008 19:13
To: Peter Rosin
Cc: [EMAIL PROTECTED]; vnc-list@realvnc.com
Subject: Re: Protocol extension for changing desktop name on the fly
[snip]
Btw, one thing that I miss somewhat is a character
I have a working implementation now, using a new pseudo encoding called
DesktopName. It's pretty similiar to the existing DesktopSize
encoding.
However, it seems like RealVNC will not allocate an encoding number for my
new encoding. There position was that this should be a TightVNC-specific
PROTECTED]
Subject: Re: Protocol extension for changing desktop name on the fly
I have a working implementation now, using a new pseudo
encoding called DesktopName. It's pretty similiar to the
existing DesktopSize
encoding.
However, it seems like RealVNC will not allocate an encoding
number
On Mon, 7 Jan 2008, James Weatherall wrote:
You may wish to check your email - you were allocated pseudo-encoding
number -307 earlier this afternoon.
This is excellent news. Thank you for your cooperation.
Rgds,
---
Peter Cstrand ThinLinc Chief Developer
Cendio AB
On Mon, Jan 07, 2008 at 05:02:25PM +0100, Peter Estrand wrote:
NumberName
-306 DesktopName pseudo-encoding
Bzzzt -307 :-)
Here's the description:
A client which requests the DesktopName pseudo-encoding is declaring that
it is capable of coping with a change of the desktop name.
On Mon, 7 Jan 2008, Peter Rosin wrote:
A client which requests the DesktopName pseudo-encoding is declaring
that
it is capable of coping with a change of the desktop name. The server
changes the desktop name by sending a pseudo-rectangle with the
DesktopName pseudo-encoding in an update.
I'd like to be able to change the desktop name on the fly so that a
vncconfig -set desktop=something immediately changes the vncviewer
window title.
Currently, the desktop name (as specified by the -desktop option to
Xvnc) remains static during the entire lifespan of the Xvnc
process. If you
