[comp.windows.x] Help understanding Xt/X interactions....

morreale@bierstadt.scd.ucar.edu (Peter Morreale) (12/11/90)

In my app at some point I create an InputOnly window to cover the
toplevel window.  Prior to mapping the window, I set the backgroundPixmap 
resource of several Xt command widgets to a "gray cross-hatch" (to imply 
that these buttons are unusable).  (which they are since I map the
InputOnly window)  Later, I unmap the window and reset to the default 
background.

This works fine *except* that the label string is covered up by the 
pixmap.  I can live with this (though I'd rather the user still saw the
text in the button...)

Here's the oddity:

I added a pop-up to the app and before I map the pop-up, I execute the
*same* routine which maps the InputOnly window to toplevel, then pop-up
the pop-up (with XtGrabNone). 

In this case, the buttons in toplevel *all* have the text showing along
with the cross-hatch backgroundPixmap.  

The question is, why does the text show in this case, but not when I 
map the InputOnly window in the other case?  

I  would really like the text of the command buttons to show throughout
the entire process 

Any suggestions appreciated,

-PWM



--
------------------------------------------------------------------
Peter W. Morreale                  email:  morreale@ncar.ucar.edu
Nat'l Center for Atmos Research    voice:  (303) 497-1293
Scientific Computing Division