Motif FAQ (Part 6 of 9)

• Introduction
• 158) How can I have a modal dialog which has to be answered before
• 159) TOPIC: MEMORY AND SPEED
• 160) When can I free data structures passed to or retrieved from
• 161) Why does my application grow in size?
• 162) Why does my application take a long time to start up?
• 163) My application is running too slowly. How can I speed it up?
• 164) Why is my application so huge?
• 165) How can I improve performance when creating and deleting
• 166) TOPIC: XMSTRING
• 167) What string functions differ in Motif 1.1 and 1.2? Is
• 168) How can I get the Ascii text out of an XmString?
• 169) When can XmStrings used as resources be freed?
• 170) Why doesn't XmStringGetNextSegment() work properly?
• 171) Why does using XmStringDraw cause a Bad Font error?
• 172) How can I control color of individual strings to show status,
• 173) TOPIC: DIALOGS
• 174) How do I stop my dialog disappearing when I press the help
• 175) How do I make my own dialog? I want a dialog with my own set
• 176) Why do dialog title bars have "_popup" or "<-popup"
• 177) How can I force a dialog window to display?
• 178) How can I control placement of a popup widget? Each time a
• 179) How can I set the dialog's default button?
• 180) How can I create a dialog that behaves like, but looks a little
• 181) TOPIC: LANGUAGE BINDINGS
• 182)* Is there a C++ binding for Motif?
• 183) How can I avoid C++ String class and typedef char *String
• 184) How can I have a C++ member function in a callback?
• 185) Is there a Common Lisp binding for Motif?