% \iffalse meta-comment % % Copyright (C) 2004-2010 by Robert Marik % ---------------------------------------------------------- % % This file may be distributed and/or modified under the % conditions of the LaTeX Project Public License, either version 1.2 % of this license or (at your option) any later version. % The latest version of this license is in: % % http://www.latex-project.org/lppl.txt % % and version 1.2 or later is part of all distributions of LaTeX % version 1999/12/01 or later. % % \fi % % \iffalse %<*driver> \ProvidesFile{fancytooltips.dtx} % %\NeedsTeXFormat{LaTeX2e}[1999/12/01] %\ProvidesPackage{fancytooltips} %<*package> [2010/06/10 v1.8 fancytooltips.dtx file] % % %<*driver> \documentclass{ltxdoc} \EnableCrossrefs \CodelineIndex \RecordChanges \usepackage[pdftex]{color} \usepackage[filename=tip,mouseover,movetips]{fancytooltips} \buttontipwidth=2cm \buttontipheight=2cm \begin{document} \color{black} \DocInput{fancytooltips.dtx} \PrintIndex \end{document} % % \fi % % \CheckSum{1075} % % \CharacterTable % {Upper-case \A\B\C\D\E\F\G\H\I\J\K\L\M\N\O\P\Q\R\S\T\U\V\W\X\Y\Z % Lower-case \a\b\c\d\e\f\g\h\i\j\k\l\m\n\o\p\q\r\s\t\u\v\w\x\y\z % Digits \0\1\2\3\4\5\6\7\8\9 % Exclamation \! Double quote \" Hash (number) \# % Dollar \$ Percent \% Ampersand \& % Acute accent \' Left paren \( Right paren \) % Asterisk \* Plus \+ Comma \, % Minus \- Point \. Solidus \/ % Colon \: Semicolon \; Less than \< % Equals \= Greater than \> Question mark \? % Commercial at \@ Left bracket \[ Backslash \\ % Right bracket \] Circumflex \^ Underscore \_ % Grave accent \` Left brace \{ Vertical bar \| % Right brace \} Tilde \~} % % % \changes{v1.0}{2007/02/15}{Initial version} % % \changes{v1.1}{2007/02/20}{Clener code, better documentation, fix % for bug with delayinterval macro, support for dvips and Distiller % users.} % % \changes{v1.2}{2007/03/01}{Better support for dvips users, buttons % for icons are created automatically using eso-pic package and have % the name "ikona.pagenumber", new option \texttt{movetips}, tooltip % appears on the current page only and, as a consequence, animations % are faster.} % % \changes{v1.3}{2007/05/08}{Fixed bug which appears in dvips route. % Improved documentation -- added a note about the required version % of eforms.sty} % % \changes{v1.4}{2009/04/29}{Added support for presentations (like % \texttt{pause} command for texpower).} % % \changes{v1.5}{2009/05/05}{Handling number of pages via aux file % (fixes some problems issued by previous modification and page % break near tooltip).} % % \changes{v1.6}{2010/04/10}{Added options \texttt{debug}, % \texttt{active} and \texttt{inactive}, added an example with % automatical previews for equations and floats. Added handling of % this.dirty and app.focusRect. Changed the name of the file with % tooltips. Added starred version of \texttt{tooltip} command.} % % \changes{v1.7}{2010/05/20}{Added options \texttt{blur} and % \texttt{fg}, cleaned some command names} % % \changes{v1.8}{2010/06/10}{Added hook do insert stuff on each page.} % % \GetFileInfo{fancytooltips.dtx} % % \DoNotIndex{\newcommand,\newenvironment} % % % \title{The \textsf{fancytooltips} package\thanks{This document % corresponds to \textsf{fancytooltips}~\fileversion, dated % \filedate.} \thanks{Supported by grants 18/2006, 99/2008 and 131/2010 % of Higher % Education Development Fund (FRV\v S) }} \author{Robert Ma\v r\'\i k \\ % \texttt{marik@mendelu.cz}} % % \maketitle % % \section{Introduction} % % The package |fancytooltips| is a package for \LaTeX. The pdf can be % created by pdflatex or by latex + dvips + % AdobeDistiller\footnote{not free ps2pdf} + Adobe % Acrobat\footnote{not free Adobe Reader.}. It allows to create % tooltips in a similar way like |cooltooltips| package, but the % tooltip is a page from another PDF file. In this way you can use % mathematics, pictures and animations in your tooltips. The % resulting PDF file can be used also with free Abobe Reader. % % The \color{black}tooltips are activated by clicking the active area % on the screen and deactivated after closing page or by moving mouse % outside the link. You can try the links \tooltip{here}{1} % (Einstein's formula) and also \tooltipanim{here}{2}{7} (animation -- % numbers from 1 to 6). You have to use the free Adobe Reader or % nonfree Adobe Acrobat to see the effect (xpdf, evince and others % fail to work with JavaScripts). For more examples how the % presentation may look like see the |examples| subdirectory. % % Similar functionality can be achieved using |pdfcomment| (smaller % size of the resulting PDF, but restricted to plain text), |ocgtools| % (works with layers, only |pdflatex| is supported) and Acro\TeX{} % (works with layers, only |latex| + |dvips| + Adobe Distiller + Adobe % Acrobat are supported). All these ``similar'' packages allow to % write the text for he tooltips and the text for the main document in % one file. In contrast to this approach, |fancytooltips| package % makes use of an external file. However, if you prefer to write both % tooltips in one file, you can preprocess your file using |preview| % package and extract tooltips automatically, as shown in the % |examples/fancy-preview| directory. % % The buttons are created using |eforms.sty| which is a part of % AcroTeX bundle. % % \section{Usage} % \subsection{How the package works} % We have to prepare external file with content of tooltips first. % The pages of this external file are inserted as icons at hidden % buttons into the presentation. Whenever we use a command to insert % tooltip, the following actions are performed % \begin{itemize}\item % The current page is covered by invisible transparent button which % spans across the whole page (the information about the pages with % tooltips is stored in |aux| file and hence we have to run \LaTeX{} % \textit{three times}). The button has an associated JavaScript % action to close all tooltips (i.e. make itself and other related % buttons hidden). % \item The button is created in text. This button is transparent, % covers the text typeset by \TeX{} into |\hbox| of dimension 0 pt % and allows to activate a JavaScript. This JavaScript takes the % picture required, puts this picture as icon to the button which % covers the corresponding page and makes this button visible. % \item Each page has an associated action which closes all tooltips % when the page is opened. % \end{itemize} % % \subsection{The file with tooltips} % The file with tooltips is an ordinary pdf file, one tooltip per % page, tooltips should be in the top right corner at the page, in a % colored box and the rest of the page should be transparent. If you % consider to use |movetips| option (see below), then every page % should have the dimensions equal to the dimensions of the colored % box with tooltip\footnote{Look at the files \texttt{tooltipy.tex} and % \texttt{tooltipy.pdf} from |examples| subdirectory for a simple example % how to meet this condition under pdf\LaTeX}. We also provide % simple cross referencing mechanism to reffer to the tooltips. If the % pdf file is created by \LaTeX, \DescribeMacro{\keytip} you can % define keywords to reffer to the pages using |\keytip| command. % Simply put |\usepackage[createtips]{fancytooltips}| into preamble % and write \texttt{\string\keytip}\marg{foo} in document. This writes % information about keyword \meta{foo} and the pagenumber into file % |\jobname.tips|. % % \subsection{The file with presentation -- pdf\LaTeX users} % In the file with presentation, the user is responsible % \begin{itemize} % \item input either |color| or |xcolor| package in the % preamble % \item \LaTeX{} the file two times (we write some macros into |aux| % file). % \end{itemize} % This is not comfortable for the user, but everybody uses different % set of packages and from this reason, this part is left to the user. % (And among others, the |color| or |xcolor| package is probably % inputted by the package which is used to build the presentation.) % % \begin{description}\def\iitem#1{\item[#1]}\sloppy\raggedright % \iitem{filename} To input the tooltips from file % \meta{foo.pdf} call the package with |filename| option: % |\usepackage[filename=foo]{fancytooltips}|. % % \iitem{movetips} By default, tooltip appears in the % top right corner of the page (use View--PageLayout-Single Page in % your Adobe Reader, please). If the option |movetips| is used, then % tooltip appears close to the mouse pointer. More precisely, tooltip % appears with left down corner at the mouse position, if there is % enough place. If not, tooltip appears with right down corner at the % mouse position. Finally, the tooltip is shifted down to fit the % page, if necessary\footnote{This option works in this way if every % page of the file with tooltips has dimensions of the box with % tooltip. See the \texttt{examples} subdirectory.}. % % % \iitem{mouseover} If you use |mouseover| option, % then tooltip appears if you move the mouse pointer to the active % area (no clicking is necessary). % % \iitem{inactive} This option makes the package % inactive. % % \iitem{active} This option forces the package % active even if |inactive| option is loaded. % % \iitem{blur} The rest of the page is blurred, when showing % tooltip. Use either |\usepackage[blur]{fancytooltips}| or % |\usepackage[blur=number]{fancytooltips}|, where |number| is % a number between 0 and 1. (Note that we use transparent package % and hence this could have an influence on the colors of the % document and could make your PDF less portable.) This option is % allowed in pdf\LaTeX{} mode only. If this options brakes colors % only on the page which include tooltips, you may want to use % option |fixcolor| to fix it. % % \iitem{debug} Prints two alerts reporting success or problems when % opening PDF file in Adobe Acrobat (Adobe Reader). Use this option % to find possible source of problems. See also the section % Troubleshooting \dots in this manual. % % \iitem{noextratext} Do not append any mark at the end of the link % which opens tooltips (see help for |\tooltip|). % % \iitem {fg} The button for displaying pictures is placed on % background and the buttons which activate tooltips are placed % immediately in the text by default. With |fg| option all these % buttons are placed into foreground after the page is completed. We % use |\pdfsavepos| command and keep track of the position for % buttons in aux file and hence this option works in pdf\LaTeX\ only % and the file needs more compilations. This option does not do % anything in dvi mode now (despite the fact that pdf\LaTeX\ % provides the feature also for dvi mode), but this could be changed % if someone requests this feature. Use this option for example, if % you use buttons and forms in your PDF (like tests produced by % Acro\TeX) and the tooltips should be on the top when displayed. % % \end{description} % % \DescribeMacro{\tooltip} The user can put the tooltip into her or % his presentation using the command % \texttt{\string\tooltip}{\marg{stuff}\marg{keyword-or-pagenumber}} % where \meta{stuff} is the printed text in \meta{tooltipcolor} color % and \meta{keyword-or-pagenumber} is either the pagenumber of the % tooltip in the external file or the keyword defined by |\keytip| % command and stored in |\TooltipFilename.tips| file, where % |\TooltipFilename| is set automatically from the |filename| option. % \DescribeMacro{\TooltipExtratext} The printed text \meta{stuff} is % followed by |\TooltipExtratext| command. The default value is small % blue soap, as you have seen in the second paragraph of this % documentation. There is a package |noextratext| which defines % |\TooltipExtratext| to be empty. \DescribeMacro{noextratext option} % If \marg{keyword-or-pagenumber} is not recognized as valid keyword % for tooltips, % % The text \marg{stuff} is inserted in |\hbox| by % |\tooltip|. \DescribeMacro{\tooltip*}With starred version of the % |\tooltip| macro the text \marg{stuff} is not inserted into the box % and the active button dos not cover the text \marg{stuff}, but % covers the mark produced by |\TooltipExtratext|. % % \DescribeMacro{\tooltipanim}\DescribeMacro{\tooltipanim*} The user % can put a series (animation) of tooltips into the presentation by % using \texttt{\string\tooltipanim}\marg{stuff}\marg{start}\marg{end} % command, where \meta{start} and \meta{end} are keywords defined by % |\keytip| command or page numbers. \DescribeMacro{\delayinterval} % The delay between two frames is |\delayinterval| milliseconds. The % default value is 200, you can change it by command % |\def\delayinterval{100}|. There is also starred version which works % similarly like |\tooltip*| command. % % \DescribeMacro{\FancyHook} Redefines |\ref| and |\eqref| commands to % work with preview, see the demo files in |example/fancy-preview| % directory. % % \DescribeMacro{\TooltipRefmark} Extra text added to |\ref| and % |\eqref| commands with previews, see the demo files in % |example/fancy-preview| directory. The default value is the same as % for |\TooltipExtratext|. % % \subsection{Changes for dvips users} % Dvips users also have to prepare tooltips into PDF file, not eps as % usual. But we have to insert these tooltips in Adobe Acrobat Pro % program. If you use Acrobat Pro version 8.1 and later, install the % file \texttt{aeb.js} from AcroTeX eDucation bundle as described in % the documentation to AcroTeX.\footnote{If you do not install % \texttt{aeb.js} properly, you can still create your presentation , % but you have to import fdf file manually, see the section % Troubleshooting and known problems.} % % Since \LaTeX{} is not capable to find the number of pages in % external PDF file with tooltips, dvips users have to specify option % |dvips| in |fancytooltips| package. \DescribeMacro{pages} You have % to use also a |pages| option with the number of pages in the PDF % file with tooltips, if you use dvips route. You have to call the % package by % something like this:\\ % |\usepackage[dvips,filename=tooltipy,pages=27]{fancytooltips}| % % You have to |latex| (two times) and |dvips| your file first. This % produces |filename.ps| and |Tooltipsdljs.fdf| files. Distill the % |filename.ps| file into |filename.pdf| and open this file by Adobe % Acrobat Professional -- this imports macros from |Tooltipsdljs.fdf| % file. In Acrobat's JavaScript console (open by |Crtl+J|) run (using % |Ctrl+Enter|) the command |ImportTooltips();| which is defined for % the document. This command inserts invisible buttons on the first % page, imports icons (the file with icons specified as % \meta{filename} parameter when loading fancytooltips must be in % working directory). You should see a message ``\texttt{importing % pictures}'' and the command returns 1 when finished. Then % \textbf{save the file} (you can use the same name). If the command % |ImportTooltips();| fails, you either have not the PDF file with % tooltips in current directory, or the PDF file does not contain % JavaScripts. In the latter case insert document level JavaScripts % manually as described in the next section. % % \section{Troubleshooting and known problems} % The source code is in Mercurial repository at % \url{http://bitbucket.org/robert.marik/fancytooltips/}. You can also % report problems and issues in the forum at this site. The code on % |bitbucket.org| is considered as development version and repository % for older versions. The last stable version is always the version % from CTAN. % \begin{itemize} % \item % The package works with |eforms.sty| from version % 2006/10/03 v1.0a. You can download this or newer version from % www.arotex.net site. % \item If the graphics included by |\TooltipExtratext| and % |\TooltipRefmark| has colors with \textbf{custom opacity}, Adobe % Acrobat Pro sometimes renders the pictures bad. No problems of % this type have been observed with free Adobe Reader. % \item For \textbf{dvips} users: In some cases the file % |Tooltipsdljs.fdf| is \textbf{not imported automatically} % (probably some setting in Adobe Acrobat or new versions of % |eforms.sty| and |insdljs.sty|). In this case you do not see any % message when using |debug| option. You have troubles of this type % if you see in the Javascript console (Ctrl+J) error messages like % ``\texttt{aebTrustedFunctions is not defined 3:Page:Open % CloseTooltips is not defined 1:Page:Open}''. In this case you % have to import the file |Tooltipsdljs.fdf| \textbf{manually from % ``Form'' menu} in Adobe Acrobat Pro. Then go to the JavaScript % console and run |ImportTooltips();| command. % \end{itemize} % % Follow the points below if you want to find the source of your % problems. % \begin{itemize} % \item For dvips users it is a good idea to check that Acro\TeX{} is % properly installed. Do the demo files from Acro\TeX{} work for you? % \item Try to use |debug| option, prepare the PDF file and open it in % Adobe Acrobat or Adobe Reader. % \begin{itemize} % \item You should see two messages when opening the file. If not, % the Javascript do not work in your document (are not inserted % properly). % \item Both messages should report success for pdflatex users. For % dvips users one of the message should report error and if you % run |ImportTooltips();| command in Javascript console, you should % see a message in Javascript console which confirms that the % pictures from external PDF file have been imported. If you save % the PDF file and open again, both messages should report % success. % \end{itemize} % \end{itemize} % % \PrintChanges % \StopEventually{} % % \section{Implementation} % \begin{macrocode} %<*package> \RequirePackage{graphicx} \RequirePackage{xkeyval} \RequirePackage{atbegshi} \newif\if@fancytooltips@createtips\@fancytooltips@createtipsfalse \DeclareOptionX{createtips}{\@fancytooltips@createtipstrue} \newif\ifTooltip@usepdftex\Tooltip@usepdftextrue \DeclareOptionX{dvips}{\Tooltip@usepdftexfalse} \newif\if@fancytooltips@extratext\@fancytooltips@extratexttrue \DeclareOptionX{noextratext}{\@fancytooltips@extratextfalse} \newif\if@fancytooltips@movetips\@fancytooltips@movetipsfalse \DeclareOptionX{movetips}{\@fancytooltips@movetipstrue} \newif\if@fancytooltips@mouseover\@fancytooltips@mouseoverfalse \DeclareOptionX{mouseover}{\@fancytooltips@mouseovertrue} \newif\if@fancytooltips@inactive\@fancytooltips@inactivefalse \DeclareOptionX{inactive}{\@fancytooltips@inactivetrue} \newif\if@fancytooltips@active\@fancytooltips@activefalse \DeclareOptionX{active}{\@fancytooltips@activetrue} \newif\if@fancytooltips@fg\@fancytooltips@fgfalse \DeclareOptionX{fg}{\@fancytooltips@fgtrue} \DeclareOptionX{filename}{\xdef\TooltipFilename{#1}} \DeclareOptionX{pages}{\xdef\TooltipPages{#1}} \newif\if@fancytooltips@blur\@fancytooltips@blurfalse \DeclareOptionX{blur}[0.4]{\@fancytooltips@blurtrue \xdef\fancytooltips@transparency{#1}} \newif\if@fancytooltips@fixcolor\@fancytooltips@fixcolorfalse \DeclareOptionX{fixcolor}{\@fancytooltips@fixcolortrue} \def\fancytooltipsdebugmsg{} \DeclareOptionX{debug}{\def \fancytooltipsdebugmsg { if (this.getField("ikona") == null) {app.alert("No buttons for placing tootlips are available. Contact the author. The file may need more compilations.");} else {app.alert("Buttons for placing tooltips are available. Congratulations! Hope everything will work.");} if (this.getField("animtiph") == null) {app.alert("No hidden buttons containing tooltips available. The interactive features will not work. \n\n If you created the file by dvips, run the command ImportTooltips() in the Javascript console (Ctrl+J, write the command followed by semicolon and Ctrl+Enter).");} else {app.alert("Hidden buttons containing tooltips are available. Congratulations! Hope everything will work.");} }} \ProcessOptionsX \if@fancytooltips@blur \ifTooltip@usepdftex\else \@fancytooltips@blurfalse \AtEndDocument{\PackageWarning{fancytooltips} {Blur option is incompatible with dvips. ^^J The option blur is turned off }} \fi \fi \ifTooltip@usepdftex\else \@fancytooltips@fgfalse \fi \newdimen\buttontipwidth \newdimen\buttontipheight \newdimen\fancy@a \newdimen\fancy@b \newdimen\fancy@layerHshift\fancy@layerHshift=0pt \newdimen\fancy@layerVshift\fancy@layerVshift=0pt \newdimen\fancy@button@Vshift \fancy@button@Vshift=0pt \newdimen\fancy@button@Hshift \fancy@button@Hshift=0pt \newtoks\pos@fancy@toks \if@fancytooltips@active\@fancytooltips@inactivefalse\fi \if@fancytooltips@inactive \newcommand{\tooltip}{\@ifstar\tooltip@Star\tooltip@NoStar}% \newcommand{\tooltip@Star}[2]{#1}% \newcommand{\tooltip@NoStar}[2]{#1}% \newcommand{\tooltipanim}{\@ifstar\tooltipanim@Star\tooltipanim@NoStar}% \newcommand{\tooltipanim@Star}[2]{#1}% \newcommand{\tooltipanim@NoStar}[2]{#1}% \def\keytip#1{}% \def\FancyHook{}% \def\TooltipPage#1#2{}% \let\TooltipExtratext\relax \let\TooltipRefmark\relax \ifx\@ocg@makeknown\undefined \def\@ocg@makeknown#1#2#3{}\fi \def\fancy@@pushButton#1#2#3#4#5#6#7#8{} \def\fancy@@anim@pushButton#1#2#3#4#5#6#7#8#9{} \PackageWarning{fancytooltips}{Fancytooltips inactive}% \expandafter\endinput\fi % \end{macrocode} % Each |\ref| command has associated a number and writes new label % into aux file. If the target page for the ref is different from the % page with this |\ref| command, the corresponding tooltip is inserted. % \begin{macrocode} \newcount\fancycheckcount\fancycheckcount=0 \def\fancy@second#1#2#3#4{#2} \def\FancyHook{ \global\let\oldref\ref \gdef\ref##1{\oldref{##1}\global\advance\fancycheckcount by 1\relax \edef\templabel{fancyanchorref:\the\fancycheckcount}% \expandafter\label\expandafter{\templabel}% \expandafter\ifx \csname FancyToolTip@##1\endcsname\relax \else\hbox to 0 pt{% \expandafter\ifx \csname r@##1\endcsname \relax\else \edef\temp{\csname r@##1\endcsname}% \expandafter\edef\expandafter\fan@tempa\expandafter{\expandafter\fancy@second\temp}% \fi \expandafter\ifx \csname r@fancyanchorref:\the\fancycheckcount\endcsname \relax\else \edef\fan@ttemp{r@fancyanchorref:\the\fancycheckcount}% \expandafter\let\expandafter\fan@temp@w\csname \fan@ttemp\endcsname \edef\fan@temp@ww{\expandafter\fancy@second\fan@temp@w}% \fi \ifx\fan@temp@ww\undefined\else \fi \ifx\fan@tempa\fan@temp@ww\else\smash{% \let\TooltipExtratext\relax\tooltip{\strut\TooltipRefmark}{##1}}% \fi \hss}% \fi} \ifTooltip@usepdftex \def\TooltipRefmark{\hbox {\smash{\raisebox{0.4em}{\includegraphics[width=0.7em]% {fancytipmark.pdf}}}}}% \else \def\TooltipRefmark{\hbox {\smash{\raisebox{0.4em}{\includegraphics[width=0.7em]% {fancytipmark.eps}}}}}% \fi%\ifTooltip@usepdftex } \if@fancytooltips@createtips % \end{macrocode} % This part (three lines) is processed if the option |createtips| is % used. In the opposite case we process the second part, up to the end % of the package. % \begin{macrocode} \newwrite\tipfile \immediate\openout\tipfile \jobname.tips \def\keytip#1{\write\tipfile{\string\tooltipname{#1}{\arabic{page}}}} \expandafter\endinput\fi % \end{macrocode} % This part is processed if the option |createtips| is not used. We % define macros which put the hidden button with the name |ikona.n| in % the background of the page |n|, if one of the commands |\tooltip| or % |\tooltipanim| has been used on this page. Javascripts defined by % |\tooltip| and |\tooltipanim| commands then unhide this button and % show the corresponding picture. % \begin{macrocode} \ifx\TooltipFilename\undefined \PackageWarning{fancytooltips}{** The filename with tooltips is not given. **} \fi \ifTooltip@usepdftex \RequirePackage[pdftex]{eforms} \def\TooltipExtratext{\hbox{\smash{\raisebox{0.4em}{\includegraphics[width=0.7em]% {fancytipmark.pdf}}}}} \else \RequirePackage[dvips]{eforms} \def\TooltipExtratext{\hbox{\smash{\raisebox{0.4em}{\includegraphics[width=0.7em]% {fancytipmark.eps}}}}} \fi%\ifTooltip@usepdftex \if@fancytooltips@extratext\else\let\TooltipExtratext\relax\fi \AtBeginDocument{ \global\buttontipwidth=\paperwidth \global\buttontipheight=\paperheight } \ifTooltip@usepdftex \def\frametip@{% \pdfstartlink user{% /Subtype /Widget /F 6 /T (ikona.\thepage) /FT /Btn /Ff 65536 /H /N /BS << /W 1 /S /S >> /MK << /TP 1 /IF <> >> }% \vbox to \buttontipheight {\vss\hbox to \buttontipwidth{\hss}}\pdfendlink}% \else % \end{macrocode} % For dvips users we use the macros from eqxerquiz.sty package. % \begin{macrocode} \def\everyeqIcon#1{\def\every@eqIcon{#1}} \def\every@eqIcon{} \newcommand\eqIconFTT[4][] {% \push@@Button{#1}{#2}{#3}{#4}{}{\eq@setButtonProps\eq@Button@driver}% {\eqIconDefaults\every@ButtonField\every@eqIcon}% } \def\eqIconDefaults {% \rawPDF{}\S{}\mkIns{/TP 1 /IF<>}\R{0} \CA{}\RC{}\AC{}\BC{}\BG{}\H{B} \textColor{0 g}\Ff{\FfReadOnly} } \def\frametip@{\eqIconFTT[\BC{}\BG{}\F{\FHidden}]% {ikona.\thepage}{\paperwidth}{\paperheight}% }% \fi%\ifTooltip@usepdftex \def\fancytooltips@one{1} \if@fancytooltips@blur \RequirePackage{ocg} \ifx\fancytooltips@one\fancytooltips@transparency \def\transparent#1{} \else \RequirePackage{transparent} \fi \else \ifx\@ocg@makeknown\undefined \def\@ocg@makeknown#1#2#3{}\fi \fi \if@fancytooltips@fg\else \RequirePackage{eso-pic} \def\frametip{% \expandafter\ifx \csname TooltipPage\thepage\endcsname\relax \else \setbox0=\hbox{\frametip@}% \hbox{\raise \dp0 \box0} \fi}% \AddToShipoutPicture{\hbox to 0 pt{\frametip\hss}} \fi \def\fancytooltips@save@position{\pdfsavepos% \write\@auxout{\string\global\string \fancy@layerVshift \the\pdflastypos sp\string\relax}% \write\@auxout{\string\global\string \fancy@layerHshift \the\pdflastxpos sp\string\relax}% } \def\fancy@beginshipout@hook{} \AtBeginShipout{% \TooltipPageopencloseJS \setbox\AtBeginShipoutBox=\hbox{% \hbox to 0 pt{\TooltipHidden}\global\def\TooltipHidden{}% \fancy@beginshipout@hook\if@fancytooltips@fixcolor\hbox to 0 pt{\resizebox{1pt}{!}{\TooltipExtratext}\hss}\fi \hbox{\box\AtBeginShipoutBox}% \ifTooltip@usepdftex \fancytooltips@save@position \if@fancytooltips@blur \expandafter\ifx \csname TooltipPage\thepage\endcsname\relax \else \lower\fancy@layerVshift\hbox to 0 pt{\kern-\fancy@layerHshift\relax \begin{ocg}{fancyOCG\thepage}{fancyOCG\thepage}{0}% \expandafter\transparent\expandafter{\fancytooltips@transparency}% \color{black}% \vbox to 0 pt{\vss\hbox{\vrule width \paperwidth height \paperheight}}% \end{ocg}\hss}% \fi \fi \if@fancytooltips@fg \expandafter\ifx \csname TooltipPage\thepage\endcsname\relax \else \lower\fancy@layerVshift\vbox to 0 pt{\vss\hbox to 0 pt{\kern-\fancy@layerHshift\relax\hbox{\frametip@}\hss}}% \fi \lower\fancy@layerVshift\vbox to 0 pt{\vss\hbox to 0 pt{\kern-\fancy@layerHshift\relax\hbox to 0 pt{\the\pos@fancy@toks\hss}}}% \fi \fi }% }% % \end{macrocode} % In the macros |\tooltip| and |\tooltipanim| we print the text into % box with zero dimensions and then we build a button which covers % this text and has an associated JavaScript action. The important % part is the |\PushButton| macro. You can adjust these macros or % write similar macros which do what you need. % \begin{macrocode} \definecolor{tooltipcolor}{rgb}{0,0,1} \newcount\tooltip@count \newtoks\tooltip@toks \newtoks\tooltip@pagetoks \tooltip@pagetoks={\thepage} \def\tooltippage{} \def\TooltipPage#1#2{% \expandafter\gdef\csname TooltipPage#2\endcsname{#2}% \expandafter\gdef\csname Tooltipcount2page#1\endcsname{#2}% } % \end{macrocode} % We use the hack for Adobe Acrobat suggested by DPS and Jorg at % http://www.acrotex.net/forum/showthread.php?tid=78. % \begin{macrocode} \def\fancy@JS#1{\JS{var DirtyBeforeTooltip=this.dirty; #1 this.dirty=DirtyBeforeTooltip;}} \newcommand{\tooltip}{\@ifstar \tooltip@Star% \tooltip@NoStar% } \newcommand{\tooltip@Star}[2]{{\color{tooltipcolor}#1}% {\let\SaveTooltipExtratext\TooltipExtratext \let\TooltipExtratext\relax \hbox to 0 pt{\tooltip@NoStar{\SaveTooltipExtratext \vrule height 10pt depth 0 pt width 0 pt}{#2}\hss}}} \newcommand{\tooltip@NoStar}[2]{% \global\advance\tooltip@count by 1% \edef\act{\write\@auxout{\noexpand\string\noexpand\TooltipPage{\the\tooltip@count}{\the\tooltip@pagetoks}}}\act \expandafter\ifx\csname Tooltipcount2page\the\tooltip@count \endcsname\relax \global\edef\tooltippage{} \else \global\edef\tooltippage{\csname Tooltipcount2page\the\tooltip@count \endcsname}% \fi \checkTipNumber{#2}\edef\TipNumber{\FindTipNumber{#2}}% \leavevmode \setbox0=\hbox{{\color{tooltipcolor}{#1}}}\copy0\fancy@a=\dp0\advance\fancy@a by \ht0\relax\hbox to 0 pt{\smash{\TooltipExtratext}\hss}\fancy@pushButton{\TipNumber}{\tooltippage}{TooltipField}{\wd0}{\fancy@a}{\dp0}} \def\fancy@tooltip@options#1#2{\BC{}\BG{} \S{}\AA{\AAMouseExit{\fancy@JS{CloseTooltips();}}% \if@fancytooltips@mouseover \AAMouseEnter{\fancy@JS{this.getField("ikona."+(#2)).hidden=false; try {app.clearInterval(animace);}catch (e) {} \if@fancytooltips@movetips nastav(#1,#2);\fi \if@fancytooltips@blur try{ for(var i=0; fancytooltipsOCGs && i> >>} \expandafter\def\expandafter\TooltipPageopencloseJS\expandafter{ \expandafter\global\expandafter\pdfpageattr\expandafter{\fancy@temp}% } \pdfximage{\TooltipFilename.pdf}% \edef\TooltipPages{\the\pdflastximagepages}% \else \edef\fancy@temp{ [ {ThisPage} << /AA << /O << /S /JavaScript /JS (var DirtyBeforeCloseTooltip=this.dirty; CloseTooltips(); this.dirty=DirtyBeforeCloseTooltip;) >> >> >> /PUT pdfmark} \expandafter\def\expandafter\TooltipPageopencloseJS\expandafter{ \expandafter\literalps@out\expandafter{\fancy@temp}} \edef\fancy@@temp{/S /JavaScript /JS ( \fancytooltips@pdfpageattrJS)} \expandafter\OpenAction\expandafter{\fancy@@temp} \fi%\ifTooltip@usepdftex \ifTooltip@usepdftex \def\fancytempA{} \ifx\FancytooltipsAfterClose\undefined\else\edef\fancytempA{\FancytooltipsAfterClose}\fi \def\fancytempAA{} \ifx\FancytooltipsAfterShow\undefined\else\edef\fancytempAA{\FancytooltipsAfterShow}\fi \if@fancytooltips@blur \def\fancytempAAA{ % \end{macrocode} % OCG's have not been initialized yet, do it now. % \begin{macrocode} var inifancytooltipsOCGs = this.getOCGs(); var fancytooltipsOCGs = []; for(var i=0; inifancytooltipsOCGs && i100) percX=100; if (percY>100) percY=100; if (percX<0) percX=0; if (percY<0) percY=0; f.buttonAlignX=percX; f.buttonAlignY=percY; } function zobraz(cislo,strana) { var f=this.getField("ikona."+(strana)); var g=this.getField("animtiph."+cislo); f.hidden=false; f.buttonSetIcon(g.buttonGetIcon()); \fancytempAA } this.dirty=false; app.focusRect = false; \end{insDLJS} \else \begin{insDLJS}[fancyTooltipsLoaded]{Tooltipsdljs}{DLJS for Tooltips} var animace; var fancyTooltipsLoaded = true; \fancytooltipsdebugmsg function CloseTooltips() { try {this.getField("ikona").hidden=true;}catch (e) {} try {app.clearInterval(animace);}catch (e) {} } function ImportTooltips() { console.println("importing pictures"); for (var i=1;i<=\TooltipPages;i++) { this.insertPages(this.numPages-1,"\TooltipFilename.pdf",(i-1),(i-1)); var rozm=this.getPageBox("Crop",this.numPages-1); this.deletePages(this.numPages-1); var p=this.addField("animtiph."+i,"button",0,rozm); p.buttonPosition=position.iconOnly; p.hidden=true; this.getField("animtiph."+i).buttonImportIcon("\TooltipFilename.pdf",(i-1)); } console.println("Imported \TooltipPages pictures, save the PDF file."); return(1); } function nastav(cislo,strana) { var f=this.getField("ikona."+(strana)); var g=this.getField("animtiph."+cislo); var sourf=f.rect; var sourg=g.rect; if ((mouseX+sourg[2]-sourg[0])100) percX=100; if (percY>100) percY=100; if (percX<0) percX=0; if (percY<0) percY=0; f.buttonAlignX=percX; f.buttonAlignY=percY; } function zobraz(cislo,strana) { var f=this.getField("ikona."+(strana)); var g=this.getField("animtiph."+cislo); f.hidden=false; f.buttonSetIcon(g.buttonGetIcon()); } this.dirty=false; app.focusRect = false; \end{insDLJS} \fi % \end{macrocode} % A cycle is used to create hidden buttons. Each button has associated a page % from the file with tooltips as icon. These icons are invoked by JavaScripts % defined in |\tooltip| and |\tooltipanim| macros. % \begin{macrocode} \newcount\tooltip@count \ifTooltip@usepdftex \newcommand*{\TooltipHidden}{% \count@=0 \@whilenum\count@<\TooltipPages \do{% \tooltip@count=\count@ \advance \tooltip@count by 1% \bgroup \immediate\pdfximage page \the\tooltip@count{\TooltipFilename.pdf}% \mbox{\leavevmode \vbox to 0 pt{\vss\hbox to 0 pt{\pdfstartlink user{% /Subtype /Widget /F 6 /T (animtiph.\the\tooltip@count) /FT /Btn /Ff 65536 /H /N /BS << /W 1 /S /S >> /MK << /TP 1 /I \the\pdflastximage\space 0 R /IF << /SW /A >> >> }% \phantom{\pdfrefximage \pdflastximage}% \pdfendlink\hss}}}% \egroup \advance\count@\@ne}% } \else \let\TooltipHidden\relax \fi % \end{macrocode} % The keywords for the tooltips can be stored in the file % |\TooltipFilename.tips|. The topics in this file are created by % |\keytip| macro (see the first part of the code). % \begin{macrocode} \AtBeginDocument{\IfFileExists{\TooltipFilename.tips}% {\input{\TooltipFilename.tips} \PackageInfo{fancytooltips}{Inputting \TooltipFilename.tips.}}% {\PackageWarning{fancytooltips}{No file \TooltipFilename.tips! Your keywords for tooltips will not work!}}} \def\tooltipname#1#2{\expandafter\xdef\csname FancyToolTip@#1\endcsname{#2}} \def\FindTipNumber#1{\expandafter\ifx \csname FancyToolTip@#1\endcsname\relax #1\else\csname FancyToolTip@#1\endcsname\fi} \def\checkTipNumber#1{\expandafter\ifx \csname FancyToolTip@#1\endcsname\relax \PackageInfo{fancytooltips}{No framenumber is assigned to keyword #1. I assume that #1 is the number of the frame.}% \fi} % % \end{macrocode} % % \Finale \endinput