People-friendly opcodes

[Soeren Sandmann]

Julien Cristau <jcristau at debian.org> writes:

> On Fri, Mar 19, 2010 at 11:24:25 -0700, Jeremy Huddleston wrote:
> 
> > How does one ensure that X Errors report human readable text versions of major / minor opcodes?
> > 
> > ie, how do I make sure that something like this is reported:
> > 
> > Major opcode of failed request:  145 (MY-EXTENSION)
> > Minor opcode of failed request:  8 (MyExtDoSomething           )
> > 
> > rather than:
> > 
> > Major opcode of failed request:  145
> > Minor opcode of failed request:  8
> > 
> AFAIK Xlib's default error handler looks these up in
> $(datadir)/X11/XErrorDB.  Others might replace that with less useful
> ones, though (hi, gtk).

We really should have an error extension that can provide detailed
error messages through the protocol. Often it's far from clear what
triggered a particular BadMatch.

It might be a good GSoC project.


Soren