Curiouslearn wrote:
Taco, thanks for the suggestions. I will try using intersectiontimes.
It would be great if, as you said, this is solved with Metapost 2.0.
Any idea when that version is coming out?
Next summer
_
Taco, thanks for the suggestions. I will try using intersectiontimes.
It would be great if, as you said, this is solved with Metapost 2.0.
Any idea when that version is coming out?
Thanks.
On Wed, Nov 25, 2009 at 2:47 AM, Taco Hoekwater wrote:
> Taco Hoekwater wrote:
>>
>> The solution is to ad
Taco Hoekwater wrote:
The solution is to add an explicit fix to Lint[4] just after its
current assignment:
Lint[4]:=(xpart Lint[4], 0);
Even better is to not use intersectionpoint at all: use
intersectiontimes instead. With that, you can select a point
that is guaranteed to be on one of t
luigi scarso wrote:
On Wed, Nov 25, 2009 at 5:45 AM, Curiouslearn wrote:
The code below shows a cyclic path that I am interested in creating
(it is in red if you run the code). The example works fine as long as
I have, u:=1cm, as in the code below. But if I replace it by ,
u:=0.6cm, there is no
On Wed, Nov 25, 2009 at 5:45 AM, Curiouslearn wrote:
> The code below shows a cyclic path that I am interested in creating
> (it is in red if you run the code). The example works fine as long as
> I have, u:=1cm, as in the code below. But if I replace it by ,
> u:=0.6cm, there is no output. There
The code below shows a cyclic path that I am interested in creating
(it is in red if you run the code). The example works fine as long as
I have, u:=1cm, as in the code below. But if I replace it by ,
u:=0.6cm, there is no output. There is an error saying that paths 4
and 3 do not intersect. Is thi
