Peter Kümmel wrote:
Abdelrazak Younes wrote:
Is this your only comment?
Yes. Sorry, don't have the time to do much more. I thought I'd share my
opinion ;-)
Sorry, too - for my harsh reply.
Anyway I don't think there is a simpler solution, at least I will
not look for it, this bug has cost me already too much time.
OK, I've found a better solution ;)
I had to test if it was worth to upgrade to 1GB ram.
I can understand that. I was thinking of collecting the scroll events
and cancelling them if a scroll operation is still on-going but maybe
that's what your patch do. I only briefly looked at it and it _seems_
very complicated.
Yes this is what it does. An it _is_ complicated. ;)
But I've found a more Qt like and elegant solution.
See attached patch, which should be much more readably.
I've introduced two events which are only posted once
to the event queue until the event is not processed.
This also improves(?) the scrolling under Windows,
see the comment in generateLyxScrollEvent.
I checked out todays SVN, applied this patch, and compiled.
Unfortunately, it doesn't help. At least not on linux.
Scrolling a maximized userguide may still overshoot by several pages.
Helge Hafting
