Edouard Griffiths

This is a one way communication and how REST APIs work and one has to live with it.

Since this is a message queue the requests are processed one after the other so I don't see the need of such a complex setup.

So the issue is only with PATCH since with PUT all fields of the settings are updated anyway so the latest that comes in is right and that's the rule....

Full diff for Airspy airspygui.cpp ```diff diff --git a/plugins/samplesource/airspy/airspygui.cpp b/plugins/samplesource/airspy/airspygui.cpp index d45c0b8f6..5e3e983b7 100644 --- a/plugins/samplesource/airspy/airspygui.cpp +++ b/plugins/samplesource/airspy/airspygui.cpp @@ -87,6 +87,7 @@ void AirspyGui::resetToDefaults() { m_settings.resetToDefaults(); displaySettings(); + m_forceSettings = true;...

Full diff for AFC feature afc.cpp ```diff diff --git a/plugins/feature/afc/afc.cpp b/plugins/feature/afc/afc.cpp index ba4c6097f..57bc499cf 100644 --- a/plugins/feature/afc/afc.cpp +++ b/plugins/feature/afc/afc.cpp @@ -118,7 +118,7 @@ void AFC::start() m_worker->setMessageQueueToGUI(getMessageQueueToGUI()); m_thread->start(); - AFCWorker::MsgConfigureAFCWorker *msg =...

@mistergitj indeed your description is too vague and discourages me to continue developing this software

I have a Airspy mini and it does crash on close with the previous revision. Let's wait for the build... No need to wait in fact. and... it does fix...

This is incompatibility with the latest version of libmirisdr-4 and will be fixed by PR #1344

Obviously gcc on Linux does not care if you set it to c++14 so some later constructs passed through. Edit: `clang-tidy` may help with this (and more...) as it defaults...

So why does it work for all other "xxx_EXPORTS"?