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
Thanks Sanjoy for pointing this out. Both problems are still *unfixed*
(beta from 17.04). Unfortunately fixing them doesn't solve my problem.
I'll try it again later. Maybe I was to tired yesterday to solve this
and the error is on my side...
Greets, Peter
Sanjoy Mahajan wrote:
there are still
From:Peter Rolf [EMAIL PROTECTED]
Both problems are still *unfixed* (beta from 17.04).
The one I pointed out doesn't have an obvious solution since (I think)
the reserveobjnum spacing change breaks with pdftex 1.30 but is needed
with pdftex 1.21. I guess the magic line could be wrapped in a
Good morning.
I use a fieldstack in my presentation. I'd like to go to the next frame
when I click on the figure. I tried this:
\definefieldstack[fgolds3]
[sgolds1,sgolds3a,sgolds3b,sgolds3c,sgolds3]
[frame=off,clickin=JS(Walk_Field{fgolds3})]
Michal Kvasnička wrote:
Good morning.
I use a fieldstack in my presentation. I'd like to go to the next frame
when I click on the figure. I tried this:
\definefieldstack[fgolds3]
[sgolds1,sgolds3a,sgolds3b,sgolds3c,sgolds3]
[frame=off,clickin=JS(Walk_Field{fgolds3})]
Hi Michal,
Michal Kvasnička wrote:
Hi Peter,
thank for your answer, but it doesn't help. First, it seems the order is
not important in ConTeXt. Second, the fieldstack works well. I can even
make it walk with \goto{...}[JS(Walk_Field{fgolds3})]. The only thing
that doesn't work is that I
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
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
Peter Rolf wrote:
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
