Hi all,
I was made aware of this thread and thought I’d share a notebook I recently
made for a similar purpose:
http://nbviewer.ipython.org/gist/krischer/d35096a9d3b6da5846a5
http://nbviewer.ipython.org/gist/krischer/d35096a9d3b6da5846a5 (takes a while
to load…)
It attempts to “optimize
I, for one, would love to see a pull request for this if you're game.
Mike
On 11/24/2014 04:27 AM, Lion Krischer wrote:
Hi all,
I was made aware of this thread and thought I’d share a notebook I
recently made for a similar purpose:
That is super cool. I was thinking about doing something similar, glad it
has already been so well done.
The example figures at the bottom bring up another point, we should have a
canonical set of test figures, both for the color map and the defaults in
general, I think that will really help
On Sun, Nov 23, 2014 at 12:59 PM, Eric Firing efir...@hawaii.edu wrote:
On 2014/11/23, 12:18 PM, Benjamin Root wrote:
Reading through the backend_wx.py code, I noticed a small deviation from
the other interactive backends. All other
new_figure_manager_given_figure() separately creates a
It is odd you mentioned the extra refreshes. I have to double-check my book
examples, but I think I found that I needed to add some extra draw_idle()
calls when using native wx widgets.
This does raise another point. As a development policy, how should we treat
the backends? Should we be free to
On Mon, Nov 24, 2014 at 9:41 AM, Benjamin Root ben.r...@ou.edu wrote:
It is odd you mentioned the extra refreshes. I have to double-check my
book examples, but I think I found that I needed to add some extra
draw_idle() calls when using native wx widgets.
I haven't messed with widgets within
On 24 Nov 2014 12:42, Benjamin Root ben.r...@ou.edu wrote:
It is odd you mentioned the extra refreshes. I have to double-check my
book examples, but I think I found that I needed to add some extra
draw_idle() calls when using native wx widgets.
This does raise another point. As a development
