We don't have a description of the XTEST extension yet, and we should.
Created attachment 5418 [details]
How's this? What apps already use XTest that we could port?
Created attachment 5419 [details]
Awesome! But I'm not sure it's quite right yet. :-/ (Would you add a URL or
other source for the XTEST protocol documentation to this bug?)
I suspect the type of 'window' should be 'WINDOW' and 'cursor' should be
'CURSOR'. I'm a bit skeptical of the FakeInput request too: perhaps FakeInput
should look more like SendEvent from the core protocol?
I haven't been the expert on describing the X protocol since we switched to XML
though, so I'm adding Josh to the CC list.
Created attachment 5422 [details]
Use XCBWINDOW and XCBCURSOR.
I could not find a protocol reference. The XTest document I found only
described the library. That's why I'm looking for a sample app to port and test
I used http://cvsweb.freedesktop.org/xorg/proto/XExt/xteststr.h?rev=184.108.40.206 and
http://cvsweb.freedesktop.org/xorg/lib/Xtst/src/XTest.c?rev=1.2 as my guide.
Created attachment 5423 [details]
Um, WINDOW and CURSOR.
Created attachment 5425 [details]
Conforming to 2.1 protocol document
OK, I did find a protocol spec for XTest 2.1:
I found and ported a test app (xte), convincing me that this description is workable. The app and
description are committed.
I've committed changes to actually build a libXCBxtest library.
git commit 498bf348b7032e05c4bf625628e8d78dd94de3d2
Oops, I'd already done that. Forgot the -a parameter for git-commit. Pushed.