| Re: Unsupported X Windows visual [message #35051 is a reply to message #14303] |
Thu, 08 May 2003 09:32   |
Karl Schultz
Messages: 341
Registered: October 1999
|
Senior Member |
|
|
"Nigel Wade" <nmw@ion.le.ac.uk> wrote in message
news:b9djf6$j1l$1@south.jnrs.ja.net...
> Hannah Chenh wrote:
>
>> "Karl Schultz" <kschultz_no_spam@rsinc.com> wrote in message
>>> The thread suggests that there is a patch available that solves a
problem
>>
>> The specified patch(newer version) for solaris 8 was installed on the
>> blade 100.
>>
>>> is not really listing this visual. Perhaps you can post the output from
>>> xdpyinfo? (This will give me some other clues)
>>
>> Here is the output of xdpyinfo on the blade:
>>
>
> [dpyinfo snipped]
>
> Do you get the same output if you run xdpyinfo on the HP machine?
> You should if X is really talking to the display on the blade.
The top of the xdpyinfo output suggests that the information is indeed from
the Sun server. The location of the client does not (should not) matter as
long as the DISPLAY variable points to the server in question.
> There's something definitely wrong in that the blade says the default
visual
> is 8bit PseudoColor yet IDL is using the default of 24bit TrueColor.
From the IDL help:
How IDL Selects a Visual Class
When opening the display, IDL asks the display for the following visuals, in
order, until a supported visual class is found:
1.. DirectColor, 24-bit
2.. TrueColor, 24-bit
3.. TrueColor, 16-bin (on Linux platforms only)
4.. PseudoColor, 8-bit, then 4-bit
5.. StaticColor, 8-bit, then 4-bit
6.. GrayScale, any depth
7.. StaticGray, any depth
You can override this behavior by using the DEVICE routine to specify the
desired visual class and depth before you create a window. For example, if
you are using a display that supports both the DirectColor, 24-bit-deep
visual, and an 8-bit-deep PseudoColor visual, IDL will select the
24-bit-deep DirectColor visual. To instead use PseudoColor, issue the
following command before creating a window:
DEVICE, PSEUDO_COLOR = 8
The colormap/visual class combination is chosen when IDL first connects with
the X Window server. Note that if you connect with the X server by creating
a window or using the DEVICE keyword to the HELP procedure, the visual class
will be set; it then cannot be changed until IDL is restarted. If you wish
to use a visual class other than the default, be sure to set it with a call
to the DEVICE procedure before creating windows or otherwise connecting with
the X Window server.
----
I'm not sure what's going on. IDL should have chosen the 24-bit DirectColor
visual as its default, yet the error message suggests that it is TrueColor.
Hannah, what DEVICE commands are being issued? (Make sure that you check
startup files, etc)
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
