ranslation routines in the operating system.
Regards,
Wez @ RealVNC Ltd.
> -Original Message-
> From: Sood, Sanjeev [mailto:[EMAIL PROTECTED]
> Sent: 21 September 2005 19:49
> To: James Weatherall; vnc-list@realvnc.com
> Subject: RE: RFB Protocol related question
>
>
EMAIL PROTECTED]
Sent: Wednesday, September 21, 2005 10:38 AM
To: Sood, Sanjeev; vnc-list@realvnc.com
Subject: RE: RFB Protocol related question
Sanjeev,
As I stated in my previous mail, no, your assumption is incorrect.
Viewers
can request any format they wish, and some do take advantage of
.
> -Original Message-
> From: Sood, Sanjeev [mailto:[EMAIL PROTECTED]
> Sent: 21 September 2005 17:55
> To: James Weatherall; vnc-list@realvnc.com
> Subject: RE: RFB Protocol related question
>
> Hello James,
>
> Thanks for your response. So what you are saying is that
Weatherall [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 21, 2005 2:28 AM
To: Sood, Sanjeev; vnc-list@realvnc.com
Subject: RE: RFB Protocol related question
Sanjeev,
Yes, viewers can request pixel formats that are "larger" than the
server's
pixel format. i.e. a viewer on a 32
Sanjeev,
Yes, viewers can request pixel formats that are "larger" than the server's
pixel format. i.e. a viewer on a 32bpp desktop can request 32bpp even
though the server is only doing 16bpp.
Regards,
Wez @ RealVNC Ltd.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAI
Matthias,
The desktop resize encoding is described in the RFB 3.7 protocol document.
RFB 3.7 is only supported by VNC Server/Viewer 4.0 and above.
I think you are confusing what the desktop resize encoding is for. It's
sent by the server when the desktop size changes, to the viewer. Not the
oth
> A silly example I sometimes use here is the next software requirements:
> If the input 2 is given, then the result must be 4. If the input 4 is
given,
> then the result must be 16.
> General solution, just writing the requirements:
> if input == 2
> then result = 4
> else if input == 4
> th
sing proper the application.
When you need to reboot your unix box, you also make a proper shutdown. Why not just
pulling the plug ???
Greetings
Rudi
-Original Message-
From: "Beerse, Corni" [mailto:[EMAIL PROTECTED]]
Sent: vrijdag 14 juni 2002 10:36
To: '[EMAIL P
>M> Are there any plans to update the RFB protocol support things like
>M> resoloution and colour depth switching? And other limitiations of
>M> the current system?
>
>M> It's quite annoying when a app changes the desktop resolution, and
>M> VNC dumps out.
>
>TightVNC will support variable screen
tware requirements:
If the input 2 is given, then the result must be 4. If the input 4 is given,
then the result must be 16.
General solution, just writing the requirements:
if input == 2
then result = 4
else if input == 4
then result = 16
else ERROR
A solution with a little more thinkin
Hello,
> "M" == MGillespie <[EMAIL PROTECTED]> writes:
M> Are there any plans to update the RFB protocol support things like
M> resoloution and colour depth switching? And other limitiations of
M> the current system?
M> It's quite annoying when a app changes the desktop resolution, and
M>
need to be changed and an rfbprotocol need to
tell the server that the client support the resizing.
Perhaps it is already include in RFB 4.0.
Need to check it!
<<mailto:[EMAIL PROTECTED]]
Sent: donderdag 13 juni 2002 15:28
To: '[EMAIL PROTECTED]'
Subject: RE: RFB protocol
&g
-Original Message-
From: "Beerse, Corni" [mailto:[EMAIL PROTECTED]]
Sent: donderdag 13 juni 2002 15:28
To: '[EMAIL PROTECTED]'
Subject: RE: RFB protocol
> -Original Message-
> From: Rudi De Vos [mailto:[EMAIL PROTECTED]]
> The problem is not implemen
TED]] On
Behalf Of Rudi De Vos
Sent: Thursday, 13 June 2002 9:21 PM
To: [EMAIL PROTECTED]
Subject: RE: RFB protocol
The problem is not implementing the option.
Just a few changes on server and client site.
But changing the client, is loosing compatibility...
Rewriting the client for all plat
> -Original Message-
> From: Rudi De Vos [mailto:[EMAIL PROTECTED]]
> The problem is not implementing the option.
> Just a few changes on server and client site.
> But changing the client, is loosing compatibility...
> Rewriting the client for all platforms.
>
> The resizing stuff was imp
The problem is not implementing the option.
Just a few changes on server and client site.
But changing the client, is loosing compatibility...
Rewriting the client for all platforms.
The resizing stuff was implemented in the old Single shared application
code. Resizing the application sends an r
16 matches
Mail list logo
