From: Hans Hagen <pragma@wxs.nl>
Subject: Re: pdfstartview
Date: Wed, 01 Feb 2006 23:28:13 +0100 [thread overview]
Message-ID: <43E135FD.1050405@wxs.nl> (raw)
In-Reply-To: <Pine.LNX.4.58.0602012206130.11728@gaston.free.fr>
� wrote:
> On Wed, 1 Feb 2006, Hans Hagen wrote:
>
>
>>>> That is:
>>>> - when starting acroread, the view is "minwidth"
>>>> - and the mode is "FullScreen"
>>>> - and when clicking on a reference, the zoom-level does *not* change
>>>>
>
>
>> hey, since when don't you read the source any more ...
>>
>> \setupinteraction[focus=fit|width|height|minwidth|minheight|standard|<empty>
>>
>
> Hello Hans,
> "focus=..." does *not* set the right zoom-level at startup of acroread
> and it *changes* the zoom-level when clicking on a reference.
>
> So, my suggestion for our needs is "startfocus=...".
>
one of the problems is (and this has changed in viewer over time, which is why i never bothered too much about it) is that the opening options are controlled differently from the annotation views
links:
\setupinteraction[state=start,focus=width]
opening:
\setupinteraction[state=start,focus=width,openaction=FitWidth]
or
% \setupinteractionscreen[option=max] % bookmark fit doublesided
or (fails):
% \setupinteraction[state=start,focus=width,openaction=page(1)]
FitWidth and FullScreen don't go well together (kind of contradict);
The open action can be chained as can other goto's:
openaction={page(2),FitWidth}]
it is possible to use FitH trickery with infinity offsets but it's not only ugly but i also consider it subjected to changes in future viewer versions; in the past i've done numerous tests with such features but nowdays i tend to be a bit less eager to implement potentially messy features
FitWidth is mapped onto a named action which is rather robust
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-01 22:28 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 ` Hans Hagen [this message]
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 ` pdfstartview Hans Hagen
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=43E135FD.1050405@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).