Hello,
recently I upgraded to matplotlib 1.0.0 which I mainly use for plotting in my
(python 2.6 based) application with Qt4 GUI. Overall it works fine, but there
are a few issues I experienced also with the previous version, especially with
the toolbar.
When building a standalone version usin
On 06/11/2010 08:03 AM, Michael Droettboom wrote:
> Wx, Gtk, Tk all work for me. Couldn't test Qt "classic" as I don't have
> pyqt 3.x installed on my system.
I just now installed pyqt3 (after some thrashing around--it turns out
one needs the python-qt-dev package on ubuntu), and verified that q
Wx, Gtk, Tk all work for me. Couldn't test Qt "classic" as I don't have
pyqt 3.x installed on my system.
Mike
On 06/11/2010 01:56 PM, Eric Firing wrote:
> On 06/11/2010 07:44 AM, Michael Droettboom wrote:
>
>> The Qt4 backend crashes with a Segmentation Fault when no toolbar is
>> requested
On 06/11/2010 07:44 AM, Michael Droettboom wrote:
> The Qt4 backend crashes with a Segmentation Fault when no toolbar is
> requested. For example:
Mike,
Have the other backends been tested for the same problem?
Eric
>
> from matplotlib import pyplot as plt
> from matplotlib import rcParams
> rc
The Qt4 backend crashes with a Segmentation Fault when no toolbar is
requested. For example:
from matplotlib import pyplot as plt
from matplotlib import rcParams
rcParams['toolbar'] = 'None'
fig=plt.figure()
plt.show()
I have attached a possible patch, but since I've never really touched
th
2009/12/31 Fernando Perez :
> On Thu, Dec 31, 2009 at 4:54 AM, Darren Dale wrote:
>> I have been resistant to committing this patch because (in my opinion)
>> mpl should not have to provide workarounds for bugs in package X on OS
>> Y, distribution Z. I think this particular issue was fixed when
>
On Thu, Dec 31, 2009 at 4:54 AM, Darren Dale wrote:
> I have been resistant to committing this patch because (in my opinion)
> mpl should not have to provide workarounds for bugs in package X on OS
> Y, distribution Z. I think this particular issue was fixed when
> PyQt4-4.6.2 was released. But it
On Wed, Dec 30, 2009 at 11:11 PM, Fernando Perez wrote:
> Howdy,
>
> On Sat, Nov 7, 2009 at 12:30 PM, Darren Dale wrote:
>> Me too. And thank you for posting the report and a workaround.
>
> Quick question: would it be worth adding this monkeypatch to mpl
> proper? Right now, the qt4 backend is
Howdy,
On Sat, Nov 7, 2009 at 12:30 PM, Darren Dale wrote:
> Me too. And thank you for posting the report and a workaround.
Quick question: would it be worth adding this monkeypatch to mpl
proper? Right now, the qt4 backend is effectively unusable out of the
box in distros like Karmic. Which i
On Sat, Nov 7, 2009 at 9:53 AM, Pierre Raybaut wrote:
>>
>> On Wed, Nov 4, 2009 at 5:29 PM, Pierre Raybaut
>> wrote:
>>
>>>
>>> > A simpler fix would be:
>>> >
>>> > ? ? ? ?class FigureWindow(QtGui.QMainWindow):
>>> > ? ? ? ? ? ?def __init__(self):
>>> > ? ? ? ? ? ? ? ?super(FigureWindow, self)._
>
> On Wed, Nov 4, 2009 at 5:29 PM, Pierre Raybaut wrote:
>
>> > A simpler fix would be:
>> >
>> > ? ? ? ?class FigureWindow(QtGui.QMainWindow):
>> > ? ? ? ? ? ?def __init__(self):
>> > ? ? ? ? ? ? ? ?super(FigureWindow, self).__init__()
>> >
>> > ? ? ? ? ? ?def closeEvent(self, event):
>> > ?
A simpler fix would be:
class FigureWindow(QtGui.QMainWindow):
def __init__(self):
super(FigureWindow, self).__init__()
def closeEvent(self, event):
super(FigureWindow, self).closeEvent(event)
self.emit
Hi,
Some Spyder users have reported a critical bug occuring with matplotlib
0.99's Qt4 backend and PyQt4 v4.6 (e.g. in Ubuntu Karmic).
Here is the traceback after calling 'plot([])', closing figure and
calling again 'plot([])' (e.g. in an IPython session with options
--pylab and --q4thread):
On Sun, Jan 27, 2008 at 11:43:16AM -0500, Darren Dale wrote:
> He also asked if it would be a good idea to render multiple figures into a
> tab
> widget instead of creating multiple windows. Its an interesting idea, but
> since the size of each figure may vary, it would mean each figure would ha
> He also asked if it would be a good idea to render multiple figures into a
> tab
> widget instead of creating multiple windows. Its an interesting idea, but
> since the size of each figure may vary, it would mean each figure would have
> to be rendered into a scrollable area. That might be a
On Sunday 27 January 2008 11:43:16 am Darren Dale wrote:
> Hi Martin,
>
> On Sunday 27 January 2008 8:51:37 am Martin Teichmann wrote:
> > Some months ago, I proposed some improvements of the Qt4 backend,
> > especially using the Qt4 toolbar instead of writing our own hand-coded
> > toolbar, amongs
Hi Martin,
On Sunday 27 January 2008 8:51:37 am Martin Teichmann wrote:
> Some months ago, I proposed some improvements of the Qt4 backend,
> especially using the Qt4 toolbar instead of writing our own hand-coded
> toolbar, amongst other detailed changes. I was told that was bad timing, as
> a new
Hi,
Some months ago, I proposed some improvements of the Qt4 backend, especially
using the Qt4 toolbar instead of writing our own hand-coded toolbar, amongst
other detailed changes. I was told that was bad timing, as a new release was
about to come out, and the project was in frozen. I promised t
Hi Jim,
On Wednesday 31 May 2006 11:51, James Amundson wrote:
> Hello,
>
> I have ported the existing Qt(3) backend to Qt4. Qt4 is a substantial
> change from Qt3; the Python bindings for Qt have also changed
> substantially. Since the two versions of Qt are likely to coexist for at
> least a whil
Hi Jim,
Would you send me your files? I'm interested in using Qt4 myself.
Thanks,
Darren
On Wednesday 31 May 2006 11:51, James Amundson wrote:
> Hello,
>
> I have ported the existing Qt(3) backend to Qt4. Qt4 is a substantial
> change from Qt3; the Python bindings for Qt have also changed
> subs
Hello,
I have ported the existing Qt(3) backend to Qt4. Qt4 is a substantial
change from Qt3; the Python bindings for Qt have also changed
substantially. Since the two versions of Qt are likely to coexist for at
least a while, I think it makes sense to have a separate Qt4 backend.
How do I go ab
21 matches
Mail list logo
