Hello, On Thu, Nov 22, 2001 at 10:19:29PM -0700, Micah Dowty wrote: > Ok, I just got this bug fixed. The event queue in pgserver was not correctly > storing the data associated with some events.
Excellent, thanks! It works perfectly for me. I see that even Thanksgiving won't stop you from fixing bugs. :) > Note, however, that when the client delays before reading an event the event is > stored in pgserver's internal event queue. This queue was designed to mainly > process UI events, so it has some limitations: It is a ring buffer of a fixed > size. If the ring buffer overflows, older events will be overwritten. Currently > the buffer in pgserver is large enough to handle 32 events per client, but this > number may likely change, or be added to the config menu. If the client expects > a large number of events to backlog, it should maintain its own larger queue > rather than relying on pgserver's queue. OK, I'll keep that in mind. > Another note: I'm pretty sure that this event queue code won't leak memory even > in severe cases of queue overflow, but let me know anyway if it detects a memory > leak on exit, or if the memory usage reported by ctrl-alt-m increases for no > apparent reason :) Didn't notice anything so far, but thanks for the warning. :) Regards, -Christian -- Christian Grigis | SMARTDATA SA Software Engineer | PSE-A / EPFL Phone: +41-(21)-693-84-98 | CH - 1015 Lausanne mailto:[EMAIL PROTECTED] | http://www.smartdata.ch _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
