# QApplication.setAttribute(Qt.ApplicationAttribute.AA_UseDesktopOpenGL)
QApplication.setAttribute(Qt.ApplicationAttribute.AA_UseOpenGLES)
QApplication.setAttribute(Qt.ApplicationAttribute.AA_ShareOpenGLContexts)
# os.environ["QTWEBENGINE_CHROMIUM_FLAGS"] = (
# "--ignore-gpu-blacklist "
# "--enable-gpu-rasterization "
# "--enable-zero-copy "
# "--num-raster-threads=4"
# "--disable-pinch"
# )
from PySide6.QtQuick import QQuickWindow, QSGRendererInterface
Kian T.Hi everyone. I have a pyside6 app for signal processing with interactive plots using pyqtgraph.
On windows there is no problem at all.
But on ubuntu, it can not show the plots that have too many points , like 60000 points in a plot, or even more.
Can I do something to solve it or it is what it is?
I don't know anything about pyqtgraph, so I can't help you there.
Try porting your graphing logic to Qt Graphs (newer QML module added in Qt 6.6 as TP, out of TP in 6.8) It's designed for higher performance than Qt Charts ever could achieve.. Not sure how it compares to pyqtgraph.
Kian T.Hi everyone. I have a pyside6 app for signal processing with interactive plots using pyqtgraph.
On windows there is no problem at all.
But on ubuntu, it can not show the plots that have too many points , like 60000 points in a plot, or even more.
Can I do something to solve it or it is what it is?
Ссылка
click to show
click to show
I have some performances issues with https://github.com/SciQLop/SciQLopPlots on Linux if I use Wayland, forcing xcb backend makes it insanely fast(er).
Kian T.Hi everyone. I have a pyside6 app for signal processing with interactive plots using pyqtgraph.
On windows there is no problem at all.
But on ubuntu, it can not show the plots that have too many points , like 60000 points in a plot, or even more.
Can I do something to solve it or it is what it is?
I do know that the maintainer, j9ac9k is on discord, in the big Python server.
https://discord.com/invite/python not sure if you have a discord account, but he is very responsive there.
Keith KyzivatAny idea what's causing it?
Not yet, I didn't investigate in details. It seems related to the number of events you get for examples when you scroll.
Qt::AA_CompressHighFrequencyEvents
Qt::AA_CompressTabletEvents
I thought there was an environment variable for this too... Maybe that is not documented, or was removed...
A customer I was working with encountered issues with specific tablets (wacom) that weren't working right that had something to do with event compression some years ago, so I was definitely investigating in that area...
I wasn't able to see any effect, I can confirm that those flags are true on X11 and false on Wayland. I didn't play with my app using wayland for some time, a the moment it's totally broken and unusable on Gnome, I even succeeded to freeze my whole desktop moving my window from one screen to another in expose mode 🤦♂️.
Anton YablokovWhy do I get 0 and then 2?
obj = QObject()
signal = SIGNAL(QObject.destroyed.signatures[0])
print(obj.receivers(signal)) # 0
obj.destroyed.connect(print)
print(obj.receivers(signal)) # 2
Hmm.
Connecting multiple slots shows it returns "number of explicit connect calls+1".
Running
obj.destroyed.connect(print)
obj.destroyed.connect(print)
obj.destroyed.connect(print)
then causes obj.receivers(signal) to return 4 (number of explicit connects + 1).
So I assume it counts some sentinel value or internal cleanup slot that is only placed/connected if anything is connected explicitly in user code.
(irc) collide2954: luziferius: Correct - Qt's receivers() includes internal bookkeeping. The +1 is Qt's connection tracking mechanism. When you connect the first slot, Qt sets up internal metadata for that signal. This is normal behavior and documented (though not prominently). Use isSignalConnected() instead if you just need to check if anyone's listening.