From: Alexandre Christe via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Alexandre Christe <aleks.christe@gmail.com>
Subject: Re: Issue with setupMPvariables
Date: Sat, 3 Sep 2022 20:31:15 +0200 [thread overview]
Message-ID: <CALC5-UKtYxF-m24orOFrr_CcVUy98iNJ8Hg=Uq18R=-=3ujTvg@mail.gmail.com> (raw)
In-Reply-To: <0deb07bf-93e8-1d1f-9049-a3185cb45472@freedom.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1847 bytes --]
Thanks Hans!
For sake of completeness a MWE is attached, in case someone needs it one
day.
Le sam. 3 sept. 2022 à 20:10, Hans Hagen via ntg-context <ntg-context@ntg.nl>
a écrit :
> On 9/3/2022 6:48 PM, Alexandre Christe via ntg-context wrote:
> > Dear all,
> >
> > I'm trying to reuse some MP code for several custom enumeration.
> >
> > However I can't make the overall setup work, needless to say different
> > border colors for each enumeration though setupMPvariables. What am I
> > missing?\startuseMPgraphic{mp:textFrame}
> begingroup;
> path p ;
> for i = 1 upto nofmultipars :
> p := (ulcorner multipars[i]) -- (llcorner multipars[i]) --
> (llcorner
> multipars[i] xshifted .25cm) -- (ulcorner multipars[i] xshifted .25cm)
> -- cycle ;
> fill p withcolor boxfillcolor ;
> draw p withcolor boxlinecolor ;
> endfor;
> endgroup;
> \stopuseMPgraphic
>
>
> -----------------------------------------------------------------
> Hans Hagen | PRAGMA ADE
> Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
> tel: 038 477 53 69 | www.pragma-ade.nl | 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 /
> https://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : https://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : https://contextgarden.net
>
> ___________________________________________________________________________________
>
[-- Attachment #1.2: Type: text/html, Size: 2960 bytes --]
[-- Attachment #2: testColorParagraphs.tex --]
[-- Type: application/x-tex, Size: 1161 bytes --]
[-- Attachment #3: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2022-09-03 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 16:48 Alexandre Christe via ntg-context
2022-09-03 18:09 ` Hans Hagen via ntg-context
2022-09-03 18:31 ` Alexandre Christe via ntg-context [this message]
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='CALC5-UKtYxF-m24orOFrr_CcVUy98iNJ8Hg=Uq18R=-=3ujTvg@mail.gmail.com' \
--to=ntg-context@ntg.nl \
--cc=aleks.christe@gmail.com \
/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).