Path: utzoo!attcan!uunet!cs.utexas.edu!usc!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Extension errors
Message-ID: <8909111909.AA08406@expire.lcs.mit.edu>
Date: 11 Sep 89 19:09:54 GMT
References: <8909111846.AA02614@amd-16.hac.com>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 14


    In adding extensions, I wanted to make use of the standard X error
    handling (and reporting) and only provide extension error text by
    providing a routine which is defined by XESetErrorString.

The following change to XGetErrorDatabaseText (on page 273 in the DP book)
will happen in R4:

XRequest  /+ For a core protocol request, +/ the major request protocol
	  number is used for the message argument.  /+ For an extension
	  request, the extension name (as given to XInitExtension) appended
	  with a period and the minor request protocol number is used for
	  the message argument. +/  If no string is found in the error
	  database, the default_string is returned to the buffer argument.