ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Shading to transparent using withshademethod
Date: Thu, 28 Jan 2016 14:45:13 +0100	[thread overview]
Message-ID: <56AA1B69.6010802@wxs.nl> (raw)
In-Reply-To: <20160128135308.4d9da069@homerow>

On 1/28/2016 1:53 PM, Marco Patzer wrote:
> On Thu, 28 Jan 2016 12:33:39 +0100
> Hans Hagen <pragma@wxs.nl> wrote:
>
>>>>> 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,
>
> …any longer. I just confirmed that it used to work on an older
> installation. Just sayin'

are you sure? a shade goes from one color to another; transparency is 
not part of that but applied to the whole (transparency is kind of 
independent of color and in context also only coupled in definition not 
in implementation)

>> it's a vector from one color to the
>> other (same color space eventually) and transparency is a property of
>> the whole
>
> That's how the new mechanism works, apparently. But transparency can
> AFAIK also be a property of the colour. So transparency is a vector
> from one colour to the other, each possibly being partly or entirely
> transparent.

no, it's independent ... and in shades one talks of color spaces (need 
to be the same too) so in context we even need to make sure an rgb to 
cmyk shade goes well

> But as I don't understand the inner internals, I believe there's a
> good reason this has been changed.

cleaner

Hans

-----------------------------------------------------------------
                                           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
___________________________________________________________________________________

  reply	other threads:[~2016-01-28 13:45 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
2016-01-28 12:53       ` Marco Patzer
2016-01-28 13:45         ` Hans Hagen [this message]
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=56AA1B69.6010802@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).