From: Hans Hagen <pragma@wxs.nl>
Subject: Re: colors in MPgraphic
Date: Fri, 06 Jan 2006 15:08:28 +0100 [thread overview]
Message-ID: <43BE79DC.5060600@wxs.nl> (raw)
In-Reply-To: <6faad9f00601060458p22fc3e7bxd0f5462bdee041c7@mail.gmail.com>
Mojca Miklavec wrote:
>>Question: what tinkering with metapost parameters is done in
>>\startMPgraphic exactly? (I could not find out readily from the
>>ConTeXt sources)
>>Which of these can be removed without danger for its operation,
>>leaving settings in \startMPinclusions unchanged -- and will that be
>>done?
>>
>>
>
>Hans will probably answer you better, but in
>http://source.contextgarden.net/metafun.mp
>there are files with metafun macros included which may set their own
>colors. See those files.
>
>I doubt that any definitions can be removed without breaking anything
>(otherwise they wouldn't be there), but I agree that MPinclusions
>could/should be included AFTER metafun macros if they're not (I didn't
>check).
>
>
(1) metafun is a format and will be loaded first
(2) inclusion scome after loading the format
(3) context only sets a bunch of variables which tell metafun certain
things
i'm not sure what you mean with tinkering
what parameters give you problems?
concerning backgrounds and plain.mf ... metafont has bacckgrounds,
metapost doesn't ; in mp the background is used for unfilling
if you want to set the background / add own stuff you can probably best
append the relevant settings / definitions to the extra_beginfig string
(grep for that one)
Hans
next prev parent reply other threads:[~2006-01-06 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 12:14 Hans van der Meer
2006-01-06 12:58 ` Mojca Miklavec
2006-01-06 14:08 ` Hans Hagen [this message]
2006-01-06 14:19 ` Taco Hoekwater
2006-01-06 16:27 ` Hans van der Meer
2006-01-06 17:56 ` Hans Hagen
2006-01-06 20:43 ` Hans van der Meer
2006-01-06 22:08 ` Hans Hagen
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=43BE79DC.5060600@wxs.nl \
--to=pragma@wxs.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).