[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Bennett Helm <[EMAIL PROTECTED]> writes:
>
| | On May 12, 2005, at 8:07 PM, Lars Gullik Bjønnes wrote:
>>
>>> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>>>
>>> | | this is kindo a proof-of-concept.
>>>>
>>> | This is a revised version of the patch. This time is also prunes key
>>> | events that is caused by auto-repeat. (Gives imho very nice
>>> behavior.)
>>>
>>> And I cleaned it up a bit.
>>>
>>> If people feels that this make behaviour better I think we should
>>> commit this for 1.4.
>>>
>>> | Comments bitte please por favor.
>>>
>>> ditto again.
>>
| | With this new version of the patch, I cannot duplicate either the
| | re-ordering problem or the problem of dropping characters. However,
| | typing feels a bit slower than before, with characters appearing on
| | the screen at a fixed speed as if from a slow teletype.
>
| 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...)
On my box 10ms feels a bit bettern when doing insert with auto-repeat.
But 100 keyevents per second should be enought for most.
(even a barcode reader that use some funky way of inserting characters
into lyx.)
--
Lgb
