[comp.windows.x] Dialog Widget Problems ?

jaz@icd.ab.com (Jack A. Zucker) (08/20/90)

I have a dialog widget where the text field seems to be
random in it's ability to allow me to edit the text. 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 ! 

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


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


Thanks, -jaz

converse@EXPO.LCS.MIT.EDU (08/21/90)

> 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.