Yes I tried without path simplification, and I don't get any crashes. If we
need to support older versions of cairo / pycairo, I suggest that we have the
path length check after checking the version of cairo / pycairo, and that we
perform the path length check after path simplification, so we kn
sweet!
John Hunter wrote:
> On Mon, Feb 22, 2010 at 11:00 AM, Tom Holroyd (NIH/NIMH) [E]
> wrote:
>> ok, this is how i do it
>> pro'ly could make this better
>
> python -c "import pylab; pylab.plotfile('temp.dat', cols=(0,2),
> delimiter=' '); pylab.show()"
>
> JDH
>
>
On Mon, Feb 22, 2010 at 11:00 AM, Tom Holroyd (NIH/NIMH) [E]
wrote:
> ok, this is how i do it
> pro'ly could make this better
python -c "import pylab; pylab.plotfile('temp.dat', cols=(0,2),
delimiter=' '); pylab.show()"
JDH
---
Michiel de Hoon wrote:
> Dear all,
>
> The draw_path method in backend_cairo.py starts with a check for the number
> of vertices in the path, and raises an error if the path contains more than
> 18980 vertices:
>
> def draw_path(self, gc, path, transform, rgbFace=None):
> if len(p
ok, this is how i do it
pro'ly could make this better
./plot file.dat
just does the first two columns
needs smarts
Tom Holroyd wrote:
here's the old way
cut and paste some numbers from a web page
like the number of live births by year
dump it in a file named moo
Sorry -- I meant remove the check for cairo >= 1.8.
Michael Droettboom wrote:
> Can you write it in such a way that the check is only removed on cairo <
> 1.8? My employer is still standardized on RHEL4, for example, which has
> cairo 1.2.
>
> Mike
>
> Michiel de Hoon wrote:
>
>> Dear all,
>
Can you write it in such a way that the check is only removed on cairo <
1.8? My employer is still standardized on RHEL4, for example, which has
cairo 1.2.
Mike
Michiel de Hoon wrote:
> Dear all,
>
> The draw_path method in backend_cairo.py starts with a check for the number
> of vertices in
Eric,
It appears to be caused by an infinite loop, and may well be due to my
changes. I'll take a look on Wednesday and get back to you.
Ian
On 22 February 2010 01:07, Eric Firing wrote:
> Ian,
>
> I hit a bug (segfault) in cntr.c that is likely related to your changes. It
> is ID 2956378 in
