At 01:51 PM 1/24/2003 +0100, you wrote:

The reason was somewhat different. Context was not the only parameter that changed since last year.. I came around it when experimenting with field stacks:

The presentationstep mechanism doesn't work with Acrobat Reader for Linux (neither do field stacks). Can this be fixed? Or maybe there is generally a lack in JavaScript capabilities in AR for Linux? Does anybody know more about it?

what version of acrobat do you run? I try to keep up with the changes in initialization order in acrobat (field init versus javascript init versus first page init: the incredible mess). Can you send me the smallest failing example (so that i can see it fail in my vmware linux box). 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 ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------

Eckhart Guthöhrlein writes: Hello Eckhart,

The presentationstep mechanism doesn't work with Acrobat Reader for Linux (neither do field stacks).

This is not true. I have a pdf file here that uses fieldstack and displays correctly with acroread 4 and 5 on my linux box. But acroread 5 has a weired bug: running acroread filename.pdf does not enable the javascript stuff but running acroread and then opening the file from the menu turns on the field stack

Can this be fixed? Or maybe there is generally a lack in JavaScript capabilities in AR for Linux? Does anybody know more about it?

If you want, I can send you the file (.tex and/or .pdf). Use: \setupinteraction[state=start,openaction=] in the .tex file. Patrick

At 02:19 PM 1/24/2003 +0100, you wrote:

running acroread filename.pdf does not enable the javascript stuff but running acroread and then opening the file from the menu turns on the field stack

whow, that's real wierd, i wonder how such an error can show up, must be intentionally programmed, unless of course no code is shared, which would explain the big binaries -) 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 ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------

Eckhart Guthöhrlein writes: Hello,

And I'm glad that and wonder how Patrick spotted it.

Pure coincidence :)

It already took me quite some time... and self-control not to smash my keyboard.

:) Patrick

I don't know much about interactivity, but I've noticed that problem with acroread before: specifying docs on the command line can give different behavior than opening them from the menu. On Linux, at least.

I remember to have heard such by "PDF guru" Stephan Jaeggi about some Windows version. Grüßlis vom Hraban! -- www.fiee.net/texnique/ www.ramm.ch/context/

On Friday 24 January 2003 15:08, Otared Kavian wrote:

But the \presentationstep command doesn't work properly with other styles.

If the presentation style doesn't say \usemodule[pre-general], you have add this. After that, \presentationstep will be defined. Then you have to make sure that a Whatever button is defined and printed. That should (in principle) be everything you need. I have produced my present style starting from s-pre-01, copied some whatever code from s-pre-02.

On the other hand the "green style" has a strange behavior: there is a black rectangle in the middle of the pages... The resulted presentationstep.pdf file can be found on

I can't reproduce that. The green style is the one in Hans' example. Doesn't that work for you? No rectangle here.

http://homepage.mac.com/otared/FileSharing3.html/presentationstep.pdf

The link doesn't work, but I got the file from the parent dir. Looks horrible, indeed )-:

After trying to change the file s-pre-02.tex I succeeded to remove the black rectangle but its frame remains there.

Well, there shouldn't be a rectangle using the original? So if you use the same context version (current beta), remove all modified and temporary files and start from the clean example that Hans posted, this should work as it does here. Eckhart