Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!think.com!paperboy!penge!dbrooks From: dbrooks@penge.osf.org (David Brooks) Newsgroups: comp.windows.x Subject: Re: XmString Question Message-ID: <16962@paperboy.OSF.ORG> Date: 7 Dec 90 05:26:55 GMT References: <502@zok.UUCP> <917@stewart.UUCP> <1990Dec5.020710.12550@alphalpha.com> Sender: news@OSF.ORG Reply-To: dbrooks@osf.org (David Brooks) Organization: Open Software Foundation Lines: 25 In article <1990Dec5.020710.12550@alphalpha.com> nazgul@alphalpha.com (Kee Hinckley) writes: > >If you do a SetValues you definitely should deallocate the string >afterwards. The GetValues is a little less consistant. The release >notes for 1.1 state that everything is copied except XmNdialogTitle, >XmNdirectory, XmNnoMatchString, XmNlabelString (RowColumn only) and >XmNtitleString (in Scale). Add XmNpattern in XmFileSelectionBox. > Presumbably those will be fixed at some >later date. I believe they will be, in 1.1.1 (as usual, no commitment to content or schedule). > Also in XmList XmNitems and XmNselectedItems, which are >arrays of XmStrings are not copied (and you wouldn't want them to be). Right. -- David Brooks dbrooks@osf.org Systems Engineering, OSF uunet!osf.org!dbrooks "No, I didn't say I wanted a Bud light!!!" -- Oedipus