void AMControlMoveAction::cancelImplementation()
{
// either don't have a control, or called prior to startImplementation(). Nothing to do except report cancelled.
if(!control_) {
notifyCancelled();
return;
}
/// \todo Question: what about controls that cannot stop? Do we need to wait for them to finish their full move before notifying that we've cancelled? [And in that case... What about mis-behaving controls that never report being done? Should they be able to block the whole action system by never cancelling? Do we need another action instruction for "abort()", which moves on from actions that have ignored their instruction to cancel()?]
if(!control_->stop()) {
AMErrorMon::report(AMErrorReport(this, AMErrorReport::Alert, -5, QString("Could not stop the control '%1' because it doesn't support stopping in mid-motion. This action has been cancelled, but be careful because the machine could still be moving.").arg(control_->name())));
}
// for now, cancel the action as long as we've sent the 'stop' request. This is an open question for debate.
notifyCancelled();
}
void
FileReadThread::run()
{
MutexLocker locker(&m_mutex, "FileReadThread::run::m_mutex");
while (!m_exiting) {
if (m_queue.empty()) {
m_condition.wait(&m_mutex, 1000);
} else {
process();
}
notifyCancelled();
}
notifyCancelled();
#ifdef DEBUG_FILE_READ_THREAD
std::cerr << "FileReadThread::run() exiting" << std::endl;
#endif
}
