Cannot convert string “center “ to type Justify
leerogers@my-deja.com wrote on Mar 23, 2000
Hello. I have installed the X11IRAF 1.1 for IRAF but when launching ximtool, I get the following error: [sco@morpho]# Warning: Cannot convert string "center " to type Justify X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 72 (X_PutImage) Serial number of failed request: 3670 Current serial number in output stream: 3675 Seems to be same error that others here have gotten but depth is set to 8 as I have seen in these other messages and X works fine for other functions. I don't see any other replies in this forum. Any other ideas? Thanks. (2) PII, 128MB, RH6.1 Sent via Deja.com http://www.deja.com/ Before you buy.
Matt Cheselka wrote on Mar 24, 2000
leerogers@my-deja.com wrote:
: Hello.
: I have installed the X11IRAF 1.1 for IRAF but when launching ximtool, I
: get the following error:
: [sco@morpho]# Warning: Cannot convert string "center " to type Justify
This warning has to do with the fact that there is a small bug in the GUI
configuration file for XImtool. This problem is fixed for the next
release. If it gets annoying, let us know and we'll send you instructions
on how to get rid of it.
: X Error of failed request: BadMatch (invalid parameter attributes)
: Major opcode of failed request: 72 (X_PutImage)
: Serial number of failed request: 3670
: Current serial number in output stream: 3675
: Seems to be same error that others here have gotten but depth is set to
: 8 as I have seen in these other messages and X works fine for other
: functions. I don't see any other replies in this forum. Any other
: ideas?
Yes, this is an 8 bpp problem. Try running 'xdpyinfo'. What you'll get is a
long listing of display information for X windows. Look for the entry marked,
"default visual id" and then the number after it. Then match that number to an
entry marked, "visual id". This should be in an entry that provides info like,
"class", "depth", "size of colormap", etc. To properly use Ximtool, this entry
should look something like this:
visual:
visual id: 0x20
class: PseudoColor
depth: 8 planes
size of colormap: 256 entries
red, green, blue masks: 0x0, 0x0, 0x0
significant bits in color specification: 8 bits
If it isn't, you can change the 'default visual id' using Xconfigurator.
The critical pieces here are to make sure you're running 8-bit
pseudocolor.
Let me know if you have problems with any of this stuff.
Matt Cheselka
NOAO/IRAF
leerogers@my-deja.com wrote on Apr 19, 2000
Thanks for the reply Matt. I am still having some troubles and thought
you may be able to point me to the right direction.
I specifically launch X in b bit mode (startx -- -bpp 8) so we can
choose the bpp depending on the application my user wants (AIPS and DS9
are killing me as an administrator :-)
xdpyinfo shows:
number of visuals: 6
default visual id: 0x22
visual:
visual id: 0x22
class: PseudoColor
depth: 8 planes
available colormap entries: 256
red, green, blue masks: 0x0, 0x0, 0x0
significant bits in color specification: 8 bits
...which looks very similar to your example in your last message.
But when launching iraf (cl) and running ximtool from within
(!ximtool&), although ximtool doesn't crash like before, it comes up
with several warnings:
cl> !ximtool&
cl> Warning: Cannot allocate colormap entry for "gray"
Warning: Cannot allocate colormap entry for "#7c8498"
Warning: Cannot allocate colormap entry for "purple"
Warning: Cannot allocate colormap entry for "steelblue"
Warning: Cannot allocate colormap entry for "darkslategray"
Warning: Cannot allocate colormap entry for "SlateGray"
Warning: Cannot allocate colormap entry for "gray63"
Warning: Cannot allocate colormap entry for "royalBlue3"
Warning: Cannot allocate colormap entry for "mediumVioletRed"
Warning: Cannot allocate colormap entry for "grey75"
Warning: Cannot convert string "center " to type Justify
Warning: Cannot allocate colormap entry for "gray65"
Warning: Cannot allocate colormap entry for "SteelBlue"
Warning: Cannot allocate colormap entry for "Gold"
...and the user reports that the tool is useless since he doesn't have
cursor abilities and colors are off.
Any suggestions on what I should do next?
Thanks again for your help.
In article <8bgblp$2c0a$1@noao.edu>,
cheselka@tucana.noao.edu (Matt Cheselka) wrote:
> leerogers@my-deja.com wrote:
> : Hello.
> : I have installed the X11IRAF 1.1 for IRAF but when launching
ximtool, I
> : get the following error:
> : [sco@morpho]# Warning: Cannot convert string "center " to type
Justify
>
> This warning has to do with the fact that there is a small bug in the
GUI
> configuration file for XImtool. This problem is fixed for the next
> release. If it gets annoying, let us know and we'll send you
instructions
> on how to get rid of it.
>
> : X Error of failed request: BadMatch (invalid parameter attributes)
> : Major opcode of failed request: 72 (X_PutImage)
> : Serial number of failed request: 3670
> : Current serial number in output stream: 3675
> : Seems to be same error that others here have gotten but depth is set
to
> : 8 as I have seen in these other messages and X works fine for other
> : functions. I don't see any other replies in this forum. Any other
> : ideas?
>
> Yes, this is an 8 bpp problem. Try running 'xdpyinfo'. What you'll
get is a
> long listing of display information for X windows. Look for the entry
marked,
> "default visual id" and then the number after it. Then match that
number to an
> entry marked, "visual id". This should be in an entry that provides
info like,
> "class", "depth", "size of colormap", etc. To properly use Ximtool,
this entry
> should look something like this:
>
> visual:
> visual id: 0x20
> class: PseudoColor
> depth: 8 planes
> size of colormap: 256 entries
> red, green, blue masks: 0x0, 0x0, 0x0
> significant bits in color specification: 8 bits
>
> If it isn't, you can change the 'default visual id' using
Xconfigurator.
>
> The critical pieces here are to make sure you're running 8-bit
> pseudocolor.
>
> Let me know if you have problems with any of this stuff.
>
> Matt Cheselka
> NOAO/IRAF
>
Sent via Deja.com http://www.deja.com/
Before you buy.
Mike Fitzpatrick wrote on Apr 19, 2000
> But when launching iraf (cl) and running ximtool from within
> (!ximtool&), although ximtool doesn't crash like before, it comes up
> with several warnings:
>
> cl> !ximtool&
> cl> Warning: Cannot allocate colormap entry for "gray"
> Warning: Cannot allocate colormap entry for "#7c8498"
> Warning: Cannot allocate colormap entry for "purple"
> Warning: Cannot allocate colormap entry for "steelblue"
> : :
>
> ..and the user reports that the tool is useless since he doesn't have
> cursor abilities and colors are off.
Since this is a RH6.1 system chances are you're using the default
Enlightenment window manager with Gnome. Enlightenment has a bug which
prevents XImtool from ever gaining the colormap focus which means it
always shows the random colormap and contrast scaling is broken. Unfor-
tunately the only workaround for this is to use a different window manager
(e.g. Gtk or WindowMaker I think will work) under Gnome or switch to the
KDE Desktop as an alternative. The Gnome config panel should allow you to
choose a different manager, but you may have to install other choices if
you didn't install everything by default.
The "cannot allocate colormap" messages can also sometimes be
blamed on the window manager. Both Gnome and KDE are big color hogs with
an 8-bit colormap and if Netscape is running it will grab all available
colors. In general colormap flashing can also be reduced by setting some
ximtool resources, e.g.
XImtool*basePixel: 128
XImtool*maxColors: 100
XImtool*cmapInitialize: True
This will allocate only 100 colors starting at cell 128 and should help
limit the flashing (ximtool defaults to use ~210 colors). If you must run
in 8-bit mode note there is also a "-ncols <N>" flag to Netscape to limit
the colors it uses (otherwise it grabs them all), or just shut it down
when using ximtool.
All the pretty desktop icons come at a price though, if it gets to
be too annoying you can always go back to an "old" window manager such as
FVWM, Motif, etc and solve both problems.
Cheers,
-Mike
Last post on Apr 19, 2000