Commit 0fe5e93e authored by Rohit Yadav's avatar Rohit Yadav Committed by Hugo Beauzée-Luyssen

Print warning before a possible assertion failure. It was seen that this part...

Print warning before a possible assertion failure. It was seen that this part of code is reached when a possible assertion is failed. So, better print warning before quiting on an assertion failure.
Signed-off-by: 's avatarHugo Beauzée-Luyssen <beauze.h@gmail.com>
parent 3a48f94c
......@@ -73,8 +73,8 @@ SettingsManager::setValue( const QString &key,
return ;
}
}
Q_ASSERT_X( false, __FILE__, "set value without a created variable" );
qWarning() << "Setting" << key << "does not exist.";
Q_ASSERT_X( false, __FILE__, "set value without a created variable" );
}
SettingValue*
......@@ -95,8 +95,8 @@ SettingsManager::value( const QString &key,
if ( it != m_classicSettings.end() )
return (*it).value;
}
Q_ASSERT_X( false, __FILE__, "get value without a created variable" );
qWarning() << "Setting" << key << "does not exist.";
Q_ASSERT_X( false, __FILE__, "get value without a created variable" );
return NULL;
}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment