From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re[2]: MetaPost/Fun question
Date: Sat, 22 Mar 2003 22:32:56 +0100 [thread overview]
Message-ID: <12815828760.20030322223256@iol.it> (raw)
In-Reply-To: <5.1.0.14.1.20030322222005.026b1b68@server-1>
Saturday, March 22, 2003 Hans Hagen wrote:
>>I would like to know if it is possible in MetaPost (in particular
>>MetaFun) to get all the possible intersection points of the paths,
[snip]
>>Anything like this?
HH> not that i know, but assuming that those path have some distance, i can
HH> imagine dividing a path in parts and determining the intersectionpoints iof
HH> the pieces;
HH> delta := .25 ;
HH> for i=0 step delta upto length(p)-delta :
HH> if intersection_found(1,subpath(i,i+.1) of p) :
HH> store point
HH> fi ;
HH> endfor ;
I'll see if I can make something of this ... (wow, looks like I'm
gonna need to learn MetaPost too ...)
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2003-03-22 21:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-22 20:59 Giuseppe Bilotta
2003-03-22 21:23 ` Hans Hagen
2003-03-22 21:32 ` Giuseppe Bilotta [this message]
2003-03-22 23:35 ` Re[2]: " Emil Hedevang Lohse
2003-03-23 13:34 ` Re[4]: " Giuseppe Bilotta
2003-03-24 12:53 ` Guy Worthington
2003-03-24 13:49 ` Giuseppe Bilotta
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=12815828760.20030322223256@iol.it \
--to=gip.bilotta@iol.it \
--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).