diff options
| author | Andrew Gallant (Ocelot) <[email protected]> | 2012-05-12 21:44:53 -0400 |
|---|---|---|
| committer | Andrew Gallant (Ocelot) <[email protected]> | 2012-05-12 21:44:53 -0400 |
| commit | e93d7d109a1eaf93b67636e04d6a795d49b15b37 (patch) | |
| tree | 6ce31a732075bfcb5cabba2001800d4b0a16d366 /xproto/xproto_test.go | |
| parent | 67f391aa9e6095a450ddb08abf0a7a6d29a6737a (diff) | |
added some docs and removed some extraneous code
Diffstat (limited to 'xproto/xproto_test.go')
| -rw-r--r-- | xproto/xproto_test.go | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/xproto/xproto_test.go b/xproto/xproto_test.go index f061198..8d0ca88 100644 --- a/xproto/xproto_test.go +++ b/xproto/xproto_test.go @@ -12,7 +12,11 @@ package xproto There are also a couple of benchmarks that show the difference between correctly issuing lots of requests and gathering replies and incorrectly doing the same. (This particular difference is one of the - claimed advantages of the XCB, and therefore XGB, family. + claimed advantages of the XCB, and therefore XGB, family.) + + In sum, these tests are more focused on testing the core xgb package itself, + rather than whether xproto has properly implemented the core X client + protocol. */ import ( @@ -164,8 +168,6 @@ func TestWindowEvents(t *testing.T) { t.Fatalf("ConfigureWindow: %s", err) } - TestProperty(t) - evOrErr := waitForEvent(t, 5) switch event := evOrErr.ev.(type) { case ConfigureNotifyEvent: |