Bug 425492 - Okular introduces an artificial delay when scrolling through a file
Summary: Okular introduces an artificial delay when scrolling through a file
Status: RESOLVED DUPLICATE of bug 422050
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 1.11.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-18 11:04 UTC by John van Spaandonk
Modified: 2020-09-09 17:18 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description John van Spaandonk 2020-08-18 11:04:14 UTC 
SUMMARY
There is an artificial delay in okular that prevents me from quickly paging up/down through a document. This delay should be removed. Perhaps it is related to an attempt to implement an (unnecessary) smooth scroll? 

If so then please remove this unneeded smooth scroll feature, it is in the way of a good user experience.

STEPS TO REPRODUCE
1. start okular
2. load pdf
3. scroll

OBSERVED RESULT


EXPECTED RESULT
I have to wait until the smooth scroll is completed before I can scroll again. 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 John van Spaandonk 2020-08-18 11:07:47 UTC 
I made an error in the bug report, For all clarity:
EXPECTER RESULT: I expect to be able to scroll to the document at the limit of computing power of my computer. No artificial delays.
Comment 2 Gleb Popov 2020-09-04 13:16:06 UTC 
I confirm this and this is indeed a bit irritating.

To make the report more clear - it happens when I scroll using "Page down" or "Space" hotkeys. In previous versions simply holding "Space" allows quickly reaching the end of the document even hundred pages long.
Comment 3 Nate Graham 2020-09-09 17:18:08 UTC 

*** This bug has been marked as a duplicate of bug 422050 ***