ldc@a.gp.cs.cmu.edu (Lonnie Chrisman) (08/12/89)
I have a Dialog Widget up and running, but I cannot seem to get the value of the textual input part. I have tried using XtDialogGetValueString(), but this seems to always return the starting (default) value, not the modified value part. On the screen, the value changes as the user types, but the value returned by XtDialogGetValueString() never changes. Does anyone recognize what is going on here? Lonnie.Chrisman@cs.cmu.edu
kochhar@endor.harvard.edu (Sandeep Kochhar) (08/12/89)
In article <5832@pt.cs.cmu.edu> ldc@a.gp.cs.cmu.edu (Lonnie Chrisman) writes: > >I have a Dialog Widget up and running, but I cannot seem to get the value >of the textual input part. I have tried using XtDialogGetValueString(), >but this seems to always return the starting (default) value, not the >modified value part. On the screen, the value changes as the user types, >but the value returned by XtDialogGetValueString() never changes. > >Does anyone recognize what is going on here? > >Lonnie.Chrisman@cs.cmu.edu A week or so ago, I too had posted the same question. I got some replies, but those didn't solve the problem. After looking a little at the widget code, I believe the problem lies in the fact that the DialogWidget doesn't do anything on a XSetValues call for XtNvalue. I haven't finished looking at the code, so I apologize in advance if what I said is wrong... thx. Sandeep Kochhar (617) 495-9515 mail: kochhar@harvard.harvard.edu Harvard University kochhar@harvard.csnet 33 Oxford st, kochhar@harvard.uucp Cambridge, Ma 02138 kochhar@harvard.bitnet "If you didn't get this message, please let me know."
kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) (08/18/89)
> I believe the problem lies in the fact that the DialogWidget doesn't > do anything on a XSetValues call for XtNvalue. You are absolutely right. This is a bug, and will be fixed in R4. Chris D. Peterson MIT X Consortium Net: kit@expo.lcs.mit.edu Phone: (617) 253 - 9608 Address: MIT - Room NE43-213