From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: question on page transitions
Date: Sat, 25 Jul 2020 19:28:27 +0200 [thread overview]
Message-ID: <068d11d0-2c18-695c-3e7b-d4c2750f2552@gmx.es> (raw)
Dear list,
I have a question about page transitions (lines 297-304 from scrn-pag.mkvi):
\def\scrn_transitions_set_indeed
{\begingroup
\edef\currentinteractionscreendelay{\interactionscreenparameter\c!delay}%
\clf_setpagetransition
n {\scrn_transitions_list}%
delay \ifx\currentinteractionscreendelay\v!none
\zerocount\else\currentinteractionscreendelay\fi
\relax
\endgroup}
I wonder whether the "delay" option in \setupinteractionscreen defines
the number of seconds for the page or for the transition.
From what I read in the code above, I would say that the duration is
defined for the transition itself.
Inspecting the output PDF code in generated documents, the duration is
set for the page.
In PDF code. /Page <</Duration 5>> sets the number of seconds for the
page
(https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#search=duration).
/Page <</Trans <</D 5>> >> sets the number of seconds for the transition
(https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#nameddest=G11.2295795).
With the followling sample:
\setuppapersize[A9,landscape]
\setupinteraction[state=start]
\setupinteractionscreen[option=max, delay=5]
\setuppagetransitions[random]
\setupbodyfont[50pt]
\starttext
\dorecurse{2}{%
\startmakeup[page][style=\bf\ss, align=center]
\recurselevel
\stopmakeup%
}
\stoptext
The output PDF document may contain a /Page object such as:
6 0 obj
<<
/Contents 4 0 R
/Dur 5
/Trans <<
/Di 90
/M /O
/S /Fly
>>
/Type /Page
>>
endobj
This forces the viewer to advance the page after 5s. To have a
transition duration of 5s, it should read:
6 0 obj
<<
/Contents 4 0 R
/Trans <<
/D 5
/Di 90
/M /O
/S /Fly
>>
/Type /Page
>>
endobj
https://www.adobe.com/content/dam/acom/en/devnet/pdf/PDF32000_2008.pdf#nameddest=G11.2104292
shows the difference between /Dur and /D.
Could anyone confirm whether this should be fixed (or I’m missing
something)?
Many thanks for your help,
Pablo
--
http://www.ousia.tk
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
reply other threads:[~2020-07-25 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=068d11d0-2c18-695c-3e7b-d4c2750f2552@gmx.es \
--to=oinos@gmx.es \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).