[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

959.0. "What are these Error MEssages ???" by POOL::KRIEGER () Thu Jun 15 1989 15:52

    
    I can't reach DECW_PROG so I'm entering this here ....
    
    	I am getting the message "not a valid window ID" and 
    
          "BadDrawable - parameter not a Pixmap or Window" ...
    
    WHAT DO THESE MEAN ...
    
    	jim "frustrated in VMS"
    

T.RTitleUserPersonal
Name
DateLines
959.1oops...I dropped my crystal ball17305::WESTI'm just visiting this planet.Thu Jun 15 1989 16:3418
Now for the obvious...

  How about an abstract of what you are intending to do.
  What X/DWT calls generated these errors.
  What version of everything...what hardware...


  What I'm trying to get at is that there are millions...ok thousands...
ok hundreds...well there are quite a few reasons why you got these
errors.

  Is this something that you coded or is a product??

  We will need more info before anyone here can help.

					-=> Jim <=-


959.2PSW::WINALSKICareful with that VAX, EugeneFri Jun 16 1989 21:3330
RE: .0

"not a valid window ID" means that a parameter that you're passing to some Xlib
or Toolkit routine, that is supposed to be a window ID, isn't.

BadDrawable means that a parameter to some Xlib or Toolkit routine that is
supposed to be a drawable, isn't.  A "drawable" is X terminology for something
that you can draw into--either a window or a pixmap.

What you need to do is to look at the routine call that is failing and check
all of the parameters that are supposed to be windows or drawables and make
sure you're passing them correctly.  Here are some common causes I can think
of for these errors:

- passing the address of the parameter instead of its value, or vice versa

- calling the routine before you've initialized the variable that's supposed to
  have the window ID in it

- using XtWindow to get the window ID of a widget before the window is realized
  (the window doesn't exist until you realize the widget--before that, XtWindow
  returns zero, which isn't a valid window ID)

Since Xlib normally does buffering of X calls, it may not be clear exactly
which X call is failing.  You can call XSynchronize() at the front of your
application to cause X to send the calls to the server one at a time, as an
aid to debugging.

--PSW