Martin Vermeer <[EMAIL PROTECTED]> writes:
| On Fri, May 13, 2005 at 05:37:18PM +0200, Lars Gullik Bjønnes wrote:
>
| ...
|
>> Note that we now send keyevents to the core every 25ms (+ the time it
>> takes to handle them) 25ms should not be noticable when typing unless
>> (as the case is on your box) the time to handle the event is really
>> long...
>> (I bet that even if you reduce it to 10ms you will have slugish
>> result...)
>>
>> Note that the actuall handling of the keyevents have not changed, so
>> that is just as fast/slow as it has been before (with a 12.5ms delay
>> added on average...)
>
| Yet I have a dark fear that somewhere in that 25 ms a
| processEvents-handled keystroke may slip in, and land on the wrong
| place. Having this happen only very rarely (but sometimes) is in a way
| even worse, more treacherous than having it all the time up-front.
???
Those events received while the timer goes (tick) is put on the queue.
--
Lgb
