LaTeX.org

I had no problem with powerdot in my last installation (2005). With a new computer, I installed TexLive 2010, and ran the same powerdot programs that compiled on the old installation. For each slide I had 3 errors, and this was due to the clock option. Once I removed it, I had no problems; however ...

dvi does not support specials that are associated with pstricks.

Is your build profile include `pdflatex'. If so then there is your error; you need to compile the tex file to a dvi file, then convert it to a ps using dvips, and then convert that to a pdf file in GSview, or using ps2pdf14.bat which ...

The realcalc.tex package should go into

. . . texmf-dist\tex\generic\realcalc

or

. . . texmf\tex\generic\realcalc

where the dots stand for whatever path leads to one of these folders (the first is preferable).

Then you must refresh the ls-R database (in TeXnicCenter) or similar in MikTeX ...

I found this book had a very good introduction to writing class files, with some good examples.

The Guide to \LaTeX\ (Fourth Edition) {\em Kopka \& Daly\/} Addison-Wesley ISBN 0-321-17385-6

John

Actually I had tried to put the option in both square and curly brackets. Each of them gave me problems.

I tried your code, and it created an awful lot of errors. Removing the optional argument from {itemstep} removed all the errors. I have version \def\Prosper@Version{2001/07/17, v. 1.5}, from the ...

Thanks for your reply, and I am looking at powerdot class.

By the way, here is a mwe

\documentclass[pdf,azure,slideColor,colorBG]{prosper}
\begin{document}
\overlays{4}{%
\begin{slide}{Slide heading}
First paragraph\par
\fromSlide{2}{Second paragraph leading to itemized list presented in steps ...

In Prosper, I am trying to build up a composite slide in parts with the first one or two slides being a preamble, and then using an {itemstep} environment. In the documentation it says
`It accepts an optional argument corresponding to the overlay level to start from.'

so I type \begin{itemstep}{3 ...

I am glad that the workaround for Reader 8.0 works.

I think that I picked it up from the TeXnicCenter user's group.

John

I have been told of a workaround for Adobe 8.0.

Simply, put a second [DocOpen("%bm.pdf")] in front of the first in the two instances in build profile, and this seems to keep it quiet.

John