summaryrefslogtreecommitdiffhomepage
path: root/tracker-hatire/ftnoir_tracker_hat.h
AgeCommit message (Collapse)Author
2018-12-24cmake: decruft, disable deprecated Qt functionsStanislaw Halik
2018-08-27tracker/hatire: appease clang analyzerStanislaw Halik
2018-06-26modernize C++ syntaxStanislaw Halik
No visible changes (hopefully).
2018-04-05modules: now use i18nStanislaw Halik
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-06-22misc irrelevantStanislaw Halik
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-04-17tracker/hatire: include right headerStanislaw Halik
2016-11-05modules: make more strings translatableStanislaw Halik
2016-11-04modules: make names uniqueStanislaw Halik
2016-08-12all: rename modules s#^opentrack-##. and opentrack -> apiStanislaw Halik
Adjust usages.
2016-05-15many: remove executable bit from source filesStanislaw Halik
We no longer have this recurring problem since I enabled ignoring executable bit changes on the Windows workstation.
2016-05-09tracker/{hatire,rift-080}: remove outdated commentsStanislaw Halik
2016-05-09tracker/hatire: move to opentrack settings APIStanislaw Halik
2016-05-04tracker/hatire: remove disconnected logicStanislaw Halik
It's not used anywhere.
2016-05-04tracker/hatire: fix spelling in identifiersStanislaw Halik
2016-04-29tracker/hatire: move io to a separate threadStanislaw Halik
We can't have async io on the main thread because QSerialPort's readyRead() signal can fire constantly, thus consuming all CPU time. We can't sleep in the main thread either as that blocks too many things. We can't ignore readyRead() invocations over a threshold as that'll make us lose some of data notifications. Refactor hatire to put IO on a thread. Since this is a separate Qt event loop, we may sleep in there. Further, add a debug mode reading data from a file, as if it came from a serial-attached device. Issue: #327
2015-10-30move to subdirectory-based build systemStanislaw Halik
Closes #224