File tree Expand file tree Collapse file tree 1 file changed +7
-3
lines changed
Expand file tree Collapse file tree 1 file changed +7
-3
lines changed Original file line number Diff line number Diff line change @@ -98,11 +98,15 @@ for more details on API limitations when comparing to Qwt.
9898
9999Try running the ` curvebenchmark1.py ` test with PyQt5 and PySide: you will notice a
100100huge performance issue with PySide2 (see screenshot above). This is due to the fact
101- that ` QPainter.drawPolyline ` is much more efficient in PyQt5 than it is in PySide2
102- (see [ this bug report] ( https://bugreports.qt.io/projects/PYSIDE/issues/PYSIDE-1366 ) ).
101+ that ` QPainter.drawPolyline ` (the ` QPainter.drawPolyline ` method has already been
102+ optimized thanks to Cristian Maureira-Fredes from Python-Qt development team, see
103+ [ this bug report] ( https://bugreports.qt.io/projects/PYSIDE/issues/PYSIDE-1366 ) ) is
104+ much more efficient in PyQt5 than it is in PySide2 (see
105+ [ this bug report] ( https://bugreports.qt.io/projects/PYSIDE/issues/PYSIDE-1540 ) ).
103106
104107As a consequence, until this bug is fixed in PySide2, we still recommend using PyQt5
105- instead of PySide2 when it comes to representing huge data sets.
108+ instead of PySide2 when it comes to representing huge data sets (except if you do not
109+ use the "dots" style for drawing curves).
106110
107111However, PySide2 support was significatively improved betwen PythonQwt V0.8.0 and
108112V0.8.1 thanks to the new ` array2d_to_qpolygonf ` function (see the part related to
You can’t perform that action at this time.
0 commit comments