diff options
author | Andrew Gallant (Ocelot) <Andrew.Gallant@tufts.edu> | 2012-10-16 23:40:59 -0400 |
---|---|---|
committer | Přemysl Janouch <p@janouch.name> | 2018-09-08 16:49:15 +0200 |
commit | 269a7b9cc68b16d3618c1302f829048ee501dfab (patch) | |
tree | 5e0af366d0554ca7decc2f1a3794d2c4b48cdc02 /nexgb | |
parent | 13eff4bec3ce71d26f6cc423a43cb158b60842a4 (diff) | |
download | haven-269a7b9cc68b16d3618c1302f829048ee501dfab.tar.gz haven-269a7b9cc68b16d3618c1302f829048ee501dfab.tar.xz haven-269a7b9cc68b16d3618c1302f829048ee501dfab.zip |
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...
Diffstat (limited to 'nexgb')
-rw-r--r-- | nexgb/xgb.go | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/nexgb/xgb.go b/nexgb/xgb.go index c62cc85..1c6ef93 100644 --- a/nexgb/xgb.go +++ b/nexgb/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 }() } |