comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Another VM conundrum
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Another VM conundrum [message #37298] Thu, 11 December 2003 10:22
JD Smith is currently offline  JD Smith
Messages: 850
Registered: December 1999
Senior Member
Having fixed my main-level XManager issues (thankfully fairly
trivial), I now find myself with another problem. Typically, I
recommend setting something like:

device,DECOMPOSED=0,TRUE=16,RETAIN=2

in your IDL startup file, where RETAIN=2 is good for most Linux
machines (whose window managers don't provide decent backing store),
DECOMPOSED=0 is immortalized on David's site, and TRUE=16 is just for
good measure, for those X servers which *claim* to offer DirectColor
but don't really (sadly, not few in the Linux world). However, I
leave it up to the end user to find some combination of device
incantations which work for them.

That's fine for interactive usage, but with a runtime/VM application,
the startup file is never consulted, so you need to perform these
device incantations yourself in the code. Has anyone solved this
problem in a platform-independent way? Would something like:

device,DECOMPOSED=0,RETAIN=2

always be safe, even for older 8-bit PSEUDOCOLOR machines? Or is
there some method of interrogating DEVICE for info before making a
final decision on RETAIN and color-model settings? What guidance from
the IDL color gurus?

Thanks,

JD
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Mesh decimate for DXF data formats
Next Topic: Virtual machine errors: badmatch, badwindow, object graphics

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Oct 11 15:57:26 PDT 2025

Total time taken to generate the page: 1.12196 seconds