Re: Interactive documents

[Hans Hagen <pragma@wxs.nl>]

At 07:59 PM 2/10/01 +0100, Giuseppe Bilotta wrote:
>Hello,
>a couple of question on interactive documents.
>
>Since I use interaction also on "printable" documents,
>I find a feature to be a nuisance: when I click on a link,
>Acrobat sets the veiw to "fit in window", which I don't like.
>I assume the problem being using page destinations instead of
>named ones ... is there and advantage in this? is it possible
>to turn it off (so that the proper destination is reached,
>preserving the zoom factor)?

Page destinations are more save, especially in the past viewers have been
buggy with respect to named destination [some funny sort / search
optimization bugs in acroread 2 and 3] so this is why i always use page
destinations when possible; right from the start context supported the dual
scheme (although acro v 1 only had page dest while for instance dviwindo
only had neamed ones]. Page dest are more efficient too, but they need more
housekeeping in the macro package.

Concerning your problem: in spec-fdf you wile find something \setuppageview
which you can change into: 

\definespecial\dosetuppageview#1%
  {\processaction
     [#1]
     [\v!passend=>\def\PDFpageviewkey{   fit}%
                  \def\PDFpageviewwrd{  /Fit},
      \v!breedte=>\def\PDFpageviewkey{  fith}%   % watch the v-h
                  \def\PDFpageviewwrd{ /FitH},   % swapping here
       \v!hoogte=>\def\PDFpageviewkey{  fitv}%   % and here and
                  \def\PDFpageviewwrd{ /FitV},   % here too
%   \v!standaard=>\def\PDFpageviewkey{  xyz 0 0 0}%
%                 \def\PDFpageviewwrd{ /XYZ 0 0 0},
      \s!unknown=>\def\PDFpageviewkey{   fit}%
                  \def\PDFpageviewwrd{  /Fit}]%
   \edef\PDFpageview{/View [\PDFpageviewwrd]}}

with a aslightly adapted \dodosetupinteraction: 

\def\dodosetupinteraction[#1]% % \dosetupinteraction == special
  {\getparameters[\??ia][#1]%
   \doifelse{\@@iastatus}{\v!start}
     {\iflocation\else
        \showmessage{\m!interactions}{2}
          {\ifusepagedestinations\space(PAGE)\fi}%
        \global\locationtrue
      \fi}
     {\iflocation
        \showmessage{\m!interactions}{3}
          {\ifusepagedestinations\space(PAGE)\fi}%
        \global\locationfalse
      \fi}%
   \iflocation
     \enablemode [\systemmodeprefix\v!interactie]%
   \else
     \disablemode[\systemmodeprefix\v!interactie]%
   \fi
   \dosetuppageview{\@@iafocus}%
   \doifsomething{\@@iabereken}
     {\doregistercalculationset\@@iabereken}%
   \doifelse{\@@iastrut}{\v!ja}
     {\locationstruttrue}
     {\locationstrutfalse}%
   \doifelse{\@@iaklik}{\v!ja}
     {\highlighthyperlinkstrue}
     {\highlighthyperlinksfalse}%
   \doifelse{\@@iasplitsen}{\v!ja}
     {\locationsplittrue}
     {\locationsplitfalse}%
   \doifelse{\v!nieuw}{\@@iascherm}
     {\gotonewwindowtrue}
     {\gotonewwindowfalse}%
   \doifelse{\@@iapagina}{\v!ja}
     {\global\usepagedestinationstrue}
     {\global\usepagedestinationsfalse}}

and a setup like this: 

\setupinteraction[focus=width,state=start]

you have more control (width, height, fit). 

There is no way to preserve the current zoom, although the pdf spec
suggests it. If you find the right way ... 

Zooming and alike has always been buggy / fuzzy in pdf. This is why i never
finished proper thread support (and probably will remove it). It has to do
with the fact that annotations have a separate layer in pdf.  

>Second question: I have a document to be produced in both
>electronic and printable version. I use the \coupledocument
>feature (but it seems not to work).

It's a two stage def: 

\coupledocument
  [alternative] % symbolic name 
  [docu-p] % name of paper version 
  [chapter,section,subsection]
  [the printable version]

\setuphead
  [chapter,section,subsection]
  [file=alternative]

and the same for the screen doc. 

>I produce the two documents this way:
>
>texexec --pdf --mode=screen --result=usatex1-e usatex1
>
>texexec --pdf usatex1
>
>I have to use this order because creating the screen version
>deletes the print version (--result renames the file after
>completion). Two questions:

tex has fixed output names, so there is no other decent way; this is why i
use two times a suffix in that case (-s and -p). 

>1) MiKTeX 2.0 allows to specify the resulting filename;
>shouldn't texexec take advantage of this when --result is
>specified?

dunno, since i don't run miktex i cannot test it, also, the main name is to
be the original in order not to get problems with all kind of internal refs
and names and so; at most you would save a couple of renames which does not
take that much time 

>2) Is it possible to obtain both documents with a single run?

Eh, i don't think so, since I suppose that you use different layouts. 

Hans
-------------------------------------------------------------------------
                                  Hans Hagen | PRAGMA ADE | pragma@wxs.nl
                      Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
 tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------