From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Fuzzy lines
Date: Wed, 12 May 2021 19:55:25 +0200 [thread overview]
Message-ID: <092986D0-2072-4907-9B86-B54D0FC3D690@fiee.net> (raw)
In-Reply-To: <CAKyqqaZbh9rKkQa6kCyr16CXJ1vZu___jW=jfJ-YUkpQPYjk8A@mail.gmail.com>
Hi Jairo,
thank you for the suggestion.
> Am 11.05.2021 um 14:56 schrieb Jairo A. del Rio <jairoadelrio6@gmail.com>:
>
> For simple pens, you may define your own (section 9.7 of MetaPost manual).
Unfortunately, pens don’t work as patterns but only as outlines.
> For complicated strokes, something along these lines could be useful as a starting point (I'm not taking cyclic paths in consideration, btw). I did something similar with duck footprints some weeks ago:
>
> %Sorry for the ugly code...
> \starttext
> \startMPpage
> %Unit size
> numeric u; u := 1mm;
>
> %In a picture you are able to include everything, kinda
> picture Pluma;
> Pluma := image(
> for i = 1 upto 5:
> for j = 1 upto 5:
> draw (i,j) randomized 1;
> endfor
> endfor
> );
Unfortunately, that’s the same pattern over and over.
The randomization is only applied once.
Good for footprints, bad for fuzzy patterns.
> %Simple curve
> path Camino;
> Camino := origin for i = 1 upto 30: .. (u*i, u*sind (12i mod 360)) endfor;
>
> %Strokes
> for i = 0 step 1/2 until length Camino:
> draw Pluma rotated (90 + angle direction i of Camino)
> shifted point i of Camino;
> endfor
Since I have more or less straight lines but of different length, the "one pattern per 1/n path segment" doesn’t work for me. I could try to construct my paths differently.
Hraban
___________________________________________________________________________________
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:[~2021-05-12 17:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 10:58 Henning Hraban Ramm
2021-05-11 11:30 ` Mikael Sundqvist
2021-05-11 12:33 ` Henning Hraban Ramm
2021-05-11 12:56 ` Jairo A. del Rio
2021-05-11 16:02 ` Aditya Mahajan
2021-05-12 18:07 ` Henning Hraban Ramm
2021-05-13 13:08 ` Henning Hraban Ramm
2021-05-13 16:36 ` Aditya Mahajan
2021-05-13 16:55 ` Henning Hraban Ramm
2021-05-13 17:17 ` Aditya Mahajan
2021-05-13 18:02 ` Henning Hraban Ramm
2021-05-13 18:26 ` Thomas A. Schmitz
2021-05-13 19:42 ` Henning Hraban Ramm
2021-05-14 15:08 ` Thomas A. Schmitz
2021-05-13 22:39 ` Aditya Mahajan
2021-05-14 9:43 ` Hans Hagen
2021-05-14 20:33 ` Henning Hraban Ramm
2021-09-03 16:04 ` Henning Hraban Ramm via ntg-context
2022-01-21 18:00 ` Iterating over MP paths (was: Fuzzy lines) Henning Hraban Ramm via ntg-context
2021-05-14 10:05 ` Fuzzy lines Hans Hagen
2021-05-12 17:55 ` Henning Hraban Ramm [this message]
[not found] ` <CAKyqqaaosis=BjOD_mArY5VM+bzcj-ar4uMtnt8SRJ2WLL9ykw@mail.gmail.com>
2021-05-12 21:21 ` Fwd: " Jairo A. del Rio
2021-05-13 13:23 ` Henning Hraban Ramm
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=092986D0-2072-4907-9B86-B54D0FC3D690@fiee.net \
--to=texml@fiee.net \
--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).