ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: t-rsteps and starttyping
Date: Thu, 22 Sep 2005 22:39:45 +0200	[thread overview]
Message-ID: <43331691.4020805@wxs.nl> (raw)
In-Reply-To: <1127419355.1886.13.camel@tempete>

David Munger wrote:

>Hans,
>
>The RawSteps module produces virtual slides with stepping, by rendering
>the step incrementally on successive pages. Thus, the
>\StartSteps...\StopSteps macro has to expand its argument (i.e. the
>content of the slide) a certain number of times, depending the number of
>requested steps. Of course, it shows only the relevant parts at each
>step.
>
>To allow this, I had to work around page numbers, formula numbers, and
>lately \starttyping blocks.
>
>If you could suggest a better way to achieve this multiple expansion, it
>would be welcome.
>  
>
did you ever try 

  texexec --mode=demo s-pre-61 

using 'layers' is rather robust (no duplicate pages and such); 

Some of the older presentation styles build the pages stepwise, they use either boxes, or buffers (i must look into it, but there is also one that plugs into the otr; in your case, collecting in a box and uncopying it is probably the best method. 

there is no general robust solution for this that does not messes up something so it depends on the kin df presentation 

Hans 



-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2005-09-22 20:39 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 16:41 Peter Münster
2005-06-25 11:08 ` Otared KAVIAN
2005-06-25 11:42   ` Peter Münster
2005-06-27 10:56   ` Hans Hagen
2005-06-28 18:16     ` Peter Münster
2005-06-27 22:06 ` David Munger
2005-09-12 17:04   ` Peter Münster
2005-09-12 21:57     ` David Munger
2005-09-21 12:38       ` Christopher Creutzig
2005-09-21 14:00         ` David Munger
2005-09-21 14:13           ` Taco Hoekwater
2005-09-21 22:16             ` David Munger
2005-09-22  6:56               ` Christopher Creutzig
2005-09-22 15:24                 ` David Munger
2005-09-22 16:56                   ` Hans Hagen
2005-09-22 20:02                     ` David Munger
2005-09-22 20:39                       ` Hans Hagen [this message]
2005-09-23  2:34                         ` David Munger
2005-09-23  7:11                           ` Mojca Miklavec
2005-09-23  8:51                         ` Peter Münster
2005-09-23 10:46                           ` Hans Hagen
2005-09-23 13:21                             ` Christopher Creutzig
2005-09-25 21:42                               ` Hans Hagen
2005-09-28 11:13                                 ` Christopher Creutzig
2005-09-26 15:04           ` footnote for author (\thanks) Albrecht Kauffmann
2005-09-26 16:08             ` Adam Lindsay
2005-09-26 15:34           ` footnote numbering Albrecht Kauffmann

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=43331691.4020805@wxs.nl \
    --to=pragma@wxs.nl \
    --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).