From: Hans Hagen <pragma@wxs.nl>
Subject: Re: pdfstartview
Date: Fri, 03 Feb 2006 21:07:02 +0100 [thread overview]
Message-ID: <43E3B7E6.9040507@wxs.nl> (raw)
In-Reply-To: <43E3A10A.2090602@elvenkind.com>
Taco Hoekwater wrote:
> Peter M�nster wrote:
>
>> On Thu, 2 Feb 2006, Taco Hoekwater wrote:
>>
>>
>>
>>> This works (but only because object 4 is the first page in my Pdf
>>> document). I do not know if this can be 'internalized'?
>>>
everything can ... but i've learned my lessons and not everything should
(unless pdf is stable -)
>>> \setupinteraction[state=start,focus=minwidth]
>>> \doPDFaddtocatalog{/PageMode /FullScreen
>>> /OpenAction << /S /GoTo /D [4 0 R /FitBH ] >> }
>>>
>> Hello Taco,
>> indeed, this seems to work!
>> Only 2 problems remain:
>> - the object number should be found automatically (as you've already written)
>> - when clicking on a reference, the zoom-level still changes...
>>
>
> I assume that is because the /FitBH should match what is implied by
> the focus=minwidth, I just freewheeled a bit. The /D(estination) in
> this is the top-level page object for page 1, so it actually does an
> implied \goto{}[firstpage].
>
> I don't know how to get the object number (I simply reverse-
> engineered the hyperref output). It is not all that sneaky an
> approach. I don't think it will work on pre 5.0 acroread, though.
>
over time, the possibilities of pdf has improved as well as changed:
- first there were only page destinations
- then came names ones
- cross doc links were implemented differently
- then there was a behavioural change in optimizers/viewers
- views are not supported in certain named destinations
- etc
this all resulted in context supporting a mixture of destinations (page
and named) and either or not providing support for views, depending on
what method was chosen.
the solution that taco suggests is possible now that in pdftex we have
pdfpageref (ok, a bit of a lie: context could sorty out page object ref
numbers itself but i never used that here due to mem limitations which
now are gone)
however, one needs to keep in mind that if we support things like this
we also assume recent viewers (ok now, but some time ago both linux and
apple were behind with viewers)
i'll adapt the pdf driver a bit so that we can do what you want, under
the assumption that everyone runs the latest pdftex (i normally take a
one year period before i assume that) as well as that one has a version
5+ viewer.
\setupinteraction[state=start,focus=width,openaction=firstpage,page=yes]
\starttext
the page actions (like firstpage) will use the obj ref approach now instead of the auto page destinations, and with page=yes one forces
all destinations to be page destinations (which is needed on order to
get the view working; keep in mind that one then looses cross document named referencing, only cross doc page referencing remains (no real problem, unless one refers from outside a pdf)
\stoptext
i'll upload a current with a slightly adapted driver (extra option which is now default; taco: just run a diff on spec-fdf.tex and you'll see what happens)
\setupinteraction[state=start,focus=width,openaction=page(3),page=yes]
\starttext
test \page
test \page
test \page
test \page
test \page
\stoptext
works ok too
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-02-03 20:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 15:33 pdfstartview Peter Münster
2006-02-01 16:17 ` pdfstartview Mojca Miklavec
2006-02-01 20:45 ` pdfstartview Hans Hagen
2006-02-01 21:10 ` pdfstartview Peter Münster
2006-02-01 22:28 ` pdfstartview Hans Hagen
2006-02-03 18:02 ` pdfstartview Peter Münster
2006-02-03 20:20 ` pdfstartview Hans Hagen
2006-02-16 17:55 ` pdfstartview Peter Münster
2006-02-16 21:24 ` pdfstartview Hans Hagen
2006-02-17 6:10 ` pdfstartview Peter Münster
2006-02-01 22:32 ` pdfstartview Taco Hoekwater
2006-02-02 9:13 ` pdfstartview Hans Hagen
2006-02-02 1:16 ` pdfstartview Mojca Miklavec
2006-02-02 9:01 ` pdfstartview Taco Hoekwater
2006-02-03 17:56 ` pdfstartview Peter Münster
2006-02-03 18:29 ` pdfstartview Taco Hoekwater
2006-02-03 19:43 ` pdfstartview Hans Hagen
2006-02-03 19:58 ` pdfstartview Peter Münster
2006-02-03 20:07 ` Hans Hagen [this message]
2006-02-02 9:16 ` pdfstartview Hans Hagen
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=43E3B7E6.9040507@wxs.nl \
--to=pragma@wxs.nl \
--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).