summaryrefslogtreecommitdiffhomepage
path: root/proto-simconnect
AgeCommit message (Collapse)Author
2018-04-05i18n: update stringsStanislaw Halik
2018-04-05modules: now use i18nStanislaw Halik
2018-03-16proto/simconnect: fix MSVC activation contextStanislaw Halik
Issue: #760
2018-02-12cmake: add zh_CNStanislaw Halik
cf. #746
2018-02-12modules: stop saving line informationStanislaw Halik
Now i18n regen won't make a mess.
2018-02-12proto/simconnect: fix i18n warningStanislaw Halik
2018-02-09update translation source files -- #743Stanislaw Halik
2018-01-20rename our Qt .png iconStanislaw Halik
facetracknoir.png -> opentrack.png
2018-01-18compat/util: retireStanislaw Halik
Adjust usages.
2018-01-04main: workaround crash on exit without terminating processStanislaw Halik
2017-12-26compat: use gettext convention for tr()Stanislaw Halik
2017-12-18plugins: rename check_status -> initializeStanislaw Halik
It's a contract for plugin invocation that the particular function fills the role of initialization. Rename accordingly.
2017-12-09many: use otr_tr for non-qobject translationStanislaw Halik
I haven't even compile-tested Linux and OSX-specific bits.
2017-12-04api: add status check for modulesStanislaw Halik
2017-10-29static constexpr -> constexprStanislaw Halik
2017-08-14some style fixesStanislaw Halik
2017-07-07proto/simconnect: fix WinSxS library versionsStanislaw Halik
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.
2017-07-06proto/simconnect: add version list for referenceStanislaw Halik
Our manifests are out of what. This'll help. Provided-by: @ronh991 in <https://github.com/opentrack/opentrack/issues/627#issuecomment-311714551>
2017-06-18get rid of "volatile" abuseStanislaw Halik
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.
2017-06-07proto/simconnect: adjust debug messagesStanislaw Halik
2017-04-07rename several protocols from abbreviated namesStanislaw Halik