From: Keith McKay via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Keith McKay <mckaymeister@gmail.com>
Subject: Re: Radius attribute and scaling in lmt_shade[ ]
Date: Sun, 9 Jan 2022 15:53:16 +0000 [thread overview]
Message-ID: <fc6b6c26-58a0-9551-e724-90f77ff26c3d@gmail.com> (raw)
In-Reply-To: <139b90cc-58cc-b0a5-28fe-153caca91452@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2207 bytes --]
Since "a picture paints a thousand words", I attach a pdf showing the
results of the execution of the code.
Are these bugs or... ?
Best Wishes
Keith
On 06/01/2022 15:57, Keith McKay wrote:
>
> Hi
>
> In the code below you will see that I have created a closed path and
> performed scaling, and shading on the path with lmt_shade [ ]. I have
> noticed a few features which may or may not be bugs depending on
> whether scaled is applied to the path within the square brackets or
> outside.
>
> 1) Applying scaled to the path within the square brackets and
> incrementing the radius key I can see the shaded areas changing,
> however the first two shapes show incorrect scaling and have ragged edges.
>
> 2) When scaled is applied outside the square brackets all shapes are
> the same size and no ragged edges, however the shading is not showing
> correctly with increasing radius.
>
> Am I missing something?
>
> Best Wishes
>
> Keith McKay
>
> *******************MWE*****************
>
> \setuppapersize[A4, landscape]
>
> \starttext
>
> \dorecurse{10}{
>
> \startMPpage
>
> StartPage;
>
> width := 27; height := 18;
>
> path r;
>
> r := (0.25cm,0cm)--(0cm,1.5cm)..(0.25cm,1.75cm)..(0.5cm,1.5cm) -- cycle;
>
> definecolor [ name = "MyColor1", r = uniformdeviate(1), g =
> uniformdeviate(1), b = uniformdeviate(1) ] ;
>
> definecolor [ name = "MyColor2", r = uniformdeviate(1), g =
> uniformdeviate(1), b = uniformdeviate(1) ] ;
>
> for k = 0.5 step 0.25 until 2:
>
> draw lmt_shade [
>
> path = r ,
>
> direction = "up",
>
> alternative = "circular",
>
> radius = k*cm,
>
> colors = { "MyColor1", "MyColor2" },
>
> ] scaled 4.5 shifted((k *12)*cm,12*cm);
>
> draw lmt_shade [
>
> path = r scaled 4.5,
>
> direction = "up",
>
> alternative = "circular",
>
> radius = k*cm,
>
> colors = { "MyColor1", "MyColor2" },
>
> ] shifted((k *12)*cm,1cm);
>
> endfor;
>
> StopPage;
>
> \stopMPpage
>
> }
>
> \stoptext
>
[-- Attachment #1.2: Type: text/html, Size: 7485 bytes --]
[-- Attachment #2: RS4 copy.pdf --]
[-- Type: application/pdf, Size: 4654 bytes --]
[-- Attachment #3: 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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-01-09 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 15:57 Keith McKay via ntg-context
2022-01-09 15:53 ` Keith McKay via ntg-context [this message]
2022-01-09 22:26 ` Hans Hagen via ntg-context
2022-01-12 11:24 ` Keith McKay via ntg-context
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=fc6b6c26-58a0-9551-e724-90f77ff26c3d@gmail.com \
--to=ntg-context@ntg.nl \
--cc=mckaymeister@gmail.com \
/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).