home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!jvnc.net!princeton!rutgers!news.cs.indiana.edu!tjones@moose.cs.indiana.edu
- From: tjones@moose.cs.indiana.edu (terry jones)
- Newsgroups: comp.windows.x
- Subject: Problem with dialog widget values in Xaw & Xaw3d.
- Message-ID: <1992Aug30.210619.10865@news.cs.indiana.edu>
- Date: 31 Aug 92 02:06:11 GMT
- Organization: Indiana University, Bloomington
- Lines: 61
-
- [SPARCstation IPX, X11R5, /bin/cc compiled.]
-
-
- I am having some odd behavior when trying to set values in Xaw
- dialog widgets. I am doing this with
-
- static void
- set_dialog_value(w, value)
- Widget w;
- String value;
- {
- Arg arg;
-
- XtSetArg(arg, "value", value);
- XtSetValues(w, arg, 1);
-
- return;
- }
-
-
- which works fine.
-
- With 9 dialog boxes (each with a label, a value (assigned with the above),
- and no buttons), things are fine.
-
- When I add a 10th dialog widget and give it a label, it too displays
- fine.
-
- When I add a value to this widget (even ""), the values in most of the
- rest of the dialog widgets are suddenly empty (at least they are
- displayed that way). This happens with Xaw3d too, though the set of
- disrupted values is different.
-
- Worse is to come... I have checked all the values I am passing around
- and they all seem fine. I don't *think* I have any memory problems. The
- problem I just described is not specific to the particular 10th dialog
- widget. I can pick some set of 9, which will work, but then turning on the
- 10th one's (whichever this happens to be) value reproduces the problem.
-
- If I add
- printf("dialog widget has value '%s'\n", XawDialogGetValueString(w));
- to the above function after the XtSetValues() call, the correct strings
- are printed for all ten widgets.
-
- In case it matters, the dialog boxes live (with two command widgets) in
- a form widget in a popup topLevelShell in the shell returned by
- XtAppInitialize.
-
-
- I am a complete X novice, so I suspect the problem is mine, but of
- course wonder if this is not some sort of memory problem on the other
- side of the fence.
-
- I'll try to make a small file that reproduces the problem.
-
- In the meantime, any suggestions would be appreciated.
- Terry Jones.
-
-
- P.S. Thanks to those who helped with the resources problem I posted
- the other day. Things now seem to work as advertised.
-