Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

Motif FAQ (Part 6 of 9)
Section - 215) When can XmStrings used as resources be freed?

( Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Forum ]


Top Document: Motif FAQ (Part 6 of 9)
Previous Document: 214)* How can I get the ASCII text out of an XmString?
Next Document: 216) Why doesn't XmStringGetNextSegment() work properly?
See reader questions & answers on this topic! - Help others by sharing your knowledge

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.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:



Top Document: Motif FAQ (Part 6 of 9)
Previous Document: 214)* How can I get the ASCII text out of an XmString?
Next Document: 216) Why doesn't XmStringGetNextSegment() work properly?

Part1 - Part2 - Part3 - Part4 - Part5 - Part6 - Part7 - Part8 - Part9 - Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
kenton@rahul.net (Ken Lee)




Last Update March 27 2014 @ 02:11 PM