X Protocol: Match Error does not identify what failed.
ralph at inputplus.co.uk
Tue May 28 13:41:44 PDT 2013
Some errors, e.g. Window, contain the bad resource ID but the common
Match error doesn't use any of the many spare bytes it has to give the
caller a clue what was disliked in the specified request. I realise it
would vary per request, but some indication, e.g. the third in a
LISTofVALUE, or a mask, would be helpful.
Is there a historical reason it wasn't done like this?
More information about the xorg-devel