Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   10987 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

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	 applica‐
	    tion'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 message
  is class if it already contains a ".", or otherwise is formed	 by  con‐
  catenating 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	 interna‐
  tionalization	 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() speci‐
  fying 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()

Vote for polarhome