The lambda in your example forms a closure. That is, it is a nested function that references objects available in its enclosing scope. Every function that creates a closure keeps a cell object for every item it needs to maintain a reference to. In your example, the lambda creates a closure with references to the … Read more
There are quite a few problems with your code : like said by Evan the emit keyword is missing all your objects live in the main thread, only the code in the run methods live in other threads, which means that the MySlot slot would be called in the main thread and I’m not sure … Read more
You should use Connections in this case (maybe it’s the only way to connect). Put your object myObj to QML file by setContextProperty qmlVectorForm->rootContext()->setContextProperty(“YourObject”, myOb); Your signal is finishedGatheringDataForItem(QString signalString) In QML file, add Connectios likes below: Connections { target: YourObject onFinishedGatheringDataForItem: { qmlString = signalString } }
This is just, how scoping, name lookup and closures are defined in Python. Python only introduces new bindings in namespace through assignment and through parameter lists of functions. i is therefore not actually defined in the namespace of the lambda, but in the namespace of __init__(). The name lookup for i in the lambda consequently … Read more
There are some rules that make life with signals and slots easier and cover the most common reason for defective connections. If I forgot something please tell me. 1) Check the debug console output: When execution errors occur, the debug output can show you the reason. 2) Use the full signature of signal and slot: … Read more
It shouldn’t matter whether the connection is made before or after moving the worker object to the other thread. To quote from the Qt docs: Qt::AutoConnection – If the signal is emitted from a different thread than the receiving object, the signal is queued, behaving as Qt::QueuedConnection. Otherwise, the slot is invoked directly, behaving as … Read more