HELP regarding colors

[dls2]

<<Derrick Shearer>>
<James "Wez" Weatherall>
>> I attempted disabling the direct hardware accessability by going to
>> the Display Properties/Settings/Advanced... from which I went to
>> Performance and selected the lowest setting.  Running VNC and
>> Starcraft again, yielded the same results of a rainbow color scheme.
>>
>> Without any direct hardware accessability, I fail to see why DirectX
>> might be bypassing the GDI.  However, my understanding of the MS
>> graphics libraries is only cursory.
>
>I think the setting you're modifying affects how many optimisations are
>used, which is only indirectly how 'direct' access to the display hardware
>is.  The problem arises, I think, because DirectX graphics manipulation
>doesn't get noticed by the standard GDI when in full screen mode, so
>colour-change messages don't occur, for example.  As a result, the colours
>can get confused.
>
>Have you tried running the game, disconnecting and then reconnecting to
>the machine running it?  That will help indicate where the problem is.
<James "Wez" Weatherall>
<<Derrick Shearer>>

I can't do otherwise. :p  Starcraft, like many games, resizes the screen,
and
changes its color depth.  When such happens, existing VNC connections
are killed, and so must be reinitiated.  An extension for quick protocol
renegotiation might be nice.  I don't, however, see a need for adding such
to VNC in any immediate timeframe, unless resolution change induced
disconnects are more common than I believe them to be. (very uncommon)

Your thinking turns out to be right with regard to DirectX and its lack of
reliance upon GDI in full screen mode.  As such, no amount of enabling
or disabling DirectX hardware acceleration has any effect upon VNC's
use of GDI hooks.  I might as well leave DirectX fully accelerated. :p
Ach well, unless VNC expands to include support for sound, then I see
no reason why DirectX support should be addressed, or otherwise
hooked.

VNC would definitely be better with the following:

*Multi-user, multi-sessioning, with consideration given to the distinction
*between shared and independently viewed client/server relationships.
*Furthermore, multiple logon types entailing multiple permission sets.
*
*Effective multi-casting to large audiences.  Repeaters/sub-multi-casters?
*
*"Drag 'n Drop" file transfers with NO command line or menu capability.
*Modular file transfer protocol.
*
*Modular modes for display. (Hextile, CoRRE, RRE, Raw, and others)
*
*Encryption; modularly integrated.
*Compression; modularly integrated.

I realize that these considerations have surfaced before through reading
the VNC-list archives.  I just though that I'd present them all again.

Would VNC be more aptly described as VND (Virtual Network Display),
allowing for VNA (Virtual Network Audio), or VNS (Virtual Network
Sound), with VND and VNA|VNS being components of VNC?

Derrick Shearer
dls2 "at" Lehigh.EDU


---------------------------------------------------------------------
The VNC mailing list     -   see http://www.orl.co.uk/vnc/intouch.html
---------------------------------------------------------------------