Ref T566, configurable matching log in matcher/simulator components

* log flag/enum in own file
* pass "what to log" as parameter
This commit is contained in:
Klaus Basan
2019-04-08 03:08:02 +02:00
committed by Mat Sutcliffe
parent 991c7d59ef
commit 0d2e6dd997
8 changed files with 43 additions and 97 deletions

View File

@@ -307,12 +307,14 @@ namespace BlackCore
return m_dBusInterface->callDBusRet<BlackMisc::CStatusMessageList>(QLatin1String("getMatchingMessages"), callsign);
}
bool CContextSimulatorProxy::isMatchingMessagesEnabled() const
MatchingLog CContextSimulatorProxy::isMatchingMessagesEnabled() const
{
return m_dBusInterface->callDBusRet<bool>(QLatin1String("isMatchingMessagesEnabled"));
//! \fixme KB 2019-04 directly return MatchingLog causes issues with QDbusArgument
const int r = m_dBusInterface->callDBusRet<int>(QLatin1String("isMatchingMessagesEnabled"));
return static_cast<MatchingLog>(r);
}
void CContextSimulatorProxy::enableMatchingMessages(bool enabled)
void CContextSimulatorProxy::enableMatchingMessages(MatchingLog enabled)
{
m_dBusInterface->callDBus(QLatin1String("enableMatchingMessages"), enabled);
}