Todo List

Member TEST (selftest, brickCheck)

: it shall not be here, use asynchronous initialization instead.

Member trikControl::AbstractVirtualSensorWorker::stop ()

Correctly stop starting sensor.

Member trikControl::Battery::readVoltage () override

: Remove these arcane numbers, or Something may be unexpectedly summoned by them.

Member trikControl::Brick::reset () override

Temporary, we need more carefully init/deinit range sensors.

Member trikControl::Brick::stop () override

: Also be able to stop initializing sensor.

Member trikControl::LineSensor::stop () override

Correctly stop starting sensor.

Member trikControl::ObjectSensor::stop () override

Correctly stop starting sensors.

Member trikControl::SoundSensorWorker::detect ()

???

Member trikControl::VectorSensorWorker::read ()

: vector copying is not atomic, so we may receive evSyn right in the middle of "return mReading".

Member trikGui::AutoRunner::AutoRunner (Controller &controller)

Make underlying components emit signal when they are ready for script execution.

Member trikNetwork::TrikServer::startConnection (Connection *connectionWorker)

: Emit "connected" signal only when socket is actually connected.

Member trikScriptRunner::PythonEngineWorker::stopScript ()

: is it actually stopped?

Member trikScriptRunner::ScriptEngineWorker::stopScript ()

: here script will continue to execute and may execute some statements before it will eventually be stopped by mThreading.reset(). But if we do mThreading.reset() before mMailbox->stopWaiting(), we will get deadlock, since mMailbox->stopWaiting() shall be executed in already stopped thread. Actually we shall stop script engines here, do mMailbox->stopWaiting(), then stop threads.

: is it actually stopped?