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...
This commit is contained in:
parent
13eff4bec3
commit
269a7b9cc6
|
@ -41,7 +41,7 @@ const (
|
||||||
// that can be loaded off the wire and not grabbed with WaitForEvent
|
// 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
|
// until reading an event blocks. This value should be big enough to handle
|
||||||
// bursts of events.
|
// bursts of events.
|
||||||
eventBuffer = 500
|
eventBuffer = 5000
|
||||||
)
|
)
|
||||||
|
|
||||||
// A Conn represents a connection to an X server.
|
// A Conn represents a connection to an X server.
|
||||||
|
@ -409,6 +409,7 @@ func (c *Conn) readResponses() {
|
||||||
case c.eventChan <- event:
|
case c.eventChan <- event:
|
||||||
default:
|
default:
|
||||||
go func() {
|
go func() {
|
||||||
|
println("overflowing...")
|
||||||
c.eventChan <- event
|
c.eventChan <- event
|
||||||
}()
|
}()
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue