Skip to content

Commit 6a05da9

Browse files
Update README.md
1 parent e932fb6 commit 6a05da9

File tree

1 file changed

+7
-3
lines changed

1 file changed

+7
-3
lines changed

README.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -98,11 +98,15 @@ for more details on API limitations when comparing to Qwt.
9898

9999
Try running the `curvebenchmark1.py` test with PyQt5 and PySide: you will notice a
100100
huge 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

104107
As 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

107111
However, PySide2 support was significatively improved betwen PythonQwt V0.8.0 and
108112
V0.8.1 thanks to the new `array2d_to_qpolygonf` function (see the part related to

0 commit comments

Comments
 (0)