XtErrorMsg(3x) — unbundled ANSI-C

NAME

XtErrorMsg − call the high-level fatal error handler.

Synopsis

void XtErrorMsg(name, type, class, default, params, num_params)

    String name;
    String type;
    String class;
    String default;
    String *params;
    Cardinal *num_params;

Inputs

nameSpecifies the general kind of error.

typeSpecifies the detailed name of the error.

classSpecifies the resource class of the error.

defaultSpecifies the default message to use if no message is found in the database.

paramsSpecifies an array of values to be inserted into the message.

num_params
Specifies the number of elements in params.

Returns

XtErrorMsg() terminates the application and does not return.

Availability

XtErrorMsg() has been superseded by XtAppErrorMsg().

Description

XtErrorMsg() passes all of its arguments to the installed high-level error handler. The default high-level error handler is _XtDefaultErrorMsg(). It calls XtAppGetErrorDatabaseText() to lookup an error message of the specified name, type, and class in the error database. If no such message is found, XtAppGetErrorDatabaseText() returns the specified default message. In either case, _XtDefaultErrorMsg() does a printf-style substitution of params into the message, and passes the resulting text to the low-level error handler by calling XtError().

Usage

XtErrorMsg() has been superseded by XtAppErrorMsg(), which performs the same function on a per-application context basis. XtErrorMsg() now calls XtAppErrorMsg() passing the default application context created by XtInitialize(). Very few programs need multiple application contexts, and you can continue to use XtErrorMsg() if you initialize your application with XtInitialize(). We recommend, however, that you use XtAppInitialize(), XtAppErrorMsg(), and the other XtApp*() application context specific functions. See XtAppErrorMsg() for more information.

Museum

Related Articles