ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Floris van Manen via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Floris van Manen <vm@klankschap.nl>
Subject: Re: About macro numberstriped ()
Date: Sun, 2 Oct 2022 11:20:52 +0200	[thread overview]
Message-ID: <4cb4b1b3-da2c-6783-df4a-c38d486b29b2@klankschap.nl> (raw)
In-Reply-To: <CACyK-epRvVWsWdd53WHzv8eUxxyfbDK30mZbCKcDQR_V1frgYg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 997 bytes --]



On 02/10/2022 10:55, Fabrice Couvreur via ntg-context wrote:
> Initially, there was a bug with maro numberstriped() and Hans suggested 
> another sensible approach to me, but you don't get the same shape of the 
> hatches depending on the dimensions of the squares.

some unexpected side effect show up when the unitsquare is xyscaled to a 
rectangle like (2.5cm,1cm)
it seems related to the angle chosen

e.g.



\startMPcode

path p, q, r, b ;
p  := unitsquare xyscaled (4cm,4cm) ;
q := unitsquare xyscaled (1cm,1cm) shifted(0,3cm) ;
r := unitsquare xyscaled (2.5cm,1cm) shifted(1cm,3cm) ;
b := unitsquare xyscaled (3cm,3cm) shifted(1cm,0) ;

draw r anglestriped (1,35,2) withcolor red;
draw q anglestriped (1,35,2) withcolor green;
draw b anglestriped (1,35,2) withcolor cyan;
draw p;
draw q;
draw b;
draw r;

label.llft("D", p) ;
label.lrt("C", p) ;
label.ulft("A", p) ;
label.urt("B", p) ;
label.urt("P", lrcorner r) ;
label.lft("Q", llcorner r) ;
label.top("M", urcorner r) ;

\stopMPcode

[-- Attachment #2: Screenshot from 2022-10-02 11-15-45.png --]
[-- Type: image/png, Size: 48177 bytes --]

[-- Attachment #3: Type: text/plain, Size: 496 bytes --]

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

  reply	other threads:[~2022-10-02  9:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 17:49 Fabrice Couvreur via ntg-context
2022-09-27 20:04 ` Hans Hagen via ntg-context
2022-09-28 13:11   ` Fabrice Couvreur via ntg-context
2022-09-28 13:29     ` Hans Hagen via ntg-context
2022-09-28 19:04       ` Henning Hraban Ramm via ntg-context
2022-10-01 17:42         ` Fabrice Couvreur via ntg-context
2022-10-01 19:46           ` Mikael Sundqvist via ntg-context
2022-10-02  8:55             ` Fabrice Couvreur via ntg-context
2022-10-02  9:20               ` Floris van Manen via ntg-context [this message]
2022-10-02  9:49                 ` Fabrice Couvreur via ntg-context
2022-10-02  9:52                 ` Hans Hagen via ntg-context
2022-10-02 11:02                   ` Fabrice Couvreur via ntg-context
2022-10-02 11:38                     ` Hans Hagen via ntg-context
2022-10-02 13:13                       ` Fabrice Couvreur via ntg-context
2022-10-02 13:26                         ` Hans Hagen via ntg-context
2022-10-02 13:36                           ` Mikael Sundqvist via ntg-context
2022-10-02 16:15                             ` Fabrice Couvreur 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=4cb4b1b3-da2c-6783-df4a-c38d486b29b2@klankschap.nl \
    --to=ntg-context@ntg.nl \
    --cc=vm@klankschap.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).