I mean the function being run in a separate thread using Qtconcurrent::run
is auto deleted from QThreadpool?
On Mon, 30 Dec, 2019, 05:52 Thiago Macieira,
wrote:
> On Saturday, 28 December 2019 08:21:39 -03 Ramakanth Kesireddy wrote:
> > Whether the thread created using Qtconcurrent::run returnin
On Saturday, 28 December 2019 08:21:39 -03 Ramakanth Kesireddy wrote:
> Whether the thread created using Qtconcurrent::run returning QFuture(status
> monitored using QFutureWatcher) needs to be deleted explicitly by the
> application or it is auto deleted when there are no references?
QtConcurren
On Sunday, 29 December 2019 13:47:23 -03 Narolewski Jakub wrote:
> Now, I have to do some fun optimization to not recreate libUV's poll
> handlers every time notifier gets unregistered and actually destroy them
> when they are not needed anymore, hmm.
The better way would be to have a new virtual
Answering my own question - QSocketNotifier gets unregistered in the event
dispatcher every time QSocketNotifier::setEnabled(false) is called.
Additionally, QSocketNotifier::setEnabled(false) is called after every
write event on the descriptor. As I was sending data 20 times per second
throught my
Hello,
Under Windows, you should use SetThreadExecutionState instead.
On 12/29/2019 5:41 PM, Kevin André wrote:
Hi,
I'm developing a FOSS music player (using Qt Widgets), and when I run
it on my company laptop, after about 15 minutes of user inactivity
(not touching the keyboard or mouse) the
Hi,
I'm developing a FOSS music player (using Qt Widgets), and when I run
it on my company laptop, after about 15 minutes of user inactivity
(not touching the keyboard or mouse) the screen turns off and the
Windows session is locked. But I've checked the screensaver setting,
and screensaver is dis
