From: Peter Rolf <indiego@gmx.net>
Subject: Re: Fieldstack Walk
Date: Sat, 22 Apr 2006 22:01:09 +0200 [thread overview]
Message-ID: <444A8B85.4070209@gmx.net> (raw)
In-Reply-To: <4444C1CE.9070205@econ.muni.cz>
[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]
Michal Kvasnička wrote:
> Good afternoon.
>
> Many thanks, this solves the problem -- at least partially. The frames
> are `walking' now, but new problems appeared. I found that when I set
> `clickin=...', it is set it automatically to `clickout' as well, so one
> mouse click runs the JavaScript code twice. So I've set it this way:
>
> \definefieldstack[fgolds2]
> [sgolds1,sgolds2a,sgolds2b,sgolds2c,sgolds2d,sgolds2]
> [frame=off,option=,clickout=JS(Walk_Field{fgolds3}),clickin=]
>
> It's better, but I found that now frames are walking in a strange order.
> It is rather puzzling, since when it is invoked by \goto{...}[JS(...)],
> it works well. Moreover, it does different things at AdobeReader 7.x
> under Linux, and Acrobat 4.x under Windoze.
>
> Can you help me to solve it?
Took some time, but it works now. What I don't understand, is the
strange behaviour of the offset parameter in this case. See attached file.
Greets, Peter
> Many thanks once more.
> M.K.
>
>
[-- Attachment #2: test.tex --]
[-- Type: text/plain, Size: 1310 bytes --]
% interface=en output=pdftex
% Time-stamp: <Samstag, 22 April 2006 21:53:30; test.tex>
%
\setupinteraction[state=start]
\setupcolors[state=start]
\starttext
\tracefieldstrue
\switchtobodyfont[96pt]
\def\FS#1{\framed[width=4cm,height=4cm,strut=no]{\red\bf#1}}%
\definesymbol [empty] []
\definesymbol [one] [\FS{1}]
\definesymbol [two] [\FS{2}]
\definesymbol [three] [\FS{3}]
\definesymbol [four] [\FS{4}]
\definesymbol [five] [\FS{5}]
\setupfield[interaction]
[width=4cm,height=4cm,
% frame=off,
framecolor=blue,
offset=none,% default offset causes different positioning of walk button and fieldstack
clickin=JS(Walk_Field{sequence})]
\definefield[Walk][check][interaction][empty][empty]
\definefieldstack[sequence]
[one,two,three,four,five]
[frame=off,
offset=none,% default offset causes different positioning of walk button and fieldstack
clickin=JS(Walk_Field{sequence})]
\defineproperty[interaction][layer][title=walkfield, state=start]
\vbox{\forgetall
\nointerlineskip\smashedvbox{\fieldstack[sequence]}%
%
\startproperty[interaction]%
\nointerlineskip\field[Walk]
\stopproperty%
}
\blank[2cm]
\showfields
\stoptext
%%% Local Variables:
%%% mode: context
%%% TeX-master: ""
%%% End:
[-- Attachment #3: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next prev parent reply other threads:[~2006-04-22 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 9:09 Michal Kvasnička
2006-04-18 9:28 ` Peter Rolf
[not found] ` <4444B1C9.1090109@econ.muni.cz>
2006-04-18 10:18 ` Peter Rolf
[not found] ` <4444B966.5020108@gmx.net>
2006-04-18 10:39 ` Michal Kvasnička
2006-04-18 11:55 ` Peter Rolf
2006-04-18 21:35 ` Peter Rolf
2006-04-18 22:03 ` Sanjoy Mahajan
2006-04-19 8:41 ` Peter Rolf
2006-04-19 11:49 ` Sanjoy Mahajan
2006-04-22 20:01 ` Peter Rolf [this message]
2006-04-22 20:09 ` Peter Rolf
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=444A8B85.4070209@gmx.net \
--to=indiego@gmx.net \
--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).