Hi all,
just a heads-up since I normally don't mess with the actual repo. I
just committed
planck[backends]> svn diff backend_qt4agg.py
Index: backend_qt4agg.py
···
===================================================================
--- backend_qt4agg.py (revision 3201)
+++ backend_qt4agg.py (working copy)
@@ -4,6 +4,8 @@
from __future__ import division
import os, sys
+
+import matplotlib
from matplotlib import verbose
from matplotlib.cbook import enumerate
from matplotlib.figure import Figure
as r3202.
That missing import would cause all kinds of problems, including the
'save' button in the GUI not working at all.
John: unfortunately it's too late to propagate these changes to the
lab, I'm afraid (as trivial as they are).
Cheers,
f
I don't understand how that could have happened. I've been using qt4agg for a
long time, and have never had trouble with the save button until now.
Darren
···
On Tuesday 10 April 2007 01:49:22 pm Fernando Perez wrote:
Hi all,
just a heads-up since I normally don't mess with the actual repo. I
just committed
planck[backends]> svn diff backend_qt4agg.py
Index: backend_qt4agg.py
--- backend_qt4agg.py (revision 3201)
+++ backend_qt4agg.py (working copy)
@@ -4,6 +4,8 @@
from __future__ import division
import os, sys
+
+import matplotlib
from matplotlib import verbose
from matplotlib.cbook import enumerate
from matplotlib.figure import Figure
as r3202.
That missing import would cause all kinds of problems, including the
'save' button in the GUI not working at all.
John: unfortunately it's too late to propagate these changes to the
lab, I'm afraid (as trivial as they are).
Could be only triggered by a particular rc file setup, but we did see
the problem.
Cheers,
f
···
On 4/10/07, Darren Dale <dd55@...143...> wrote:
I don't understand how that could have happened. I've been using qt4agg for a
long time, and have never had trouble with the save button until now.