xtappgeterb(3) [hpux man page]

XtAppGetErrorDatabaseText()											       XtAppGetErrorDatabaseText()

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.

  name	    Specifies the name or general kind of the message.

  type	    Specifies the type or detailed name of the message.

  class     Specifies the resource class of the error message.

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

  nbytes    Specifies the size of buffer_return in bytes.

  database  Specifies 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 XtAppGetError-
  Database() 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 mes-
  sage 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.

See Also
  XtAppGetErrorDatabase(1),
  XtErrorMsgHandler(2).

Xt - Error Handling												       XtAppGetErrorDatabaseText()

XtAppErrorMsg() 														   XtAppErrorMsg()

Name
  XtAppErrorMsg - call the high-level fatal error handler.

Synopsis
  void XtAppErrorMsg(app_context, name, type, class, default,  params, num_params)
	 XtAppContext app_context;
	 String name;
	 String type;
	 String class;
	 String default;
	 String *params;
	 Cardinal *num_params;

Inputs
  app_context
	    Specifies the application context.

  name	    Specifies the general kind of error.

  type	    Specifies the detailed name of the error.

  class     Specifies the resource class of the error.

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

  params    Specifies an array of values to be inserted into the message.

  num_params
	    Specifies the number of elements in params.

Returns
  XtAppErrorMsg() terminates the application and does not return.

Description
  XtAppErrorMsg()  passes  all	of  its arguments except app_context 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 han-
  dler by calling XtError().

  See XtAppGetErrorDatabaseText() for details on how messages are looked up in the error database.

Usage
  To  report  non-fatal  error	messages  or  warnings	without  exiting, use XtAppWarningMsg().  To change the high-level error handler, use
  XtAppSetErrorMsgHandler().

  Note that the num_params argument to this function is a Cardinal *, not a Cardinal.

  Although the Intrinsics interface allows separate error and warning handlers for each application context, most implementations  will  sup-
  port only a single set of handlers.  When a new handler is installed, it will be used in all application contexts.

Example
  The following code is from the Intrinsics internal function _XtCreateWidget():

     String params[2];
     Cardinal num_params = 2;

     params[0] = name;
     params[1] = XtName(parent);
     XtAppErrorMsg(XtWidgetToApplicationContext(parent),
	 "nonWidget", XtNxtCreateWidget, XtCXtToolkitError,
	 "attempt to add non-widget child to parent which supports only widgets",
	 params, &num_params);

See Also
  XtAppError(1), XtAppSetErrorHandler(1), XtAppSetErrorMsgHandler(1), XtAppSetWarningHandler(1), XtAppSetWarningMsgHandler(1), XtAppWarn-
  ing(1), XtAppWarningMsg(1),
  XtErrorMsgHandler(2).

Xt - Error Handling														   XtAppErrorMsg()