Eric Firing wrote:
> I think this may be a slippery slope. The problem is that for it to
> work well, there has to be a clear distinction between methods that are
> endpoints, requiring a redraw, and methods that will be used by other
> methods. For example, errorbar makes multiple calls to plot, vline,
> etc.
I agree -- I don't mind a call to Draw() or something now and then.
maybe I can put them in my hypothetical OOlab (see prev. msg.) some day,
so that there are a few calls that do the draw, but not every call to
plot().
> by including an additional kwarg ("redraw=False"),
That's the question -- in my wxPython FloatCanvas, I decided that
NOTHING redraws, and you have to make a call to Draw(0 to get a re-draw.
In fact, that won't even work if the Canvas thinks nothing has changed,
so you sometimes need to call Draw(force=True). In that case, I was
optimizing for fast drawing of lots of stuff, and for embedding in a
program -- not interactive use.
I do like the default redraw of False that can be overridden -- but how
many places will that have to be added to the code?
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
[EMAIL PROTECTED]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
