forked from qt-creator/qt-creator
Debugger: Add new debuggers from option page
The asserts should be moved from the addDebugger() method which is called to add an 'empty' debugger when adding new one from the option page. Change-Id: Ic402db514d1e97f5fdc12d9bb9070bf29b2ab354 Reviewed-by: Friedemann Kleint <Friedemann.Kleint@digia.com> Reviewed-by: hjk <hjk121@nokiamail.com>
This commit is contained in:
@@ -647,6 +647,9 @@ void DebuggerItemManager::saveDebuggers()
|
||||
|
||||
QVariant DebuggerItemManager::registerDebugger(const DebuggerItem &item)
|
||||
{
|
||||
QTC_ASSERT(!item.command().isEmpty(), return QVariant());
|
||||
QTC_ASSERT(!item.displayName().isEmpty(), return QVariant());
|
||||
QTC_ASSERT(item.engineType() != NoEngineType, return QVariant());
|
||||
if (findByCommand(item.command()))
|
||||
return item.id();
|
||||
|
||||
@@ -661,9 +664,6 @@ void DebuggerItemManager::deregisterDebugger(const DebuggerItem &item)
|
||||
|
||||
QVariant DebuggerItemManager::addDebugger(const DebuggerItem &item)
|
||||
{
|
||||
QTC_ASSERT(!item.command().isEmpty(), return QVariant());
|
||||
QTC_ASSERT(!item.displayName().isEmpty(), return QVariant());
|
||||
QTC_ASSERT(item.engineType() != NoEngineType, return QVariant());
|
||||
QTC_ASSERT(item.id().isValid(), return QVariant());
|
||||
m_debuggers.append(item);
|
||||
m_model->addDebugger(item);
|
||||
|
||||
Reference in New Issue
Block a user