ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jairo A. del Rio" <jairoadelrio6@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Two questions about color in MetaFun
Date: Thu, 13 Aug 2020 22:56:48 -0500	[thread overview]
Message-ID: <CAKyqqaYhUfFKLM1aRF25WgDcHg1YJkpCpLHYqChm-Vxz7-MoaQ@mail.gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.78.908.2008131945170.1544@nqv-guvaxcnq>


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

Using \MPcolor does it for me. Thank you very much, Aditya :)

Jairo :)

El jue., 13 de ago. de 2020 a la(s) 18:47, Aditya Mahajan (adityam@umich.edu)
escribió:

> On Thu, 13 Aug 2020, Jairo A. del Rio wrote:
>
> > Hi, list! I have two questions concerning MetaFun:
> >
> > 1st:
> >
> > What is the correct way to pass a ConTeXt named color (e.g. xwi's
> "maroon")
> > to MetaFun. Using (with \usecolors[xwi] loaded in the preamble):
> >
> > withcolor maroon
> >
> > does not work.
>
> You need:
>
>     withcolor \MPcolor{maroon}
>
> or (note the quotes)
>
>     withcolor "maroon"
>
> > 2nd:
> >
> > I was trying to do some stuff for my girlfriend using ConTeXt and I tried
> > to randomize colors in MetaFun using normaldeviate. However, something
> > interesting happens. The following:
> >
> > [snip]
> >
> > changes the color of every letter. I don't complain (in fact it does look
> > better), but I still have a question: what should I do if I wanted to
> > select a random color first and then use it for the entire content?
> Thanks
> > in advance.
>
>
> newcolor randomcolor;
> randomcolor := (normaldeviate, normaldeviate, normaldeviate);
>
> .... withcolor randomcolor;
>
> Aditya
>
> ___________________________________________________________________________________
> 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
>
> ___________________________________________________________________________________
>

[-- Attachment #1.2: Type: text/html, Size: 2727 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2020-08-14  3:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 22:48 Jairo A. del Rio
2020-08-13 23:47 ` Aditya Mahajan
2020-08-14  3:56   ` Jairo A. del Rio [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=CAKyqqaYhUfFKLM1aRF25WgDcHg1YJkpCpLHYqChm-Vxz7-MoaQ@mail.gmail.com \
    --to=jairoadelrio6@gmail.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).