Age | Commit message (Collapse) | Author |
|
|
|
|
|
We heavily used "volatile bool" to check if the thread
loop should stop. But this functionality is already
provided by Qt5's QThread::requestInterruption.
In other cases, "volatile" is wonderfully
underspecified so it's better to ditch its usage in
favor of std::atomic<t>. At the time we don't appear to
be using the "volatile" keyword except when calling
win32's Interlocked*() family of functions as
necessary.
In freetrackclient's header the "volatile" qualifier
was used as part of a typedef. This doesn't work. Use
it as part of data declaration.
|
|
|
|
|
|
|
|
|
|
Reported-by: @Sone989
Issue: #440
|
|
|
|
Reported-by: @MathijsG
Issue: #434
|
|
|
|
It was easiest to reproduce when a protocol failed to load. As usual, win32
debugging without MSVC++ is nearly useless.
|
|
Adjust usages.
|