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 644246 - timer feature in presentations
timer feature in presentations
Status: RESOLVED DUPLICATE of bug 454731
Product: evince
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-03-08 21:57 UTC by 255993
Modified: 2011-03-27 21:34 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description 255993 2011-03-08 21:57:29 UTC
Evince lacks ability to track time and position in slides during presentation. It could have feature simmilar to mgp timer [http://member.wide.ad.jp/wg/mgp/].

Idea is to add edit option and widget as in #454731
Menu -> Edit -> Presentation
Presentation:
+==========================================+
||DUALHEAD\|Timer\                         |
|+---------+      \-----------------------+|
||                                        ||
||                                        ||
||[ ] Show timer during presentation      ||
||                                        ||
|| Estimated presentation time:_____min.  ||
||                                        ||
||                                        ||
|+----------------------------------------+|
+------------------------------------------+


And during presentation there should be small progressbar showing position in slides and countdown for actual slide (estimated time/number of slides) on the bottom of the screen.

Estimated presentation time should be savet in file metadata. something like metadata::evince::presentation::timer: on/off
metadata::evince::presentation::time: 30
Comment 1 255993 2011-03-27 21:34:03 UTC
I'm closing this as this feature should be part of control window of dualhead presentations.

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