diff options
Diffstat (limited to 'kopete/kopete/config/accounts/kopeteaccountconfig.cpp')
-rw-r--r-- | kopete/kopete/config/accounts/kopeteaccountconfig.cpp | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/kopete/kopete/config/accounts/kopeteaccountconfig.cpp b/kopete/kopete/config/accounts/kopeteaccountconfig.cpp index feaa88fd..356f0528 100644 --- a/kopete/kopete/config/accounts/kopeteaccountconfig.cpp +++ b/kopete/kopete/config/accounts/kopeteaccountconfig.cpp @@ -53,8 +53,8 @@ class KopeteAccountLVI : public KListViewItem typedef KGenericFactory<KopeteAccountConfig, TQWidget> KopeteAccountConfigFactory; K_EXPORT_COMPONENT_FACTORY( kcm_kopete_accountconfig, KopeteAccountConfigFactory( "kcm_kopete_accountconfig" ) ) -KopeteAccountConfig::KopeteAccountConfig( TQWidget *parent, const char * /* name */, const TQStringList &args ) -: KCModule( KopeteAccountConfigFactory::instance(), parent, args ) +KopeteAccountConfig::KopeteAccountConfig( TQWidget *tqparent, const char * /* name */, const TQStringList &args ) +: KCModule( KopeteAccountConfigFactory::instance(), tqparent, args ) { ( new TQVBoxLayout( this ) )->setAutoAdd( true ); @@ -136,7 +136,7 @@ void KopeteAccountConfig::slotItemSelected() m_view->mButtonDown->setEnabled( itemSelected->itemBelow() ); Kopete::Account *account = itemSelected->account(); - TQColor color= m_newColors.contains(account) ? m_newColors[account] : account->color(); + TQColor color= m_newColors.tqcontains(account) ? m_newColors[account] : account->color(); m_view->mUseColor->setEnabled( true ); m_view->mUseColor->setChecked( color.isValid() ); m_view->mColorButton->setColor( color ); @@ -201,7 +201,7 @@ void KopeteAccountConfig::slotEditAccount() if ( !m_accountWidget ) return; - // FIXME: Why the #### is EditAccountWidget not a QWidget?!? This sideways casting + // FIXME: Why the #### is EditAccountWidget not a TQWidget?!? This sideways casting // is braindead and error-prone. Looking at MSN the only reason I can see is // because it allows direct subclassing of designer widgets. But what is // wrong with embedding the designer widget in an empty TQWidget instead? @@ -231,7 +231,7 @@ void KopeteAccountConfig::slotRemoveAccount() return; Kopete::Account *i = lvi->account(); - if ( KMessageBox::warningContinueCancel( this, i18n( "Are you sure you want to remove the account \"%1\"?" ).arg( i->accountLabel() ), + if ( KMessageBox::warningContinueCancel( this, i18n( "Are you sure you want to remove the account \"%1\"?" ).tqarg( i->accountLabel() ), i18n( "Remove Account" ), KGuiItem(i18n( "Remove Account" ), "editdelete"), "askRemoveAccount", KMessageBox::Notify | KMessageBox::Dangerous ) == KMessageBox::Continue ) { |