From: Wolfgang Schuster <schuster.wolfgang@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Numbering and module visualcounter
Date: Mon, 25 Jan 2016 16:08:16 +0100 [thread overview]
Message-ID: <56A63A60.8040205@gmail.com> (raw)
In-Reply-To: <CACyK-epmCpp10y+neOsL=wmgTi-YK+UzTCx1mnKyN7Jbfv_vfQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2292 bytes --]
> Fabrice Couvreur <mailto:fabrice1.couvreur@gmail.com>
> 25. Januar 2016 um 14:20
>
> Hello,
> In the code below, I use the module visualcounter
> The numbering is obtained
>
> 1.1
> 1.2
> 1.3
> How to have
>
> 1
> 2
> 3?
> thank you,
> Fabrice
>
> \usemodule[visualcounter]
> \unprotect
You can drop the \unprotect and \protect command when you use
\visualcounterparameter{XXX}
instead of
\visualcounterparameter\c!XXX
> \definevisualcounter
> [randomcircle]
> [
> mp=visualcounter::randomcircle,
> rulethickness=1pt,
> ]
>
> \startuseMPgraphic{visualcounter::randomcircle}
> begingroup;
>
> \includeMPgraphic{visualcounter::initialization}
>
> if (last_counter > 0) and (current_counter > 0) :
> newpicture countertext ; countertext :=
> textext("\white\visualcounterparameter\c!text");
You need the value of the “n” key, not the “text” key.
newpicture countertext ; countertext :=
textext("\white\visualcounterparameter{n}");
> newpicture max_countertext ; max_countertext :=
> textext("\white\visualcounterparameter{\c!max\c!text}");
>
> newnumeric diameter;
> diameter := 1.9 * max(bbwidth(max_countertext),
> bbheight(max_countertext));
>
> newpath randomcircle;
> randomcircle := fullcircle xyscaled(diameter, diameter) randomized
> (diameter/20);
>
> pickup pencircle scaled \visualcounterparameter\c!rulethickness ;
> fill randomcircle withcolor green; % Can be made configurable
> label (countertext, origin);
>
>
> fi;
> endgroup;
> \stopuseMPgraphic
> \protect
>
> \definevisualcounter
> [fuzzyitem]
> [randomcircle]
> [counter=\getvalue{v_strc_itemgroups_counter}]
You can set the counter for the enumeration with
[counter=itemgroup:itemize]
> \definesymbol[fuzzy][{\framed[location=depth, frame=off,
> strut=no]{\usevisualcounter{fuzzyitem}}}]
>
Keep setups like this only in your examples when they are necessary
which isn’t the case here.
> \setuphead [part]
> [command=\ChapterCommand,
> page=yes,
> textstyle=\ss,
> sectionresetset=,
> number=no,
> placehead=yes,
> bodypartlabel=chapter]
Wolfgang
[-- Attachment #1.2: Type: text/html, Size: 6181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-25 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 13:20 Fabrice Couvreur
2016-01-25 15:08 ` Wolfgang Schuster [this message]
2016-01-25 17:06 ` Fabrice Couvreur
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=56A63A60.8040205@gmail.com \
--to=schuster.wolfgang@gmail.com \
--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).