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
Peter,
You may wish to check your email - you were allocated pseudo-encoding number
-307 earlier this afternoon.
Please note, for future reference, that if you choose to unilaterally allocate
yourself encoding numbers then your VNC-based software will no longer be
VNC-compatible and your users
On Jan 5, 2008 2:05 PM, Afief Halumi [EMAIL PROTECTED] wrote:
Hello,
I am running the free version of RealVNC for windows and am interested
in being able to run a server that gives the clients control of the
computer or just lets them view the desktop by running different BAT
files.
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.