Qt for Python

@parth07sm Then read "Selecting a mirror for opensource" in https://wiki.qt.io/Online_Installer_4.x - it even shows what to do.

@ktechhydle If you enter "qt6 QWindow OpenGL" in Google first result is: https://doc.qt.io/qt-6/qtopengl-openglwindow-example.html

@JonB said in Fast loading of complex interfaces: Just one thing: let's say you leave it as-is because you don't want to divide it for whatever reason. Are you at least aware that Qt has a QSplashScreen? Didn't know that. I'll use it. tnx @jsulm said in Fast loading of complex interfaces: you can still design ui widgets for different parts of the user interface using designer. I think I'll do what you wrote. Thank you.

@Shyamnath How do I add project data files (images and QML files) to the pysidedeploy.spec file so that the generated executable file can be run anywhere?Because my data files are not being added.

@JonB in that case the OP would be testing Qt rather than his own code. Nothing wrong with writing tests that allows to understand and confirm how a given framework works as advertised but it should not be the base for the tests of your actual code as it is a different goal.

I also submited an issue on Qt issue tracker https://bugreports.qt.io/browse/PYSIDE-2955

Like I said, Qt's support for JSON or XML is not as comprehensive as Python's, and you can afford to use the latter in a Qt Python program if you want better support.

@Alberto123 said in My app doesn't appear on screen: What could I do? Provide information needed to find the issue. Especially the code...

@JonB Okay. Now it is clear. I thought the QtSql data model will manage it for me. Thank you very much!

Hi, Qt has the QColorDialog. Would that work for you ? Otherwise, you can build your widget with Qt OpenGL related classes and use shaders if you want.

@JonB Thanks for help. I experimented with sys.stdin.read(5) and it works. The data doesn't have to be binary, I can convert it, so using QTextStream, adding a trailing newline character and receiving with sys.stdin.readline() works as well.

I run into the same issue. Except I am using Pyside2. Is there any way to fix this issue? Calling update hides the window. So after setWindowFlags function, I have to call show function but like OP it flickers. Not sure why this sort of design is implemented. Can this be remedied in a future version or is there a workaround? My code is like this: def setPassThroughMode(window, enable): if enable: # Set the window to be transparent for input window.setWindowFlags(QtCore.Qt.Tool | QtCore.Qt.FramelessWindowHint | QtCore.Qt.WindowTransparentForInput) else: # Restore the normal floating window behavior window.setWindowFlags(QtCore.Qt.Tool | QtCore.Qt.FramelessWindowHint) window.setAttribute(QtCore.Qt.WA_TransparentForMouseEvents, enable) window.setAttribute(QtCore.Qt.WA_NoMousePropagation, enable) # Ensure changes take effect window.show() # Reapply visibility to update flags def togglePassThroughMode(window): # Check if the window is valid if not shiboken2.isValid(window): return # Check if the window is in pass-through mode isPassThrough = isPassThroughEnabled(window) # Toggle the state using setPassThroughMode setPassThroughMode(window, not isPassThrough) # To turn it off, you have to call the function twice if isPassThrough: setPassThroughMode(window, not isPassThrough) I have to call it twice to turn these flags off also, not sure why that is.

Hi and welcome to devnet, I haven't used that module yet however I think that manually triggering a secondary event loop like that is wrong. I just found this example which confirms my intuition.

@Dwarrel said in Pyqt Signals connecting multiple slots: My assumption was indeed that the emit would be independent of the execution time of a listener (connected function). Knowing that that is not the case completely explains the observed behaviour. OIC! The behaviour depends on the parameters to connect() and whether the signalling object and the slot object are in the same or different threads. Assuming default --- no extra parameter to connect() --- If they are in the same thread signal/slot is executed directly, upon emit signal call, i.e. it behaves just like a direct call to the slot(s). Slots are executed consecutively per the order they were connect()ed. Signaller code does not continue until all slots have completed. If they are in different threads signal causes slot(s) to be executed queued. When slot object thread next enters Qt event loop slot(s) get executed. Order is actually undetermined. Signaller code continues immediately after emit, it does not wait. Extra parameter to connect() can be used to alter default behaviour, see docs. You still should not try DirectConnection across threads, you could choose QueuedConnection if same thread. But non-default is unusual, unless you know what you are doing. P.S. I just noticed you are Python. the above is still correct, but there can be extra restrictions with multiple threads to do with Python GIL. But nothing special if all same thread.