Dov Feldstern wrote:
Peter Kümmel wrote:
I'm running out of ideas...
Is this patch better (the flush call is new)?
Or with processEvents instead of flush?
event_2.patch works for me --- but then again event_1 did, too. Again,
this is on linux. Scrolling appears to be fine (both with arrow keys
and page-up and page-down, and with the scrollbars). I don't see any
overshoot, either -- scrolling stops as soon as I stop pressing (or
within a split-second).
Can you try this with the machine being really busy? For example,
test scrollbar scrolling with a maximized window, while the machine
is busy compiling LyX? Or make it busy by running a simple
script to make it waste time:
File loadscript:
./loadscript
This script will call itself in an endless loop, break it with ctrl+c when
you are done testing. You can bring the load further up by running several
of these, each in an xterm of its own.
Or try delaying the display hardware by running some heavy
animation/movie/3D-test on half the screen and do a lyx scrolltest
on the other half.
It is no surprise if a loaded test makes LyX _slow_, it still shouldn't
overshoot though.
Helge Hafting
