Re: [Interest] Klocwork error in Qt5 concurrentwrapper

2020-05-31 Thread Ramakanth Kesireddy
Thanks for your mail. Basically Klocwork categories the severity as error mentioning void function returns value under CODE VOIDRET pointing to the below function in qtconcurrentfunctionwrappers.h as the cause of error severity. Best Regards, Ramakanth On Sun, 31 May, 2020, 12:02 Thiago Macieira

Re: [Interest] QTimer::singleshot extending into global destruction phase

2020-05-31 Thread Thiago Macieira
On Sunday, 31 May 2020 12:48:31 PDT Thiago Macieira wrote: > This also removes the need for the event loop to be > involved. BTW, I'm not sure how your code could ever solve your problem. By the time the global destructors are being run, the event loop has shut down. No timers are being serviced

Re: [Interest] QTimer::singleshot extending into global destruction phase

2020-05-31 Thread Thiago Macieira
On Sunday, 31 May 2020 07:09:23 PDT René J.V. Bertin wrote: > Hi, > > I have an application with a lengthy shutdown procedure that's been known to > get stuck. So, I added > > static bool coreShuttingDown = true; > QTimer::singleShot(6, [&] { > if (coreShuttingDown

[Interest] QTimer::singleshot extending into global destruction phase

2020-05-31 Thread René J . V . Bertin
Hi, I have an application with a lengthy shutdown procedure that's been known to get stuck. So, I added static bool coreShuttingDown = true; QTimer::singleShot(6, [&] { if (coreShuttingDown) { // when our time is up, raise the SIGHUP signal that ca