qtOperationLauncher fails in Single Thread mode
qtOperationLauncher.cxx needs to be updated to handle being set back into Single Thread mode. Attached is a patch for this.
`diff --git a/smtk/extension/qt/qtOperationLauncher.cxx b/smtk/extension/qt/qtOperationLauncher.cxx index f921ac7..40f030d 100644 --- a/smtk/extension/qt/qtOperationLauncher.cxx +++ b/smtk/extension/qt/qtOperationLauncher.cxx @@ -30,7 +30,7 @@ std::shared_ptr qtOperationLauncher::operator()(
// Access the promise's associated future before moving the promise onto the // subthread.
- std::futuresmtk::operation::Operation::Result future = promise.get_future();
-
std::shared_futuresmtk::operation::Operation::Result future = promise.get_future();
// Set the result handler's future handler->m_future = future; @@ -46,7 +46,7 @@ std::shared_ptr qtOperationLauncher::operator()( /// by the time this function returns. Passing a lamda to invokeMethod and /// using QueuedConnection will allow the emit to happen after the current /// path of execution.
- invokeMethod(
- QMetaObject::invokeMethod( this, handler, result { emit handler->resultReady(result); }, Qt::QueuedConnection);
#elseqtOpLaunch-future.patch`