Bennett Helm <[EMAIL PROTECTED]> writes:
| On May 12, 2005, at 12:56 PM, Lars Gullik Bjønnes wrote:
>
>> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>>
>> | Would be nice if people could try this a bit and see if the problems
>> | seen earlier can be reproduced with this patch applied.
>>>
>> | - most likely a check for update in progress is needed in the
>> | keyeventTimeout
>> | - event coalescing would be nice... (may be 1.5 stuff if we go
>> this route)
>>
>> Without this patch I saw the "occasional drop of chars" when typing
>> really fast. With this patch I cannot see that anymore.
>
| With this patch, I see an occasional re-ordering (rather than
| dropping) of characters. So typing "The last time I tested lyx"
| produces "The last tim I tested ly.xe". That's an improvement.
Interesting... and bad... we are back to the original problem. But
perhaps reordering is better than dropping in any case.
Is the reordering problem seen on any other platform? Or is it just
Qt/Mac?
| Moreover, with this patch I no longer see the problem with the mouse
| automatically selecting text as it's moved, without any button clicks.
I have no idea how you could see that from the beginning... could be
that some user-mouse-event got thrown away... and that event was
really needed...
| However, even with this patch -- and this was the original problem I
| reported for Mac OS X -- I can still type much faster than lyx is able
| to display (when working on long-ish documents).
If event coalescing was added I think this would be a lot better.
| lyx-140 is (still)
| too slow for me to be able to use it on a relatively recent and
| powerful machine, let alone my aging laptop. I'm not sure whether this
| patch improves matters there over the state of lyx-140 early this week.
Seem that something else than LyX really have a problem on your box.
If your trace that showed some font handling to use up to 50% of the
time is correct there isn't a lot we can do...
(except perhaps use a cache to avoid the lenghty operation)
--
Lgb
