Seems like a good idea to me. I'm a little surprised we haven't seen
this case before. Thanks for the patch -- it's committed in SVN r4391.
Cheers,
Mike
Ben North wrote:
> Hi,
>
> I think there is a bug in the PostScript backend, when trying to draw a
> polygon with zero linewidth. If you ha
Hi,
I think there is a bug in the PostScript backend, when trying to draw a
polygon with zero linewidth. If you have a zero linewidth, the
generated PostScript is along the lines of
173.31 49.274 m
305.066 57.999 l
173.533 46.684 l
closepath
gsave
fill
grestore
whereas if t
I sent a note a while ago about a key events being broken. I have a
bit more information, but still no solution:
- Other mouse-based events seem to work just fine
- Key events broke somewhere between 2007-11-7 and 2007-11-10
-Rob
Rob Hetland, Associate Professor
Dept. of Oceanogr
On Nov 20, 2007 7:44 AM, Rob Hetland <[EMAIL PROTECTED]> wrote:
>
>
> I sent a note a while ago about a key events being broken. I have a
> bit more information, but still no solution:
>
> - Other mouse-based events seem to work just fine
> - Key events broke somewhere between 2007-11-7 and 20
On Nov 20, 2007, at 3:12 PM, John Hunter wrote:
> I am using tkagg with svn and key events are working. Just to make
> sure we are doing exactly the same thing, I am running
> examples/simple_plot.py with -dTkAgg and clicking in the subplot area
> and then pressing 'g' to toggle the grid on and
On Nov 20, 2007 9:15 AM, Rob Hetland <[EMAIL PROTECTED]> wrote:
>
> On Nov 20, 2007, at 3:12 PM, John Hunter wrote:
> I am using Mac OS X 10.4.11, python 2.5, and svn versions of numpy
> and mpl. I use Tk/Tcl 8.4.7 that (if I remember right) came with the
> OS. I did not use the simple_plot, but
On Nov 20, 2007, at 5:09 PM, John Hunter wrote:
> Are you on this box now to verify the problem? There was a bug in
> keypress_demo, because the demo was using 'g' to turn the grid on and
> off and the default key interaction was doing the same, resulting in a
> double toggle and no change. I f
On Nov 18, 2007 10:10 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
>
> On Nov 18, 2007 11:33 AM, Eric Firing <[EMAIL PROTECTED]> wrote:
> > Trailing whitespace introduces noise--sometimes a *lot* of noise--into
> > svn changesets. I would very much appreciate it if everyone would try
> > to elimi
It made my merge from trunk to branch a little harder than it had to be,
too.
I understand the drive for this, but there is that downside as well.
Cheers,
Mike
John Hunter wrote:
> On Nov 18, 2007 10:10 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
>> On Nov 18, 2007 11:33 AM, Eric Firing <[EMA
Michael Droettboom wrote:
> It made my merge from trunk to branch a little harder than it had to be,
> too.
>
> I understand the drive for this, but there is that downside as well.
John, Mike,
Yes, I understand, and I am sorry--but I hope it is one-time pain to
avoid continuing pin-pricks. If
I'm not sure that this consumes enough cycles to warrant the additional
complexity of doing things differently on a per-backend basis (the
choice to stick with 8-bit colors would have to be made higher than the
backend to see any savings). The pcolor images are an exception, since
that code is
On Nov 20, 2007 11:24 AM, Rob Hetland <[EMAIL PROTECTED]> wrote:
> 2007-11-20 18:13:23.074 Python[24184] *** _NSAutoreleaseNoPool():
> Object 0x409e190 of class NSCarbonWindowContentView autoreleased with
> no pool in place - just leaking
I googled this message and found this:
http://www.cocoabu
Publishers sometimes require electronic figures as tif or eps, and using
the cymk color system. We do everything in rgb. I don't understand
color systems well. What would be needed to give mpl the ability to
produce files using the cymk system?
Thanks.
Eric
Jeff,
as you mentioned license as one issue in not using shapely, I thought
you might be interested in this:
Original Message
Subject: [Community] Proposal to change Shapely license from LGPL to BSD
From: Sean Gillies <[EMAIL PROTECTED]>
I propose that the Shapely license be c
Christopher Barker wrote:
[...]
> As for ctypes vs. pyrex -- I find it ironic that you've chosen pyrex for
> dependency reasons -- there are lot of folks that using ctypes to asve
> the hassles of compiliation, particularly on Windows (see geoGjango, for
> instance). But I guess MPL required com
Christopher Barker wrote:
> Jeff,
>
> as you mentioned license as one issue in not using shapely, I thought
> you might be interested in this:
>
> Original Message
> Subject: [Community] Proposal to change Shapely license from LGPL to BSD
> From: Sean Gillies <[EMAIL PROTECTED]>
Jeff Whitaker wrote:
> Chris: I don't consider the pyrex GEOS interface I created for basemap
> a general-purpose binding - it's limited to the only the functionality
> that basemap needs.
sure, but if there was an existing general purpose binding that met your
needs, you wouldn't need this.
17 matches
Mail list logo