Re: Problem bei Anwendung von step/stepwise
[first of all, please keep discussion on this list in english]
On Fri, 4 Aug 2000 10:24:01 +0200, "Goebel, Juergen" wrote:
[what's wrong with the following construct?]
\stepwise{%
\begin{enumerate}
\step{\color{colori}\item Einleitung}
\step{\color{colorii}\item Antennen und Wellenausbreitung}
[...]
\step{\color{colorxi}\item Anwendungen}
\end{enumerate}
} % - Zeile 44
[it yields the following error message]
! LaTeX Error: Something's wrong--perhaps a missing \item.
See the LaTeX manual or LaTeX Companion for explanation.
Type H return for immediate help.
...
l.44 }
Well, \stepwise is very thorough in hiding its argument,
so for the very first step, the argument of \stepwise looks
like this:
\begin{enumerate}
\end{enumerate}
which is illegal in LaTeX, so the error message is as precise
as could be ;-)
I advise to include the whole list into the first step,
like this:
\stepwise{%
\step{%
\begin{enumerate}
\color{colori}\item Einleitung
\step{\color{colorii}\item Antennen und Wellenausbreitung}
[...]
\step{\color{colorxi}\item Anwendungen}
\end{enumerate}
}%
} % - Zeile 44
regards
Stephan
--
Stephan Lehmke [EMAIL PROTECTED]
Fachbereich Informatik, LS I Tel. +49 231 755 6434
Universitaet Dortmund FAX 6555
D-44221 Dortmund, Germany
Re: texpower pdfscreen dimmed colors
On Thu, 03 Aug 2000 16:15:15 +0200, Hana Skoumalova wrote:
in fact I would like to get sth like this:
\begin{itemize}
\liststepwise[\let\hidestepcontents=\hidedimmed
\let\displaystepcontents=\hidedimmed
\let\activatestep=\highlightenhanced]
{
\step{\item we ``discover'' the structure of the document (DTD)}
\step{\item SGML tools (nsgmls, yasp) help us to correct the source}
\step{\item we can produce the ``printing'' markup again}
\step{\item we can use SGML format for other applications}
}
\end{itemize}
Only the highlighted item is well seen, others are dimmed. Is there a
better way to do this?
Looks ok to me. If you wish to avoid dimming colors with
\displaystepcontents only to enhance them again with
\activatestep, you can use the optional arguments of
\step for controlling activation:
\liststepwise[\let\hidestepcontents=\hidedimmed
\let\activatestep=\highlightenhanced]
{
\step[][\boolean{firstactivation}]{\item we ``discover'' the structure of the
document (DTD)}
\step[][\boolean{firstactivation}]{\item SGML tools (nsgmls, yasp) help us to
correct the source}
\step[][\boolean{firstactivation}]{\item we can produce the ``printing''
markup again}
\step[][\boolean{firstactivation}]{\item we can use SGML format for other
applications}
}
Of course, you can hide the optional argument in a
selfdefined macro (item can go in there, too, like
\newcommand{\myitem}[1]{\step[][\boolean{firstactivation}]{\item#1}}
).
And what if I wanted to use a different color
(say green instead of dimmed)?
If you want _all_ colors to go to green, use
\hidevanish instead of \hidedimmed and set
\renewcommand{\vanishcolor}{green}.
If you want different defined colors to go
to different shades of green, redefine the
dimmed variants (dtextcolor, dmathcolor, ...)
accordingly (using \definecolor or \replacecolor).
regards
Stephan
--
Stephan Lehmke [EMAIL PROTECTED]
Fachbereich Informatik, LS I Tel. +49 231 755 6434
Universitaet Dortmund FAX 6555
D-44221 Dortmund, Germany
Re: texpower+ifmslide+latex
On Wed, 06 Sep 2000 17:58:29 +0200, Ignasi Furió Caldentey wrote:
may be I've missunderstood something but I'm trying to obtain
a ps version of the ifmslidemo without success.
I just want the printed version so I supress the display
option from the header:
\documentclass[KOMA,landscape]{powersem}
Then latex ifmslidemo.tex + dvips ifmslidemo.
The dvi file is OK, I can see it in Yap with the extra margins and
landscape orientation, but the dvips results in a portrait document.
That's strange. I just did the following:
* copy http://lrb.cs.uni-dortmund.de/~lehmke/TeXPower/doc/ifmslidemo.tex
* delete ",display" from \documentclass[KOMA,landscape,display]{powersem}
* run latex on the result
* run dvips (without options, or with option -Ppdf)
and I get a ps file in landscape orientation...
What am I doing wrong?
Maybe you could post the log entries showing the version numbers
and dates of hyperref, powersem, ifmslide (and the one showing the
driver used by hyperref)...
regards
Stephan
--
Stephan Lehmke [EMAIL PROTECTED]
Fachbereich Informatik, LS I Tel. +49 231 755 6434
Universitaet Dortmund FAX 6555
D-44221 Dortmund, Germany
Re: Page duration problem
[First of all, to all readers of this list who are wondering
whether maybe TeXPower development has died in July: v0.9
is underway, but at this moment, I'm putting the final touch
to my PhD thesis and giving a lecture, so I have very little
spare time for development. I'm afraid the next release will
have to wait for Feb 2001, when the winter term ends.
If anyone feels daring enough and competent to read the raw code,
I'm willing to privately send the current development version,
which seems to be stable enough (at least I'm using it for
my lecture slides), but no documentation and no support
at all.
For the same reasons, my answering time on this list is
slow at the moment; I'm trying to reduce my email backlog,
but without much success :-| ]
On Wed, 08 Nov 2000 13:08:20 +0100, Pascal Kockaert wrote:
I'm trying to use \pageDuration in order to animate some part of a PDF file.
What I do is to put \pageDuration{0} on pages which have to change quicly
Better use something like \pageDuration{0.01}; it seems a value of 0
will cause flickering on some configurations while a positive
value will cause acroread to always wait until a page is built
completely before switching screens.
then put a \pageDuration{} to stop the evolution.
Unfortunaltely, the page doesn't change when viewing the file in acrobat
reader 4.05b.
Yes, after asking on the pdftex list and in comp.text.pdf,
I have it from the experts that this is indeed a bug in all
4.05 versions of acroread (I personally tested about 10 variants
on 4 systems). When I need animations, I use acrobat (the
commercial product) or acroread 4 (without .05). Unfortunately,
acroread 4 seems to have problems extracting fonts on Linux
(never had problems with acroread 4 on Sun Solaris systems).
So, my questions are :
- is this a feature/bug of Reader which can't be avoided ?
see above
- is there a more powerfull command than \pageDuration that could force a
break in the file ?
dunno
More generally, is there a way to animate some part of a picture without
using /Dur ? I mean something like animated gifs or png equivalent or
embedded java code ?
Might be. I think I heard of an "animated png" variant, but I don't
remember whether it really exists or is only planned, and whether
acroread and pdftex support it. Maybe you'll get a competent
answer from the pdftex list or the newsgroup comp.text.pdf.
The adobe website also has a forum, but the one time I looked
into it, it seemed to have a very low level and not to be read
by developers.
regards
Stephan
--
Stephan Lehmke [EMAIL PROTECTED]
Fachbereich Informatik, LS I Tel. +49 231 755 6434
Universitaet Dortmund FAX 6555
D-44221 Dortmund, Germany
Re: Strange color behaviour with seminar
On Wed, 07 Feb 2001 16:37:04 +0100, Beaubert Francois wrote:
My latex preamble looks like this:
\documentclass[a4]{seminar}
\usepackage{color}
\usepackage{pifont}
\input{seminar.bug}
\input{seminar.bg2}
\usepackage[colorlinks,urlcolor=red]{hyperref}
\usepackage{fixseminar}
\PassOptionsToPackage{lightbackground,sans,fixcolorstack}{texpower}
\usepackage{texpower}
...
with the fancyheadings package the header (text and rule) is in black
(!?)
Unfortunately, your code is far from providing a working
example of the effect you mention.
If I extend it like this:
\documentclass[a4]{seminar}
\usepackage{color}
\usepackage{pifont}
\input{seminar.bug}
\input{seminar.bg2}
\usepackage[colorlinks,urlcolor=red]{hyperref}
\usepackage{fixseminar}
\PassOptionsToPackage{lightbackground,sans,fixcolorstack}{texpower}
\usepackage{texpower}
\usepackage{fancyhdr}
\pagestyle{fancy}
\renewcommand{\headrulewidth}{2pt}
\renewcommand{\footrulewidth}{2pt}
\begin{document}
\begin{slide}
test
\newslide
test
\end{slide}
\end{document}
and compile with latex+dvips+distiller, then everything is
blue as expected. When I compile with pdflatex, then everything
on the first page is blue as expected, and on the second page
everything (including body) is black.
This is a problem ultimately caused by the fact that seminar's
output routine stems from the stoneage of LaTeX, when the
color package didn't exist.
Using the current development version of powersem (attached)
instead of seminar will cure this somewhat, because it defines
a patched output routine. But you have to leave out
\input{seminar.bug}
\input{seminar.bg2}
because they will overwrite powersem's changed output routine.
powersem loads these anyway before applying the patch.
and the footrule is brown (it should be blue)
As I said, for my example it's black. Could you post
a complete (minimal) test example?
sometimes the rule in array are brown to
Are you sure this isn't a `trick of the light' or some
anti-aliasing effect? Did you look with maximal
magnification?
If yes, please post a complete (minimal) test example.
I got this with or without the option lightbackground, fixcolorstack
These shouldn't have any influence here, unless
you're using dvips.
regards
Stephan
--
Stephan Lehmke [EMAIL PROTECTED]
Fachbereich Informatik, LS I Tel. +49 231 755 6434
Universitaet Dortmund FAX 6555
D-44221 Dortmund, Germany
%-
% File: powersem.cls
%
% Make seminar ready for the Third Millennium ;-)
% This class loads seminar and tries to fix some problems which occur when trying to
create dynamic presentations with
% the texpower package.
%
% Some new features helpful for dynamic presentations are also added.
%
% This class is part of the TeXPower bundle, to be found at
%
% http://ls1-www.cs.uni-dortmund.de/~lehmke/texpower/
%
% The TeXPower bundle also contains a package fixseminar.sty which applies some more
fixes, in particular for
% hyperref. These can not be applied here because they have to be made after hyperref
is loaded.
%
%-
% Autor: Stephan Lehmke [EMAIL PROTECTED]
%
% v0.1 Oct 18, 1999 First version. So far it doesn't do much more than load seminar.
%
% v0.2 Mar 28, 2000 Force seminar to treat \paperwidth and \paperheight in a sensible
manner.
%
% v0.3 May 10, 2000 Added option `calcdimensions'.
%
% v0.4 Jun 16, 2000 Now separates text from footnotes when option `display' is given.
%
% v0.5 Jun 26, 2000 \@colht is ignored by seminar, which is bad. Added a patch to
\set@slidesize.
% calcdimensions now handles slide frames.
%
% v0.5a Jul 03, 2000 The footnote patch with option display effectively disabled
setting \centerslidestrue. Fixed.
%
% v0.6 Sep 05, 2000 seminar's \output@slide kernel copied and modified for better
color handling and to remove some
%overfull \vbox warnings.
%
\def\fileversion{0.6}
\def\filedate{2000/09/05}
\NeedsTeXFormat{LaTeX2e}
\ProvidesClass%
{powersem}%
[\filedate\space Create online Presentations with seminar. v\fileversion]
%--
\RequirePackage{ifthen}
%--
% The display option is understood by all relevant classes and packages from the
TeXPower bundle. It means that
% `dynamic' features are to be turned on.
% There is a boolean register display (as defined in ifthen.sty) which is set by this
option and can be used to
% differentiate between slides for display and slides for printout.
% Notes are disabled automatically.
\newboolean{display}
\DeclareOption{display
Re: powersem display option - bug?
:
\documentclass[display]{powersem}
with
\documentclass{powersem}
\display
I'm not sure this is a good idea. At least, it's not
trivial. A lot of code is defined differently at loading
of powersem and texpower, depending on whether or not
the display option is given.
Putting this into a command may break things big time.
I want to wrap the \display inside \ifpdf.
You can say
\ifpdf\PassOptionsToClass{display}{powersem}\fi
regards
Stephan
--
Stephan Lehmke [EMAIL PROTECTED]
Fachbereich Informatik, LS I Tel. +49 231 755 6434
Universitaet Dortmund FAX 6555
D-44221 Dortmund, Germany
Re: Flickering screen
On Fri, 14 Sep 2001 18:28:37 +0300 (EET DST), Tarik Kara wrote:
\pageDuration{0.01} solved my problem but when I use \pageDuration{0.01}
then autoadvance does not work with Acrobat Reader 5
There's an amazing trick to this: turn on `automatically advance
every ... pages' in the full screen settings dialog.
Of course, then all pages without page duration key will get advanced
after the time set in the dialogue.
Mindbogglingly, the people at adobe managed to think of another
booby trap for people trying to earnestly use this feature:
while older versions of acroread have no problems to let you
set the advancing time to 3600 seconds (approaching infinity
for lectures), the maximum is 60 (!) seconds for acrobat 5 :-(
One remedy is to set a large page duration (say 546) at the
beginning of your document. Then every page has a duration key
and the setting in the dialogue is effectively ignored.
Unfortunately, 9 Minutes 6 Seconds is all the time you'll
get for one slide; for a setting of 547 and above (arbitrary,
isn't it?), at least here there seems to be some kind of overflow
and acrobat 5 goes into `fast forward' mode :-(
regards
Stephan
--
Stephan Lehmke [EMAIL PROTECTED]
Fachbereich Informatik, LS I Tel. +49 231 755 6434
Universitaet Dortmund FAX 6555
D-44221 Dortmund, Germany
Re: Text wobbling when foiltex is used
Hi all,
sorry for being sluggish on the list again.
Alas! The Real Life!
Still, TeXPower is by no means a `dead project', in spite
of some statements in this direction ;-)
I hope I'll have time to do some catching up these days
(though my second child is due end of april :-))
On 06 Mar 2002 07:40:37 +0100, Henrik Holm wrote:
[Henrik Holm]
I discovered that, for certain combinations of words, the
text jumps a bi up and down.
Alan Williams advised me to use \parstepwise instead of
\stepwise. This seems to cure the problem!
The problem is as follows:
Using the `vanilla' stepwise makes the non-active steps
disappear completely.
Try \step{one} and \step{two} and \step{three} to see what
I mean.
In particular, no blank space is left for the non-visible
things. This is more robust in a lot of respects, so it is
the standard behaviour. It is good for displaying list items,
equations, picture elements etc.
Inside a paragraph, however, it can lead to problems. You have
experienced one: the vertical position of a line in a paragraph
depends on the height and depth of the text in the paragraph.
When things are displayed by (the standard version of) \step,
this height and depth can change when high or deep text appears.
\parstepwise is made especially for this purpose: the `invisible'
things don't disappear completely, but blank space of the right
dimensions is left for them. This remedies this kind of problem.
I've also read
some more in the «fulldemo», and according to that document,
text wobbling seems to be a known problem.
That's another problem: LaTeX is sometimes `too smart' when
calculating vertical placement of lists and the like, with
the result that the calculation yields different results
for different iterations of \stepwise, making lines wobble
vertically (but for a different reason than your problem).
As \parstepwise is not suited for displaying lists, there exists
another variant \liststepwise which will hopefully remedy
this kind of problem.
Alas, sometimes only trial-and-error helps. As I have a lot
of experience with this kind of thing by now, the list is
indeed the right place to ask. And I promise to try answering
more promptly in the next time :-)
regards
Stephan
--
Stephan Lehmke [EMAIL PROTECTED]
Fachbereich Informatik, LS I Tel. +49 231 755 6434
Universitaet Dortmund FAX 6555
D-44221 Dortmund, Germany
