From: Alan via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen via ntg-context <ntg-context@ntg.nl>
Cc: Alan <braslau.list@comcast.net>
Subject: Re: no greyscales in MetaFun any more?
Date: Thu, 21 Jul 2022 09:16:59 -0600 [thread overview]
Message-ID: <20220721091659.4764fd4d@boo.my.domain> (raw)
In-Reply-To: <1ebccd7e-d19e-36aa-0148-0734857f2adc@freedom.nl>
On Sun, 17 Jul 2022 23:46:36 +0200
Hans Hagen via ntg-context <ntg-context@ntg.nl> wrote:
> On 7/17/2022 9:52 PM, Henning Hraban Ramm via ntg-context wrote:
> > Hi Hans et al.,
> >
> > all my greys are black:
> >
> > % MWE:
> > \startMPpage
> > fill unitsquare scaled 10mm withcolor .5;
> > \stopMPpage
> >
> > % real life example:
> > \startMPpage
> > % grayscale squares
> > for s=5 step 5 until 95:
> > numeric c; c := s/100;
> > fill unitsquare scaled 5mm shifted (0,(s-5)*mm) withcolor c;
> > label.lft(100-s, (0, (s-2.5)*mm));
> > endfor;
> > \stopMPpage
> >
> > This used to work with previous LMTX versions.
> fixed in next upload
Is this related?
(regression: uniqueMPgraphic drops color)
\startuniqueMPgraphic{red}
draw textext("red?") withcolor red ;
\stopuniqueMPgraphic
\starttext
\startMPcode
draw textext("red!") withcolor red ;
\stopMPcode
\uniqueMPgraphic{red}
\stoptext
Alan
___________________________________________________________________________________
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-07-21 15:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 19:52 Henning Hraban Ramm via ntg-context
2022-07-17 21:46 ` Hans Hagen via ntg-context
2022-07-21 15:16 ` Alan 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=20220721091659.4764fd4d@boo.my.domain \
--to=ntg-context@ntg.nl \
--cc=braslau.list@comcast.net \
/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).