From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Fuzzy lines
Date: Thu, 13 May 2021 20:26:46 +0200 [thread overview]
Message-ID: <1805dfd3-a8cc-3fc6-521e-54ea0bd196c3@uni-bonn.de> (raw)
In-Reply-To: <D475154D-8B65-45A7-BA63-E5DF1A0FADCA@fiee.net>
[-- Attachment #1: Type: text/plain, Size: 508 bytes --]
On 5/13/21 8:02 PM, Henning Hraban Ramm wrote:
> Unfortunately, the deviation of edge points is too big – try my attached test file.
>
> Strangely, if I include the MP code in a ConTeXt document,
I find the discussion interesting. Could you send complete documents,
like Aditya did? When I try to compile your files, I get all sorts of
errors, so I suspect they are not complete. Would be appreciated if you
could send a ConTeXt document. I'm still not quite sure what you're
looking for...
Thomas
[-- Attachment #2: test.tex --]
[-- Type: text/x-tex, Size: 462 bytes --]
\setupbodyfont[20pt]
\showframe
\startuseMPgraphic{fuzzy}
path p ; p := (0,0) -- (0,OverlayHeight) -- (OverlayWidth,OverlayHeight) --
(OverlayWidth,0) -- cycle ;
pickup pencircle scaled .5pt ;
for i=1 upto 20 :
draw p enlarged -5pt randomized 15pt withcolor blue ;
endfor ;
\stopuseMPgraphic
\defineoverlay [Fuzzy] [\useMPgraphic{fuzzy}]
\startTEXpage
\framed [height=20cm,width=12cm,frame=on,background=Fuzzy,align={middle,lohi}]
{Test}
\stopTEXpage
[-- Attachment #3: test.pdf --]
[-- Type: application/pdf, Size: 8593 bytes --]
[-- Attachment #4: 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:[~2021-05-13 18:26 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 [this message]
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
[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=1805dfd3-a8cc-3fc6-521e-54ea0bd196c3@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--cc=ntg-context@ntg.nl \
--cc=texml@fiee.net \
/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).