From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: Re: \startuseMPgraphic
Date: Mon, 11 Apr 2016 19:50:49 +0000 [thread overview]
Message-ID: <81D8AB9F-83C8-452E-A392-02B7416873EC@uva.nl> (raw)
In-Reply-To: <alpine.LNX.2.20.1604111316000.7203@ybpnyubfg.ybpnyqbznva>
But why should typing \MPcolor{\MPvar{color}}be necessary or useful when \MPvar(color) obviously is sufficient?
Or is there a special reason for the nested macros?
> On 11 Apr 2016, at 19:16, Aditya Mahajan <adityam@umich.edu> wrote:
>
> On Mon, 11 Apr 2016, Meer, Hans van der wrote:
>
>>
>> On 11 Apr 2016, at 16:17, Alan BRASLAU <alan.braslau@cea.fr<mailto:alan.braslau@cea.fr>> wrote:
>>
>> Remember that ConTeXt colors can be accessed in MP as
>> \MPcolor{orange}
>>
>> Alan
>>
>> However with the snippet below I see the default black with MPcolor and the wanted red with \MPvar. Thus?
>>
>> Hans van der Meer
>>
>> \starttext
>> \startuseMPgraphic{example1}{color}
>> pickup pencircle scaled 1mm;
>> draw unitsquare scaled 1cm
>> withcolor \MPcolor{color};
>
> This is looking for a color named 'color'. You need \MPcolor{\MPvar{color}}.
>
>
>> \stopuseMPgraphic
>> \startuseMPgraphic{example2}{color}
>> pickup pencircle scaled 1mm;
>> draw unitsquare scaled 1cm
>> withcolor \MPvar{color};
>> \stopuseMPgraphic
>> \useMPgraphic{example1}{color=red}
>> \useMPgraphic{example2}{color=red}
>> \stoptext
>
> Aditya
Hans van der Meer
___________________________________________________________________________________
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-04-11 19:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1460368801.12686.ntg-context@ntg.nl>
2016-04-11 13:10 ` \startuseMPgraphic Jeong Dal
2016-04-11 14:17 ` \startuseMPgraphic Alan BRASLAU
2016-04-11 14:38 ` \startuseMPgraphic Meer, Hans van der
2016-04-11 17:16 ` \startuseMPgraphic Aditya Mahajan
2016-04-11 19:50 ` Meer, Hans van der [this message]
2016-04-11 20:27 ` \startuseMPgraphic Wolfgang Schuster
2016-04-11 22:30 ` \startuseMPgraphic Alan BRASLAU
2016-04-11 22:52 ` Warnings while compiling pdf after update L.S.-Soc&Gam
2016-04-11 23:07 ` Hans Hagen
2016-04-11 23:00 ` \startuseMPgraphic Aditya Mahajan
2016-04-11 8:35 \startuseMPgraphic Meer, Hans van der
2016-04-11 12:42 ` \startuseMPgraphic Wolfgang Schuster
2016-04-11 13:30 ` \startuseMPgraphic Meer, Hans van der
2016-04-11 14:12 ` \startuseMPgraphic Wolfgang Schuster
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=81D8AB9F-83C8-452E-A392-02B7416873EC@uva.nl \
--to=h.vandermeer@uva.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).