From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: troubles with \MPinclusions
Date: Thu, 21 Feb 2019 10:51:39 +0100 [thread overview]
Message-ID: <E61D32EE-426E-4140-8CBB-315AEFDF8242@elvenkind.com> (raw)
In-Reply-To: <20190221090307.GA53231@valencay.home>
> On 21 Feb 2019, at 10:03, Damien Thiriet <damien@thiriet.web4me.fr> wrote:
>
> Hi,
>
>
> Why does (1) compile, whereas (2) doesn’t?
For me, both compile. However (2) does not work.
1. Variable names x and y are special and cleared before
every graphic. This is related to the fact that “z" is
defined as a shortcut for "(x,y)”. Both of these are
traditional.
Every metapost graphic does at least this at its start:
save x,y;
currentpicture := nullpicture;
currentpen:=defaultpen;
so pair xx[]; would have worked just fine.
In general, I would advice to stay away from single-letter
variable names inside MPinclusions, and use CamelCase
to avoid clashes with metafun internals.
2. You need a bigger pen to actually see the dots even if
you change the variable name. :)
Best wishes,
Taco
> I can't understand why can MPinclusions store path and not pairs.
>
>
> %%%%%%%%%%%% (1) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> \setuppapersize[A4,landscape]
>
> \startMPinclusions
> u:=1mm ;
> %fond
> path p ;
> p:= (0,0) -- (150u,0) -- (150u,95u) -- (0,95u) -- cycle ;
> pair x[] ;
> x[0]:= (20u,90u) ;
> x[1]:= (40u,90u) ;
> x[2]:= (90u,90u) ;
> x[3]:= (140u,90u) ;
> \stopMPinclusions
>
> \startreusableMPgraphic{test}
> draw p ;
> \stopreusableMPgraphic
>
> \starttext
> \reuseMPgraphic{test}
> \stoptext
>
> %%%%%%%%%%%% (1) %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
> \setuppapersize[A4,landscape]
>
> \startMPinclusions
> u:=1mm ;
> %fond
> path p ;
> p:= (0,0) -- (150u,0) -- (150u,95u) -- (0,95u) -- cycle ;
> pair x[] ;
> x[0]:= (20u,90u) ;
> x[1]:= (40u,90u) ;
> x[2]:= (90u,90u) ;
> x[3]:= (140u,90u) ;
> \stopMPinclusions
>
> \startreusableMPgraphic{test}
> draw p ;
> for i=0 step 1 until 3 :
> drawdot x[i] ;
> endfor ;
> \stopreusableMPgraphic
>
> \starttext
> \reuseMPgraphic{test}
>
>
> More generaly, which kind of variables cannot be stored in
> \startMPinclusions ?
>
> Thanks,
>
>
> Damien Thiriet
> ___________________________________________________________________________________
> 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://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
Taco Hoekwater
Elvenkind BV
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2019-02-21 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 9:03 Damien Thiriet
2019-02-21 9:44 ` Hans Hagen
2019-02-21 9:51 ` Taco Hoekwater [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=E61D32EE-426E-4140-8CBB-315AEFDF8242@elvenkind.com \
--to=taco@elvenkind.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).