>>>>> "Martin" == Martin Vermeer <[EMAIL PROTECTED]> writes:
Martin> QFontEngineMac::doTextTask eating 55% of your CPU? Or spending Martin> 55% of its time there, waiting for drawing to finish? That's weird, especially since none of this time is credited to a lower-level function. Martin> Older LyX also silently drops keystrokes if you type too fast. Martin> Only, it is so much faster that that rarely happens. Perhaps Martin> we should work on 1.4 speed, then. Martin> Or should we switch off processEvents just for the Mac Martin> architecture? What may happen is that the processEvents flag means: "silently eat keystroke events" instead of "leave them in the queue". Actually reading qeventloop_x11.cpp confirms this analysis (it uses XNextEvent, whereas XPeekEvent would be better for what we want to do). So it seems that my brilliant idea was a bit lousy. I do not see what Qt machinery could help us, except perhaps QApplication::postEvent. We could setup an eventFilter for the application that fileters user input events and posts them for later. I am not even sure it would work, but it is similar to the idea of queueing key events for later use. JMarc
