ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Meer, Hans van der" <H.vanderMeer@uva.nl>
To: NTG ConTeXt <ntg-context@ntg.nl>
Subject: \startuseMPgraphic
Date: Mon, 11 Apr 2016 08:35:33 +0000	[thread overview]
Message-ID: <87835776-211F-4B8A-9730-A49978E25D66@uva.nl> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1240 bytes --]

I seem to remember the following variations in \startuseMPgraphic.

(1) \startuseMPgraphic{name}{comma separated list of variables}
(2) \startuseMPgraphic{name}{comma separated list of key=value pairs}
In the second case one is able to set a default value to that variable, possibly to be overridden with \useMPgraphic{name}{key=value}.
I very much would like to specify default values on the \startuseMPgraphic definition of the graphic.

However, I cannot get option (2) working. Do I have a bad memory (possible of course ;-), Has it to be done otherwise?
In the example below the graphic myname1 is ok, but myname2 gives the following error:
metapost        > error:
>> orange
! Improper type.
<to be read again>
                   ;
<*> ...raw unitsquare scaled 1cm withcolor orange;

minimal example:

\starttext
\startuseMPgraphic{myname1}{color}
  pickup pencircle scaled 1mm;
  draw unitsquare scaled 1cm withcolor \MPvar{color};
\stopuseMPgraphic

\startuseMPgraphic{myname2}{color=red}
  pickup pencircle scaled 1mm;
  draw unitsquare scaled 1cm withcolor \MPvar{color};
\stopuseMPgraphic

\useMPgraphic{myname1}{color=blue}
\useMPgraphic{myname2}{color=orange}

\stoptext

Hans van der Meer


[-- Attachment #1.2: Type: text/html, Size: 3547 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
___________________________________________________________________________________

             reply	other threads:[~2016-04-11  8:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11  8:35 Meer, Hans van der [this message]
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
     [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         ` \startuseMPgraphic Meer, Hans van der
2016-04-11 20:27           ` \startuseMPgraphic Wolfgang Schuster
2016-04-11 22:30             ` \startuseMPgraphic Alan BRASLAU
2016-04-11 23:00               ` \startuseMPgraphic Aditya Mahajan

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=87835776-211F-4B8A-9730-A49978E25D66@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).