On Friday, 22 September 2023 15:48:53 PDT Stefan Seefeld wrote:
> I'm not sure what "at the same time" means. At least in my sample code, I'm
> really calling the `quit()` function from a different thread (while the
> event loop is still running, of course), and am only destroying the
> application
Hi Jeremy,
thank you very much for following up !
On Fri, Sep 22, 2023 at 6:36 PM Jeremy Katz wrote:
>
> I went searching for Qt 6 references to QCoreApplication.quit, as this
> has changed from Qt 5. Qt 5 makes no promises.
> https://doc.qt.io/qt-6/qcoreapplication.html#quit says:
> Thread-saf
Hi Jeremy,
thanks for the quick reply !
On Fri, Sep 22, 2023 at 1:16 PM Jeremy Katz wrote:
>
> On 9/22/23 09:35, Stefan Seefeld wrote:
>
> > 1. run the above command, but click the "quit" button immediately. Thus
> > results in the error message `QObject::killTimer: Timers cannot be
> > stopped
On Fri, 22 Sept 2023 at 18:36, Stefan Seefeld wrote:
> Hello,
>
> I'm trying to establish a Python test methodology whereby a QApplication
> is launched (and its event loop executed) in a secondary thread, while the
> primary thread performs some "test scenario".
>
QApplication.exec must be call
Hello,
I'm trying to establish a Python test methodology whereby a QApplication is
launched (and its event loop executed) in a secondary thread, while the
primary thread performs some "test scenario".
Summary: I'm unable to set this up, and it isn't clear why this isn't
working.
Details: please c
