| Age | Commit message (Collapse) | Author |
|---|
|
reducing jitter and reduce the simconnect thread to keepalive work
|
|
Issue: #975
|
|
Issue: #804
- don't call simconnect_close without a valid handle
- remove magic numbers
- fix event handle logic. only use it for checking
whether we're timing out.
- add more informative stderr output
- don't hardcode QFunctionPointer type alias
- remove awful VirtPos/Rot...
|
|
|
|
|
|
Issue: #804
|
|
|
|
Maybe global `-Wcomma' is too harsh.
There should be no functional changes whatsoever.
|
|
No visible changes (hopefully).
|
|
|
|
|
|
It's a contract for plugin invocation that the particular function fills
the role of initialization. Rename accordingly.
|
|
I haven't even compile-tested Linux and OSX-specific bits.
|
|
|
|
We had all the wrong versions assigned to comboboxen.
With the correct versions, Prepar3D works with its own
SimConnect redist named "SP2-XPACK". The library
version is the same as SP2 and the combobox item exists
only to help users.
|
|
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.
|
|
|
|
|
