Hi,
I've also posted this question as a bug report at qt-project.org
(https://bugreports.qt-project.org/browse/PYSIDE-151), but this is also a PyQt
issue.
QGraphicsView is apparently very slow under Linux and Mac OS X. I've attached
an example program (runs with PySide or PyQt). The signals sh
On 04/03/2013 03:24 PM, Andreas Pakulat wrote:
first of all, QTimer gives you no guarantee that it'll fire exactly
after the given amount of time. In particular not with such small
timeouts and when having non-trivial paint functions like yours. QTimer
is bound to the event loop, hence cannot fi
On 04/03/2013 04:23 PM, Hans-Peter Jansen wrote:
What you see is possibly related to the default Qt graphics engine:
when using:
QT_GRAPHICSSYSTEM=opengl python graphicsviewtest.py
the values are oscillating around 150 here. With "native" and "raster", it's
back to 25: openSUSE 12.2/x8
On 04/03/2013 05:09 PM, Andreas Pakulat wrote:
As I said, with Qt4.8 I don't see this here on Linux at all, once the
window is at a certain size the timer fires every 25 ms again. This is
on a somewhat new system with Debians standard Qt/PyQt packages. So its
not necessarily a general problem wi
On 04/03/2013 06:46 PM, Hans-Peter Jansen wrote:
Which graphic driver do you use? (that doesn't tell us much, since the C++
version behave with the same driver, just for the record..)
xf86-video-intel 2.21.5-1
intel-dri 9.1.1-1
Might be worth to compare the C++ version (that you should publi
does work on my Mac now after this initial second (maybe
some updated got installed that fixed the problem?).
Any more ideas?
Clemens
On Apr 4, 2013, at 17:15 , Clemens Brunner wrote:
> On 04/03/2013 06:46 PM, Hans-Peter Jansen wrote:
>
>> Which graphic driver do you use? (tha
ntTime()
#if self.lastTimerEvent:
#print self.lastTimerEvent.msecsTo(currentTime)
#self.lastTimerEvent = currentTime
if __name__ == '__main__':
app = QtGui.QApplication(sys.argv)
d = Dummy()
sys.exit(app.exec_())
On 04/05/2013 08:33 PM, Clemens Brunn
