After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 341566 - Mark the position when scrolling
Mark the position when scrolling
Status: RESOLVED DUPLICATE of bug 170871
Product: evince
Classification: Core
Component: general
0.5.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-05-12 17:37 UTC by Hubert Figuiere (:hub)
Modified: 2006-11-04 21:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Hubert Figuiere (:hub) 2006-05-12 17:37:28 UTC
Evince should mark the position when scrolling. For exemple if you scroll down, you mark the bottom of the screen prior scrolling. This mark can be achieved by flashing a line at that position.

Why? Because when you read and scroll, the eye lose the position in the text. Having a slow flashing like that would allow the eye to jump back easily. AFAIK, Acrobat Reader does it.
Comment 1 Petr Sýkora 2006-06-25 12:49:16 UTC
gv does it too

I think that this feature is realy helpful for finding the line where you were before the scroll.
Comment 2 Nickolay V. Shmyrev 2006-06-25 12:57:02 UTC
Agree, patch is welcome
Comment 3 Wouter Bolsterlee (uws) 2006-11-04 19:42:10 UTC
Duplicate of #170871 I guess.

*** This bug has been marked as a duplicate of 170871 ***
Comment 4 Petr Sýkora 2006-11-04 20:38:41 UTC
I don't think it's duplicate. In 170871 the idea is, to gray out the area that will be hidden by the scroll, but in this "thread" the idea is to mark the area, that was exposed by the scroll. I think that marking area that will be hidden is only "useless eye-candy" (for me) but marking area that was exposed seems to me as useful hint.
Comment 5 Wouter Bolsterlee (uws) 2006-11-04 21:12:59 UTC
I agree that they're not identical, but they're about the same thing. I've updated the description of bug #170871 accordingly.