On Wed, Jun 9, 2010 at 8:17 PM, Jason Grout wrote:
> In the "call signature" of savefig found here:
>
> http://matplotlib.sourceforge.net/api/pyplot_api.html#matplotlib.pyplot.savefig
>
> it doesn't list the bbox_inches and pad_inches options, though they are
> listed in the list below the signatu
In the "call signature" of savefig found here:
http://matplotlib.sourceforge.net/api/pyplot_api.html#matplotlib.pyplot.savefig
it doesn't list the bbox_inches and pad_inches options, though they are
listed in the list below the signature.
Thanks,
Jason
---
Jae-Joon, your patch looks to be effectively the same except for
slightly different behavior when more than 3 points are present... but
that was what was originally intended - the numpoints-> scatterpoints
was a good catch!
As for allowing an array markerscale, I agree with Jae-Joon... I think
the
On 06/09/2010 10:53 AM, Jae-Joon Lee wrote:
> On Wed, Jun 9, 2010 at 4:18 PM, Eric Firing wrote:
>> My sense is that box-forced lets you shoot yourself in the foot with
>> shared axes, box doesn't. The reason I prohibited sharing x and y axes
>> with adjustable as box is that it is not clear what
I'm not very kin to implement every possible options for every possible cases.
If you need customization beyond what the current "legend" class
provide, I recommend you to use proxy artists.
http://matplotlib.sourceforge.net/users/legend_guide.html#using-proxy-artist
I personally think that the d
On Wed, Jun 9, 2010 at 4:18 PM, Eric Firing wrote:
> My sense is that box-forced lets you shoot yourself in the foot with
> shared axes, box doesn't. The reason I prohibited sharing x and y axes
> with adjustable as box is that it is not clear what should happen, or
> will happen--fundamental inc
I was trying the patch and I realized a possible use-case that might not
have been thought of before. Consider the situation where a user does a
scatter plot with markers of two different sizes. Then, it isn't that
far-fetched that the user might also want to control the markerscale for
each mark
On 06/09/2010 09:58 AM, Benjamin Root wrote:
> Has anybody given any further thought to the implication of having
> Basemap set adjustable as "box-forced" instead of "box"? So far, it has
> been working just fine for me, but I have no clue if there are any
> unintended side-effects.
My sense is t
Has anybody given any further thought to the implication of having Basemap
set adjustable as "box-forced" instead of "box"? So far, it has been
working just fine for me, but I have no clue if there are any unintended
side-effects.
Ben Root
On Tue, Jun 1, 2010 at 6:00 PM, Benjamin Root wrote:
Thanks for reporting these.
I took a look at your patch and slight revised it (see the attached).
While I believe that my patch is compatible to yours, it'll be great
if you check my patch to see if I missed anything.
I'll commit the change soon.
Regards,
-JJ
On Tue, Jun 8, 2010 at 3:16 PM, Eri
10 matches
Mail list logo
