Re: [Plplot-devel] Bug in notcrossed() function of plfill.c

2016-09-12 Thread Arjen Markus
Hi Phil, > -Original Message- > From: Phil Rosenberg [mailto:p.d.rosenb...@gmail.com] > > In this special case the three short sides are all approximately 2 Plplot > internal units > long which fools the intersection test into thinking they are close to > parallel to the > test line.

Re: [Plplot-devel] Bug in notcrossed() function of plfill.c

2016-09-12 Thread Alan W. Irwin
Hi Phil: It was good to hear from you again. On 2016-09-12 03:06+0100 Phil Rosenberg wrote: > Hi All > It's been a while. Sorry for my lack of activity over the summer. I took quite a long break from PLplot this summer as well. So no worries about that. > > I've just picked up some Plplot ite

[Plplot-devel] Fortran build error on Ubuntu

2016-09-12 Thread Phil Rosenberg
Hi Alan I just tried to build on Ubuntu to check your results and got a build error that seems fortran related. I thought I'd start a new thread to keep the subjects separate. I'm just doing cmake .. make all My build directory is a subdirectory of the source directory. The compile error is mak

Re: [Plplot-devel] Bug in notcrossed() function of plfill.c

2016-09-12 Thread Phil Rosenberg
Hi Alan I just built on Ubuntu (disabling F95 due to the issue I reported a short while ago). I get the same full fill issue with wxWidgets, but not with other drivers. I guess each driver may use slightly different geometry so it ruins the example. Please could you try with wxWidgets driver or let

Re: [Plplot-devel] Bug in notcrossed() function of plfill.c

2016-09-12 Thread Phil Rosenberg
>>> I'm still of the opinion that the notcrossed function should not use >>> the 2 pixel fuzziness. At this point in the drawing we are dealing in >>> integer pixels and we need only an epsilon test I think. I think the >>> best fix is to change this. There are some sticking plaster solutions >>> t

Re: [Plplot-devel] Bug in notcrossed() function of plfill.c

2016-09-12 Thread Phil Rosenberg
sorry meant "no doubt that the point" not "no count that the point" On 12 September 2016 at 21:39, Phil Rosenberg wrote: I'm still of the opinion that the notcrossed function should not use the 2 pixel fuzziness. At this point in the drawing we are dealing in integer pixels and we

Re: [Plplot-devel] Fortran build error on Ubuntu

2016-09-12 Thread Alan W. Irwin
On 2016-09-12 21:07+0100 Phil Rosenberg wrote: > Hi Alan > I just tried to build on Ubuntu to check your results and got a build > error that seems fortran related. I thought I'd start a new thread to > keep the subjects separate. I'm just doing > > cmake .. > make all > > My build directory is a

Re: [Plplot-devel] Bug in notcrossed() function of plfill.c

2016-09-12 Thread Alan W. Irwin
On 2016-09-12 21:21+0100 Phil Rosenberg wrote: > Hi Alan > I just built on Ubuntu (disabling F95 due to the issue I reported a > short while ago). I get the same full fill issue with wxWidgets, but > not with other drivers. I guess each driver may use slightly different > geometry so it ruins the

Re: [Plplot-devel] Bug in notcrossed() function of plfill.c

2016-09-12 Thread Alan W. Irwin
On 2016-09-12 21:39+0100 Phil Rosenberg wrote: I'm still of the opinion that the notcrossed function should not use the 2 pixel fuzziness. At this point in the drawing we are dealing in integer pixels and we need only an epsilon test I think. I think the best fix is to change t

Re: [Plplot-devel] Fortran build error on Ubuntu

2016-09-12 Thread Arjen Markus
Hi Phil, Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > > Hi Phil: > > ... > > Could the problem be that you are using an older version of gfortran that > does not > completely support the Fortran 2003 standards that we depend on for our new > For

Re: [Plplot-devel] Bug in notcrossed() function of plfill.c

2016-09-12 Thread Arjen Markus
Hi Phil, Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > > @Arjen: I am interested whether gcc on Cygwin for this current example > triggers > the bug or not. > I will test it but it may be a one or two days before I get around to it. Regards, Arj