@@ -766,7 +766,7 @@ def worker_function(*args, **kwargs):
766
766
############################################################################
767
767
768
768
# This is a variant on the above pattern, it uses QThread instead of Qrunnable
769
- # see https://doc.qt.io/qt-5 /threads-technologies.html#comparison-of-solutions
769
+ # see https://doc.qt.io/qt-6 /threads-technologies.html#comparison-of-solutions
770
770
# (it appears from that table that QRunnable cannot emit or receive signals,
771
771
# but we circumvent that here with our WorkerBase class that also inherits from
772
772
# QObject... providing signals/slots).
@@ -777,7 +777,7 @@ def worker_function(*args, **kwargs):
777
777
#
778
778
# However, a disadvantage is that you have no access to (and therefore less
779
779
# control over) the QThread itself. See for example all of the methods
780
- # provided on the QThread object: https://doc.qt.io/qt-5 /qthread.html
780
+ # provided on the QThread object: https://doc.qt.io/qt-6 /qthread.html
781
781
782
782
if TYPE_CHECKING :
783
783
@@ -808,7 +808,7 @@ def new_worker_qthread(
808
808
standard "single-threaded" signals & slots, note that inter-thread
809
809
signals and slots (automatically) use an event-based QueuedConnection, while
810
810
intra-thread signals use a DirectConnection. See [Signals and Slots Across
811
- Threads](https://doc.qt.io/qt-5 /threads-qobject.html#signals-and-slots-across-threads>)
811
+ Threads](https://doc.qt.io/qt-6 /threads-qobject.html#signals-and-slots-across-threads>)
812
812
813
813
Parameters
814
814
----------
0 commit comments