From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Shading to transparent using withshademethod
Date: Thu, 28 Jan 2016 12:33:39 +0100 [thread overview]
Message-ID: <56A9FC93.1010709@wxs.nl> (raw)
In-Reply-To: <20160128114553.3e4fb3a7@homerow>
On 1/28/2016 11:45 AM, Marco Patzer wrote:
> On Thu, 28 Jan 2016 09:43:24 +0100
> Hans Hagen <pragma@wxs.nl> wrote:
>
>> On 1/27/2016 10:05 PM, Marco Patzer wrote:
>>> The new code appears to work in general, but only if no shading to
>>> transparent is being used:
>>>
>>> \definecolor [trans] [a=multiply, t=.5, s=.5]
>>> \starttext
>>> \startMPcode
>>> % works
>>> fill fullcircle scaled 10cm withcolor \MPcolor{trans};
>>>
>>> fill fullsquare xyscaled (15cm, 15cm)
>>> withshademethod "linear"
>>> withshadevector (0,1)
>>> % works
>>> withshadecolors (red,\MPcolor{blue})
>>> % fails
>>> %% withshadecolors (red,\MPcolor{trans})
>>> ;
>>> \stopMPcode
>>> \stoptext
>>>
>>> How to make transparent shadings work with the new mechanism?
>>
>> withtransparency (1,.5)
>
> However, this makes the entire shade transparent. How to shade from
> one colour to transparent using withtransparency to achieve an
> effect like in the example below?
that isn't how shading works, it's a vector from one color to the other
(same color space eventually) and transparency is a property of the whole
> \definecolor [trans] [a=multiply, t=0]
> \setupbackgrounds [page] [background=color, backgroundcolor=lightgray]
>
> \starttext
> \startMPcode
> fill fullsquare xyscaled (15cm, 15cm)
> withshademethod "linear"
> withshadevector (0, 1)
> %% colour doens't match
> %% withshadecolors (red, lightgray)
> %% output is ok with \MPcolor
> withshadecolors (red, \MPcolor{lightgray})
> %% ??
> %% withtransparency (1, .5)
> ;
> \stopMPcode
> \stoptext
>
> Furthermore, why do the tex and MP colours differ? Wouldn't it make
> sense to use the same colour definitions? Or was that intentional?
it's already hard enough to have what we have now (tex and mp are
different species)
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-01-28 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 21:05 Marco Patzer
2016-01-28 8:43 ` Hans Hagen
2016-01-28 10:45 ` Marco Patzer
2016-01-28 11:33 ` Hans Hagen [this message]
2016-01-28 12:53 ` Marco Patzer
2016-01-28 13:45 ` Hans Hagen
2016-01-28 14:34 ` Marco Patzer
2016-01-28 17:26 ` Hans Hagen
2016-01-28 18:09 ` Marco Patzer
2016-01-28 11:29 ` Hans Hagen
2016-01-28 13:02 ` Marco Patzer
2016-01-28 15:16 ` 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=56A9FC93.1010709@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).