Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rapid cursor not ideal for long skips #8

Open
jpreiss opened this issue Apr 30, 2022 · 2 comments
Open

Rapid cursor not ideal for long skips #8

jpreiss opened this issue Apr 30, 2022 · 2 comments

Comments

@jpreiss
Copy link
Owner

jpreiss commented Apr 30, 2022

In the question-asking period after a presentation, we often need to traverse almost the whole slide deck. This can be a little slow using rapid cursor. For example, a 1-hour talk that uses Beamer transitions might have around 60 slides according to numbering but more like 100 pages in the PDF.

In PPT-like software, presenters sometimes exit to the editor view and scroll to the desired slide. This is also helpful because the numbering in the PPT editor corresponds to the "logical" numbering shown on the slide. For PDFs, we only know the rendered page index and not the logical slide number, so even if we implemented this view (lots of work) it wouldn't be as useful.

In a perfect world we could read logical slide numbers - maybe this is stored as metadata somewhere? If so, we could use the keyboard for instant skipping.

Possibly speeding up rapid cursor is good enough for us.

@jpreiss
Copy link
Owner Author

jpreiss commented Apr 30, 2022

The command pdfinfo -dests gives page numbers for things like theorems and numbered equations. There is probably some way to make Beamer create such a destination for every slide. Then we could parse the output of this command (assuming pdf2image doesn't already have that functionality) to reconstruct the mapping from a logical slide number to a set of page numbers. Also sounds like a lot of work.

@jpreiss
Copy link
Owner Author

jpreiss commented Apr 30, 2022

For now, just speed up rapid traverse and get rid of dissolves so it's easier to see when to stop. in 0d1f368

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant