Volume 6A: Motif Programming Manual

you cannot unmanage automatically−created children directly in UIL, which means that the program must handle this

step.

The program also updates the XmNmessageString of the ErrorDialog each time it is used to display an error

message. The error strings are hard−coded into this application. You can make your programs more open to

internationalization if you place the strings in a UIL module. Then you can easily set string resources by replacing

calls to XtVaSetValues() with calls to MrmFetchSetValues().

26.3 Summary

Creating an application that uses UIL and Mrm is very similar to creating an application that just uses Motif. The main

difference is that the user interface of the application is defined in one or more UIL modules, instead of being created

in application code by Motif and Xt creation procedures. Using UIL tends to simplify the application code by

separating the interface from the code itself. In some situations, provisions must be made to pass widget IDs from a

UIL module to the application, so that the application can modify a widget dynamically while it is running. While

using UIL certainly affects the creation of a user interface, application callbacks and other internal operations remain

much the same.

26 Building an Application With UIL 26.3 Summary

716