Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!mintaka!bloom-beacon!EXPO.LCS.MIT.EDU!converse
From: converse@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: Dialog Widget Problems ?
Message-ID: <9008201935.AA28359@excess.lcs.mit.edu>
Date: 20 Aug 90 19:35:41 GMT
References: <1752@abvax.UUCP>
Sender: daemon@athena.mit.edu (Mr Background)
Organization: X Consortium, MIT Laboratory for Computer Science
Lines: 34


> I have a dialog widget where the text field seems to be
> random in it's ability to allow me to edit the text. 

You don't say what version of X you are running, nor do you name the
supplying vendor, patch level, your window manager, or hardware.
I rarely commit to memory the observable side effects of various kinds
of mistakes.  You've got to supply some more information so that somebody
can make a reasonable guess.

> This usually happens while running under dbx (not xdbx). After
> this occurs, then running while not under dbx causes the
> same problem. If I exit from X and restart X altogether,
> the field is editable again. Or in my application, if I
> click on the [OK] prompt, it brings up another dialog
> widget telling me that I have to enter in a file name,
> and after clicking the [OK] button in that widget, I 
> "XtPopdown()" the second widget, and my original one
> is now editable ! 

Sounds like there is a problem with one part of memory overwriting 
another, or that there is a problem with the keyboard input being
received by the dialog.  

> Has anyone seen this behavior before or is it programmer 
> error ?

I can't duplicate it here.

> I'm using the following resources:
> xtag.openfile.dialog*value:
> xtag.openfile*editType:edit

These look fine.