Bug 167438 - Browse Tool scrolling jumps at border of the screen
Summary: Browse Tool scrolling jumps at border of the screen
Status: RESOLVED FIXED
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-25 18:27 UTC by Stephan Burkhardt
Modified: 2009-05-04 16:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Burkhardt 2008-07-25 18:27:53 UTC
Version:           0.7.80 (using 4.1.60 (KDE 4.1.60 (KDE 4.2 >= 20080709)), Kubuntu packages)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.24-20-generic

When using Okulars browse tool for mouse scrolling there is a great feature that allows you to scroll over the edge of the screen by placing the mouse cursor on the bottom of the screen when it would leave the top of the screen and vice versa. I don't know if there is a name for it (something like borderless mouse scrolling maybe).
This is great and is actually one of the reasons I really like Okular.

But sadly about one in three times (I can't predict when) it doesn't work the way it is supposed to be but instead scrolls one screen down or up when I cross the screen-border. It is important to note, that it does scroll into the right direction, but instead of scrolling smoothly it jumps one screen-height too far.

Reproduce: 
-open a pdf in okular (dvi works too, backend shouldn't matter)
-scroll somewhere to the middle of the document
-use the browse tool and move the mouse back and forth over the edge of the screen several times
You should see the mentioned behavior after some tries.

 Stephan

     P.S: why does this borderless mouse scrolling only work in the vertical, not the horizontal direction?
Comment 1 Stephan Burkhardt 2008-08-13 20:33:14 UTC
I cannot reproduce this bug in the Windows build I installed today. Everything works fine there.
Comment 2 Ramón Zarazúa 2009-01-26 07:51:13 UTC
I have that bug too, I am trying to fix it, but with api.kde.org down it's really hard to make progress.
Comment 3 Ramón Zarazúa 2009-02-18 22:28:09 UTC
From what I've seen, this happens with 64-bit versions of QT, both my 64-bit installations share the same bug (QMouseEvent is called twice for the same event), however my 32-bit installation works perfectly, I'm not sure if I should submit this bug to QT, or let an official KDE developer submit it (since you guys may have higher priority than some random user.)

Let me know if there is anything else I can do.
Comment 4 Stephan Burkhardt 2009-05-04 16:42:00 UTC
In Kubuntu Jaunty this seems to be fixed. Might be due to Qt4.5.
Thanks to Ramón for digging into this even though this seems to have fixed on its own. I will change this to RESOLVED if this is okay.