No worry. anyway, the current design is broken because.
1) Filter X event like that is a broken approach, for example, it
would break the meaning of zig-zag movement. The filtering strategy
should rely on distance and time one a _fixed size buffer_ (As any
display server does to prevent frozen
On Fri, Jan 28, 2011 at 5:39 PM, Banlu Kemiyatorn obj...@gmail.com wrote:
(My NSApp has this implementation, allowing it to store parameters
instead of real event on a fixed size loop queue which can migrate old
event out of the fast loop queue and collect leak events and
auto-scale the fast
On 28 Jan 2011, at 14:53, Banlu Kemiyatorn wrote:
On Fri, Jan 28, 2011 at 5:39 PM, Banlu Kemiyatorn obj...@gmail.com wrote:
(My NSApp has this implementation, allowing it to store parameters
instead of real event on a fixed size loop queue which can migrate old
event out of the fast loop
On Fri, Jan 28, 2011 at 10:33 PM, Richard Frith-Macdonald
rich...@tiptree.demon.co.uk wrote:
On 28 Jan 2011, at 14:53, Banlu Kemiyatorn wrote:
Just try benching with preallocated pool to make use of deallocated
object w/o reallocation, it's ~160% faster than traditional +alloc. So
my event
