Changing pixelformat on the fly
Christopher Mc Carthy
christopher.mccarthy "at" gltrade.com
Mon Jan 3 16:55:01 2005
Bit of feedback on one small issue of this discussion - I agree strongly
with James on this point, that it is far better to assume low bandwidth
at the beginning and then only change if this is not the case.
Using a modem (or other slow connection) connection for VNC (as I have
done only on a few occasions) can be pretty painful already, please
don't make it any harder ;)
As always thanks for the hard work that's going into this. 'Bonne
annee' and all that from France.
(infrequent Real- and Tight- VNC user).
From: "James Weatherall" <jnw "at" realvnc.com>
To: "=?iso-8859-1?Q?'Peter_=C5strand'?=" <astrand "at" cendio.se>,
<vnc-list "at" realvnc.com>, <vnc-tight-list "at" lists.sourceforge.net>
Subject: RE: Changing pixelformat on the fly
Date: Mon, 27 Dec 2004 20:30:01 -0000
Organization: RealVNC Ltd.
> >If users of faster connections object to the initial low-colour
> >display then they can explicitly force full colour mode=20
> while leaving
> > AutoSelect set.
> It's all about selecting good defaults. I think full color is=20 a
>better=20 default than low color.
As I've said previously, it's clearly not. It results in a =
significantly longer startup time for users with slow connections (56K
modem, for example), while providing no real benefit to users of fast
networks, who = can either let AutoSelect choose Full Colour for them or
set it explicitly themselves.