ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: placelist not working in latest beta
Date: Mon, 21 Mar 2016 15:28:13 +0100	[thread overview]
Message-ID: <56F004FD.6080708@wxs.nl> (raw)
In-Reply-To: <A2DF84F0-7368-44FD-ABF1-68DF2D3D96F4@uni-bonn.de>

On 3/21/2016 9:57 AM, Schmitz Thomas A. wrote:
> Hi all,
>
> example attached with output from latest beta and an older one. The \placelist command appears to have changed recently; the older beta I tested is from November, but this used to work in February as well, the change must be recent.

when playign with some new feature i commented too much

around line 722, uncomment:

\setuplistalternative
   [\c!command=\strictlistparameter\c!command,
    \c!symbol=.]



> Thanks a lot
>
> Thomas
>
> \definelist[MyTopics][criterium=all]
>
> \def\MyMark{}
>
> \def\Topic%
>    {\dosingleargument\doTopic}
>
> \def\doTopic[#1]{%
>    \gdef\MyMark{#1}%
>    \writetolist[MyTopics][location=none]{#1}{}}
>
> \define[3]\FancyEntry{%
>    \doifelse{\rawstructurelistfirst}{\MyMark}%
>      {\quad\color[red]{#1}\quad}
>      {\quad #1\quad}}
>
> \setuplist[MyTopics]
>            [pagenumber=no,
>             alternative=command,
>             command=\FancyEntry]
>
> \setupfootertexts [{\switchtobodyfont[8pt]\quad{\placelist[MyTopics]}}]
>
> \starttext
>
> \Topic[First]
> \contextversion
>
> First Topic
>
> \page
>
> \Topic[Second]
>
> Second Topic
>
> \page
>
> \Topic[Third]
>
> Third Topic
>
> \stoptext
>
>
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive  : http://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
>


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
       tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-03-21 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21  8:57 Schmitz Thomas A.
2016-03-21 14:28 ` Hans Hagen [this message]
2016-03-21 15:10   ` Schmitz Thomas A.

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=56F004FD.6080708@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).