Path: utzoo!censor!geac!jtsv16!uunet!tut.cis.ohio-state.edu!bloom-beacon!EXPO.LCS.MIT.EDU!kit
From: kit@EXPO.LCS.MIT.EDU (Chris D. Peterson)
Newsgroups: comp.windows.x
Subject: Re: Dialog Widget Value String
Message-ID: <8908041516.AA12935@expo.lcs.mit.edu>
Date: 4 Aug 89 15:16:46 GMT
References: <2363@husc6.harvard.edu>
Organization: The Internet
Lines: 23


> According to the Xaw manual, 
> 	"if a string was specified in the XtNvalue resource, Dialog
> 	will store the input directly into the string" (p. 39).

The documentation is wrong (sigh).  The Dialog actually makes a local copy
of the string for you.  Since changing the behavior to match the docs
may break some applications, I am planning on updating the docs for R4, and
leaving the implementation the way it currently behaves.

> However, I find that the string I pass is not changed even though
> the value string was changed by the user; however, XtDialogGetValueString()
> returns the correct (new) string.

Yep, to retreive the string you will need to use XtDialogGetValueString(), or
make a GetValues() call.  

						Chris D. Peterson     
						MIT X Consortium 

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