From 94ba2d1333e1ab229fe08f58b5b963e05a4af083 Mon Sep 17 00:00:00 2001 From: "Andrew Gallant (Ocelot)" Date: Tue, 16 Oct 2012 23:40:59 -0400 Subject: The hack continues. I've increased the event channel buffer. I know I'm goofing here. What I'd personally like to do is just use an "infinite" channel. That is, push the limit of how many events can be processed to the machine and not set an artificial limit in XGB. Some day... --- xgb.go | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'xgb.go') diff --git a/xgb.go b/xgb.go index c62cc85..1c6ef93 100644 --- a/xgb.go +++ b/xgb.go @@ -41,7 +41,7 @@ const ( // that can be loaded off the wire and not grabbed with WaitForEvent // until reading an event blocks. This value should be big enough to handle // bursts of events. - eventBuffer = 500 + eventBuffer = 5000 ) // A Conn represents a connection to an X server. @@ -409,6 +409,7 @@ func (c *Conn) readResponses() { case c.eventChan <- event: default: go func() { + println("overflowing...") c.eventChan <- event }() } -- cgit v1.2.3