Grant McDorman wrote:
>
> > I am using TightVNC connect from sunbox to
> > sunbox. The remote VNC server is 24-bit
> > true color, while the local machine's
> > display has 6 visuals, one of which is
> > 24-bit true color. When I try to start
> > the vncviewer with -truecolor, it always
> > says that it is using 8-bit pseudocolor.
> > I confirm this on the VNC server side by
> > viewing the log. Why does the viewer
> > ignore the option for true color? The
> > reaons why I know that the 24-bit true
> > color is valid is by xdpyinfo.
>
> vncviewer -owncmap -truecolour
>
> If you don't use -owncmap, the viewer uses the
> default colour map (which makes - -depth and
> -truecolour useless). IMHO, vncviewer should either
> automatically use a private colourmap when one of
> those options are used, or print a warning message.
> - --
> Grant McDorman <[EMAIL PROTECTED]>, Sr.
> Software Design Consultant
> Cedara Software Corp. <URL:http://www.cedara.com>
> (formerly I.S.G. Technologies Inc.)
> Mississauga, Ontario, Canada
Hi, Grant,
Actually, your comment sent me off on some more
sleuthing. The problems seems to be that -owncmap
is being specified (I forgot that I had vncviewer
aliased to always specify -owncmap). If I specify
-truecolor without -owncmap, the viewer uses a true
color visual of depth 8. Funny, but I still get
flashing colors when moving the mouse pointer in
and out of the viewer.
The illuminating thing is that if I specify -truecolor
and '-depth 24', the viewer complains that it can't
find a matching visual. It uses "default colormap" and
translates from BGR233. There is no flashing! (Yay!).
But of course; it's not using its own colormap. The
only mystery is why there *is* flashing when both
server and viewer are true color, as above. At least
with the default colormap, I don't get messed up colors
when I put the viewer in fullscreen (it seems that the
fullscreen uses the nonprivate color map when the
viewer is started with -owncmap!).
The reason for not finding a true color visual of
depth 24 is obvious when I reexamine the xdpyinfo:
visual id: 0x26
class: TrueColor
depth: 8 planes
available colormap entries: 8 per subfield
red, green, blue masks: 0x7, 0x38, 0xc0
significant bits in color specification: 8 bits
Before, I mistook the 8bit/subfield as meaning 8-bit
per color plane, thus yielding 24-bits. I ignored the
depth of 8 planes because I wasn't sure if that a
"planeL was a "bit"; one would assume so, but it
contradicted my mistaken impression of 24-bits. Now,
it seems pretty certain that "subfield" means "pixel",
so there are *not* 24 bits.
Anyway, the outstanding "mystery" seems to be that
I get pseudocolor symptoms when the viewer and the
serverlog claims that the client is 8-bit true color.
That means flashing when crossing the viewer boundary,
and messed up colors in fullscreen. (The VNC server is
true color, depth 24).
I think I've beaten this one to death. Thanks if
anyone still has any answers.
Fred
--
Fred Ma, [EMAIL PROTECTED]
Carleton University, Dept. of Electronics
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list
