[Xcb] Working on RandR 1.2 proto

[Barton C Massey]

Talked to Keithp just now, and as I suspected he used event
subcodes because X is getting low on extension event codes;
Xinput is apparently the main culprit here.  I'd say
extending the XSLT to support subcodes would be a fine
approach.

	Bart

In message <D9019EB2-65C9-44D9-8D96-6151691C259A at quirkster.com> you wrote:
> OK, I've hit the first XSLT limitation.
> 
> RandR 1.2 defines one new event ("Notify") which has three subCodes  
> (specified using the CARD8 hole between event type and sequence  
> number). Unfortunately, the remainder of the event structure is  
> completely different between these three subcodes. Currently, our  
> XSLT doesn't allow us to overload event numbers with different event  
> structures like this.
> 
> Is this a useful enough pattern in extensions for us to extend our  
> XML descriptions with an optional subcode?  Like so:
> 
>    <event name="CrtcChangeNotify" number="1" subcode="0">
>      <!-- subcode is specified, so no need to delcare or pad the  
> CARD8 hole -->
>    </event>
> 
>    <event name="OutputChangeNotify" number="1" subcode="1">
>    </event>
> 
>    <event name="OutputPropertyNotify" number="1" subcode="2">
>    </event>
> 
> Or should we ask Keith to use standard event numbering, introducing  
> three new events instead of one event with three subcodes?
> 
> Reference (events are at the bottom):
> http://gitweb.freedesktop.org/?p=xorg/proto/ 
> randrproto.git;a=blob;f=randrproto.h
> 
> Ian
> 
> On Nov 28, 2006, at 11:11 AM, Ian Osgood wrote:
> 
> > So folks know...
> >
> > Ian
> > _______________________________________________
> > Xcb mailing list
> > Xcb at lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/xcb
> >
> 
> _______________________________________________
> Xcb mailing list
> Xcb at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/xcb