ios: fix deploystep displayName updating

still uses the default deploystepconfiguration, which gives some
artifacts (to be fixed later)

Change-Id: I3f4f8a71fbe4e18fc171aee571da72da1c9735db
Reviewed-by: Tobias Hunger <tobias.hunger@digia.com>
This commit is contained in:
Fawzi Mohamed
2014-05-13 16:09:11 +02:00
parent f7a4e44764
commit e7ac3bf16e
3 changed files with 24 additions and 9 deletions

View File

@@ -46,6 +46,7 @@ IosDeployStepWidget::IosDeployStepWidget(IosDeployStep *step) :
m_step(step)
{
ui->setupUi(this);
connect(m_step, SIGNAL(displayNameChanged()), SIGNAL(updateSummary()));
}
IosDeployStepWidget::~IosDeployStepWidget()
@@ -55,8 +56,7 @@ IosDeployStepWidget::~IosDeployStepWidget()
QString IosDeployStepWidget::displayName() const
{
const QString deviceName = m_step->device().isNull() ? IosDevice::name() : m_step->device()->displayName();
return tr("<b>Deploy to %1</b>").arg(deviceName);
return QString::fromLatin1("<b>%1</b>").arg(m_step->displayName());
}
QString IosDeployStepWidget::summaryText() const