Andrew Straw wrote:
> jason-s...@creativetrax.com wrote:
>
>> On this thread:
>>
>> http://www.mail-archive.com/matplotlib-devel@lists.sourceforge.net/msg05383.html
>>
>> clip_on was a suggested way of getting around the clipping that happens
>> at the edge of a frame. In the Sage project, we
Michael Droettboom wrote:
> I think this is just a vanilla bug that set_clip_on is being ignored for
> collections. That patch is rather straightforward.
>
> Other developers: do you agree this should be fixed, or is there a good
> reason for current behavior that I'm missing?
It certainly loo
I think this is just a vanilla bug that set_clip_on is being ignored for
collections. That patch is rather straightforward.
Other developers: do you agree this should be fixed, or is there a good
reason for current behavior that I'm missing?
Cheers,
Mike
Index: lib/matplotlib/collections.py
=
jason-s...@creativetrax.com wrote:
> On this thread:
>
> http://www.mail-archive.com/matplotlib-devel@lists.sourceforge.net/msg05383.html
>
> clip_on was a suggested way of getting around the clipping that happens
> at the edge of a frame. In the Sage project, we are always setting the
> limits
On this thread:
http://www.mail-archive.com/matplotlib-devel@lists.sourceforge.net/msg05383.html
clip_on was a suggested way of getting around the clipping that happens
at the edge of a frame. In the Sage project, we are always setting the
limits on the axes via set_xlim and set_ylim. Is the
