Parent document is top of "Motif FAQ (Part 6 of 9)"
Previous document is "216) How can I get the Ascii text out of an XmString?"
Next document is "218) Why doesn't XmStringGetNextSegment() work properly?"
217) When can XmStrings used as resources be freed?
Answer: The policy OSF have been trying to enforce is that if you set an
XmString or XmStringTable resource, the application is responsible for freeing
the XmStrings used because the widget makes a copy. If you get an XmString
resource, then the application must free the value gotten. If you get an
XmStringTable, then the application should NOT free the value gotten. If the
application wants to manipulate it, it should make a copy first. This policy
appears to be implemented progressively, so may be less true for Motif 1.0
than 1.1.
Parent document is top of "Motif FAQ (Part 6 of 9)"
Previous document is "216) How can I get the Ascii text out of an XmString?"
Next document is "218) Why doesn't XmStringGetNextSegment() work properly?"