Qt for Python (PySide/Shiboken)

I found to drastic to do a fatal error if you try to connect to something that's not decorated as Slot

@cmaureir How bindings.xml detect Qt Version in: <object-type name="QMessageLogContext" since="5.14"/> How```since="5.14``` works?

Now, I have another error: qt.shiboken:-1: error: (bindings) Duplicate type entry: 'QMessageLogContext'

did you also declared it in your local typesystem?

From other sied, typesystem_core_common.xml has twice definition of QMessageLogContext with different Qt versions: <object-type name="QMessageLogContext" since="5.14"/> <object-type name="QMessageLogContext" since="5.9" until="5.13.2"> <modify-function signature="copy(const QMessageLogContext &amp;)" remove="all"/> </object-type> Therefore, I think, that my qt version is not defined and I included QMessageLogContext twice

that's ok, because there is a special function from 5.9 too 5.13.2

yes, and that's only 1 little issue, I'm pretty sure other things will break too.

But, the main difference - I use Qt from conan and build it manually with clang

I understand that, but we need to discover where does it fail to detect the version

The main goals of using conan - dependecy management for C++. Qt is not once library, that I used. Also, I use libssh2 amd libyaml. Also, I can choose which Qt modules and component I need. By the one code line I can choose static or shared Qt compilation, that will depends from other options, for example.

I'd go with "don't use a thread, use QNetworkAccessManager" this time (though the answer isn't as clear as with QTimer, since requests is easier to use than QNAM)

I'm confused( i deleted all my previous posts to ask in a clean new post). Does threading by creating a Qobject and moving it to a QThread create an event loop?(which does not return therefore the finished signal is not emitted) while subclassing QThread and reimplementing the run method causes the run method to return once it is done executing so finished signal is emitted?

(sidenote, you can also use: the `finished` signal for inline code)

AFAIK that's why you are using PyQt5 and all the tutorials out there, right? I guess you are mostly cover on that front :P It's almost impossible to make beginner friendly tutorials to cover every single use case. Now it's QThread, tomorrow, for another user is QtSerialPort, maybe someone else want some tutorial on Creating custom widgets, etc, etc, etc. That's why all the tutorials out there you use for PyQt5, are written by the community. That's why, I encourage you to write tutorials of things you learn, otherwise, the same story repeats over and over.

True 👌, even pyqt lacks documentation(most are Stackoverflow questions and not actual tutorials)

I think so - the Qt docs say "QThreads begin executing in run(). By default, run() starts the event loop by calling exec() and runs a Qt event loop inside the thread.", so I suppose if you override run(), there's no event loop by default

fair enough, but then how do you solve the situations we already mentioned, lambda functions and partial)