Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: X11R4 Dialog Widget Question
Message-ID: <9003011729.AA20736@expo.lcs.mit.edu>
Date: 1 Mar 90 17:29:48 GMT
References: <2474@ektools.UUCP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 40


>       dialog = XtCreateManagedWidget ( "dialog", dialogWidgetClass,
>			root_wid, dialogArgs, XtNumber (dialogArgs) );

> This call (and the setup of dialogArgs) works when the "value" resource
> is set to NULL, but not when I set the resource to allow user input.

Does the example program `examples/Xaw/popup' work for you?  Does it work if
you set the value field (it currently is set to <empty+string>)?

In short I need some example code to track down your problem.

> The X Protocol message:

> X Error of failed request:  BadWindow (invalid Window parameter)
>   Major opcode of failed request:  38 (X_QueryPointer)
>   Minor opcode of failed request:  0
>   Resource id in failed request:  0x0
>   Serial number of failed request:  205
>   Current serial number in output stream:  205

Looks to me like someone is doing a query pointer on an unrealized widget.
The Dialog widget doesn't do any query pointer calls so I don't think it
is the Dialog's fault.

> Can someone tell me what has changed since R3 WRT the Dialog Widget?
> The release notees say that no changes will be necessary for the Dialog
> widget, but perhaps, it ain't necessarily so.

There is a difference between no external changes, and no internal changes.  I
did change some of the internal code of the Dialog, but have never seen the
problem that you are having.


						Chris D. Peterson     
						MIT X Consortium 

Net:	 kit@expo.lcs.mit.edu
Phone:   (617) 253 - 9608	
Address: MIT - Room NE43-213