Martin Vermeer wrote:
On Fri, May 18, 2007 at 08:55:15AM +0200, Peter Kümmel wrote:
Martin Vermeer wrote:
On Thu, May 17, 2007 at 10:41:56PM +0200, Andre Poenitz wrote:
On Thu, May 17, 2007 at 12:57:29PM +0200, Peter Kümmel wrote:
I would feel more comfortable is this were restricted to scrolling,
but I take it you extensively tested it with 'usual typing'
Currently all generated events are dropped which couldn't become
visible immediately. But could you image a scenario where this is
a problem?
People might type very quickly. Typing 200 characters/minutes without
mistake is not unheard of (even if it's surely not my league...), I
guess they would be annoyed if a keystroke get eaten because they typed
'too fast'.
Another scenario: I am typing on my Nokia 770 Internet tablet over a
vnc connection. It does 'word completion', which is like very fast typing...
and indeed, in LyX 1.4 characters get lost :-(
Fine, this is a case I haven't realized.
Here it depends on the value isAutoRepeat() returns.
When it is true it is possible that the keys are lost,
but I assume that for lyx/Qt the word completion looks
like a user input, then it should work.
Eh, what I meant was that _even without your patch_ LyX is
dropping characters on the floor. Not good.
Maybe this tablet uses Input Methods? In which case, 1.5 will be better
here. Try it.
Abdel.
