summaryrefslogtreecommitdiffhomepage
path: root/tracker-hatire/thread.hpp
AgeCommit message (Collapse)Author
2017-06-08tracker/hatire: fix breakageStanislaw Halik
Issue: #139
2017-05-24api/variance: move to compat/Stanislaw Halik
2016-11-05fix buildStanislaw Halik
2016-08-12all: rename modules s#^opentrack-##. and opentrack -> apiStanislaw Halik
Adjust usages.
2016-05-17tracker/hatire: move logger from headerStanislaw Halik
There's no need for the identifier to be exposed.
2016-05-15tracker/hatire: fix buildStanislaw Halik
2016-05-15tracker/hatire: remove unused unused macroStanislaw Halik
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: move to opentrack settings APIStanislaw Halik
2016-05-09tracker/hatire: remove min length check duplicationStanislaw Halik
The api callee already takes care of that so remove the "ok" argument.
2016-05-06tracker/hatire: add debug logging varianceStanislaw Halik
2016-05-06tracker/hatire: move function from headerStanislaw Halik
2016-05-06tracker/hatire: simplifyStanislaw Halik
We don't need to move back the datagram since we're processing the original.
2016-05-04tracker/hatire: try to optimize the polling pathStanislaw Halik
Issue: #327
2016-05-04tracker/hatire: remove raceStanislaw Halik
Don't prepend existing remaining data racing with add new data. Expose the lock as a public member.
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