scott@grlab.UUCP (Scott Blachowicz) (03/14/90)
Hi-
I'm running gwm 1.5d on an HP9000/375 with HP-UX 6.5. I'm using HP's
xwcreate program to create a window for use with their Starbase
graphics package(using the "sox11" driver). At any rate, Starbase sets
up a colormap for the X-window that I don't want it to do. After
initialization, I set the window's colormap back to the root-window's
colormap with code that looks like this:
XGetWindowAttributes (display, graph_child_id, &graph_attr);
XGetWindowAttributes (display, root_window, &root_attr);
XSetWindowColormap (display, graph_child_id, root_attr.colormap);
XFreeColormap (display, graph_attr.colormap);
XSync (display, 0);
The colormap gets setup OK...I inquire it later and it is then set to
the root colormap. However, gwm will complain about it with messages
like this:
Gwm X error: X_InstallColormap(0x1495c): no such colormap
It seems gwm isn't recognizing the colormap change. Is there some
magic I need to do to get gwm to recognize a ColormapNotify? or am I
doing things the wrong way?
Thanx,
--
Scott Blachowicz E-mail: scott@grlab.UUCP
USPS: Graphicus ..or.. ...!hpubvwa!grlab!scott
150 Lake Str S, #206 VoicePh: 206/828-4691
Kirkland, WA USA 98033 FAX: 206/828-4236stroyan@hpfcso.HP.COM (Mike Stroyan) (03/16/90)
> I'm running gwm 1.5d on an HP9000/375 with HP-UX 6.5. I'm using HP's >xwcreate program to create a window for use with their Starbase >graphics package (using the "sox11" driver). At any rate, Starbase sets >up a colormap for the X-window that I don't want it to do. The sox11 driver will allocate a new colormap if it needs to, but will use the default colormap if it can. The following actions require a new colormap- gopen with either INIT or RESET_DEVICE shade_mode with INIT define_color_table double_buffer display_enable If you avoid these actions you can sidestep the GWM problem. When you gopen without the INIT flag you will probably want to call clear_view_surface to clear the window, since gopen will not do it. Mike Stroyan, stroyan@hpfcla.hp.com