matplotlib-devel Mailing List for matplotlib

Hello,
I was playing a bit with the clippedline example
(http://matplotlib.org/examples/pylab_examples/clippedline.html) and I
feel it is not working anymore.
From what I understand of the traceback I got, there may be something
evil happening after setting
>>> self._marker = 's'
in the draw method. Maybe using the self.set_marker('s') is safer
Also, by reading some archived emails from this mailing list, it seems
that the purpose of this example became pointless because line clipping
is now implemented directly in matplotlib. Am I right ?
For what it's worth, I modified the clippeline.py example to make it
just serve the purpose of dynamically changing the appearance of the
line when zoom level is changing. I called t "zoom_adaptive_line.py" :
https://gist.github.com/3607993
Would this script be an appropriate replacement for the clippedline
example ?
Best,
Pierre

On 26 August 2012 18:19, Michael Droettboom <md...@st...> wrote:
> I understand the comments about the difficulty of introspection. The
> reason it works the way it does is so that additional parameters can be
> added to the artist layer without needing to update every single
> plotting function. A real world example of this is when hatching was
> added -- that feature only had to be added in one place and most artists
> were able to use it. In that sense, I think this approach is very
> beautiful in terms of code maintainability and extensibility.
I'm jumping into this conversation a bit late, but from Python 3.3 it
will be possible to set a __signature__ attribute on a function, using
a Signature object which can be programmatically generated. So it
should be possible, with a bit of legwork, to introspect pass-through
parameters without having to manually declare them at the highest
level.
The details are here:
http://www.python.org/dev/peps/pep-0362/
Thanks,
Thomas

Michiel,
In the 4th comment on
https://github.com/matplotlib/matplotlib/issues/786
I give a little example illustrating a macosx bug: it seems that when 
drawing a path, the linewidth, which is specified in points, is not 
interpreted correctly unless the figure.dpi has exactly the right value. 
 For a high dpi, as in the example I gave, all lines are too thin, but 
text is still scaled correctly, and the general layout is correct.
Will you be able to take a look? We are trying to get out a release 
soon, so it would be nice to have this fixed.
Thank you.
Eric