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 - 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 | Cities ]


Top Document: Motif FAQ (Part 6 of 9)
Previous Document: 215) When can XmStrings used as resources be freed?
Next Document: 217) Why does using XmStringDraw cause a BadFont error?
See reader questions & answers on this topic! - Help others by sharing your knowledge

Answer: The documentation in Motif 1.0 is in error. Instead of

XmStringGetnextSegment(context, ...)
XmStringContext * context;

it should be

XmStringGetnextSegment(context, ...)
XmStringContext context;

i.e. with no indirection.

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: 215) When can XmStrings used as resources be freed?
Next Document: 217) Why does using XmStringDraw cause a BadFont error?

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