XtAppGetErB(3x) — HPUX 9.05

NAME

XtAppGetErrorDatabaseText − get the text of a named message from the error database.

Synopsis

void XtAppGetErrorDatabaseText(app_context, name, type, class, default, buffer_return, nbytes, database)

    XtAppContext app_context;
    String name, type, class;
    String default;
    String buffer_return;
    int nbytes;
    XrmDatabase database;

Inputs

app_context
Specifies the application context.

nameSpecifies the name or general kind of the message.

typeSpecifies the type or detailed name of the message.

classSpecifies the resource class of the error message.

defaultSpecifies the default message to use if an error database entry is not found.

nbytesSpecifies the size of buffer_return in bytes.

databaseSpecifies the database to be used, or NULL if the application’s database is to be used.

Outputs

buffer_return
Specifies the buffer into which the error message is to be returned.

Description

XtAppGetErrorDatabaseText() looks up the message named by name, type, and class in database or in the database returned by XtAppGetErrorDatabase() for app_context if database is NULL. If such a message is found, it is stored into buffer_return, otherwise the message in default is stored into buffer_return. The resource name of the message is formed by concatenating name and type with a single "." between them. The resource class of the message is class if it already contains a ".", or otherwise is formed by concatenating class with itself with a single "." between the strings.

Usage

You should not need to call XtAppGetErrorDatabaseText() unless you are writing a customized high-level error or warning handler. Because the Intrinsics do not support the customization and internationalization of error messages very well, some applications may want to read a customized error database (found with XtResolvePathname() or named by an application resource, for example) and provide customized error and warning handlers that call XtAppGetErrorDatabaseText() specifying this custom database explicitly. While the X Toolkit specification permits individual error databases for each application context, most implementations will only support a single database. In the MIT implementation, the error database file is /usr/lib/X11/XtErrorDB.

Museum