VNC multihead and size change extension

the list of screens and can simply display the entire framebuffer. -- Pierre OssmanOpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio ABWeb: http://www.cendio.com [demime 1.01d removed an attachment of type application

Re: VNC multihead and size change extension

lost in some revision. How about this replacement text: 0 - The screen layout was changed via non-RFB means on the server. For example the server may have provided means for server-side applications to manipulate the screen layout. This code is also used when the client sends a non-incremental Fra

Re: VNC multihead and size change extension

On Mon, 16 Mar 2009 13:29:38 +0100 Peter Rosin wrote: > Den 2009-03-16 11:45 skrev Pierre Ossman: > > > > That would be very against the RFB mentality, yes. But the wiki entry > > you pointed to suggests that these encodings are just used for > > "offline"

Re: VNC multihead and size change extension

On Mon, 16 Mar 2009 16:54:20 +0100 Peter Rosin wrote: > Den 2009-03-16 15:00 skrev Pierre Ossman: > > > > Annoying. Do they also rely on putting the conversion requirements on > > the client? > > Yes. If a client claims support for WMVi, it has to support all

Re: VNC multihead and size change extension

d to change the screen settings need to deal with this. And it allows us to define new error codes in the future with an arbitrary payload. Rgds -- Pierre OssmanOpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio ABWe

Re: VNC multihead and size change extension

On Tue, 17 Mar 2009 11:30:51 +0100 Pierre Ossman wrote: > > How do local equivalents behave? How does Windows or RandR respond to > an invalid change request? I haven't seen much more than "sod off" in > the way of helpfulness from those systems either. The only additi

VNC multihead and size change extension (v2)

ot understand. Note that a simple client which does not support multi head does not need to parse the list of screens and can simply display the entire framebuffer. -- Pierre OssmanOpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio AB

Annoucement: Community RFB protocol specification

: http://www.mail-archive.com/tigervnc-rfbpr...@lists.sourceforge.net/ Please join and help us fully document the RFB landscape. :) Rgds -- Pierre OssmanOpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio AB

Specification for the X11 VNC extension?

Is there some documentation available for the VNC extension? Looking at the RealVNC vncconfig implementation does not explain everything. E.g. what is the character encoding for parameters? Rgds -- Pierre OssmanOpenSource-based Thin Client Technology System Developer

Re: Specification for the X11 VNC extension?

On Tue, 09 Jun 2009 12:34:51 +0200 Corne Beerse wrote: > Pierre Ossman wrote: > > Is there some documentation available for the VNC extension? Looking at > > the RealVNC vncconfig implementation does not explain everything. E.g. > > what is the character encoding for par

Re: Specification for the X11 VNC extension?

eveloper, need an official specification for in order to guarantee interoperability between VNC implementations. I get the impression that you are not involved in VNC development so I doubt you have the answers I'm looking for. Rgds -- Pierre OssmanOpenSource-based Thin Client T

Re: Specification for the X11 VNC extension?

James, do you guys have some internal docs for when you implemented vncconfig? On Thu, 4 Jun 2009 13:36:08 +0200 Pierre Ossman wrote: > Is there some documentation available for the VNC extension? Looking at > the RealVNC vncconfig implementation does not explain everything. E.g. > wh

Re: Extensions for fine-grained image quality control

Subencodings are not needed for that. In essence Tight layers another encoding system on top of the existing one. (And they're not really fixed either as the JPEG encoding is not used until the server has seen a "Quality" encoding.) Rgds -- Pierre OssmanO

Re: Negotiating server screen size

esktopSize. I don't know what implementations > support that extension though... > TigerVNC 1.0.0 does, but I haven't seen anyone else mentioning it yet. Rgds -- Pierre OssmanOpenSource-based Thin Client Technology System Developer Telephone: +46-13-21 46 00 Cendio

Re: Negotiating server screen size

want on the vncviewer command line. The reason you see a finite set with the xrandr tool is because of the way RandR works. What you see is a default list, but more resolutions can be added. Rgds -- Pierre OssmanOpenSource-based Thin Client Technology System Developer Te

Re: Negotiating server screen size

On Wed, 16 Sep 2009 18:10:23 +0200 Christophe Lohr wrote: > Pierre Ossman a écrit : > > You can select any resolution you want on the vncviewer command line. > > > Yes, one can gives any resolution to the DesktopSize option of the Tiger > vncviewer, however only