Use of longMessage (Was: extragear/multimedia/amarok/src)

[Seb Ruiz]

We only need to use longMessageThreadSafe when showing messages from  
within a thread (as if you didn't know that already :).  longMessage  
needs to stay because this method is called when an event is received.  
  See StatusBar::customEvent( QCustomEvent *e )

Seb

Quoting Jeff Mitchell <kde-dev at emailgoeshere.com>:

> Should we always be using longMessageThreadSafe as opposed to   
> longMessage?  If
> so, we should probably just remove longMessage; if not, when would we use one
> or the other?
>
> Thanks,
> Jeff
>
> On Monday 24 July 2006 01:50, Alexandre Pereira de Oliveira wrote:
>> SVN commit 565686 by aoliveira:
>>
>> Use longMessageThreadSafe in doJob's.
>>
>>
>>  M  +1 -1      scancontroller.cpp
>>
>>
>> --- trunk/extragear/multimedia/amarok/src/scancontroller.cpp #565685:565686
>> @@ -229,7 +229,7 @@
>>              CollectionDB::instance()->copyTempTables(); // copy temp into
>> permanent tables if( AmarokConfig::aTFJustTurnedOn() )
>>              {
>> -                amaroK::StatusBar::instance()->longMessage( i18n("ATF is
>> now enabled.  Enjoy!\n"), +
>> amaroK::StatusBar::instance()->longMessageThreadSafe( i18n("ATF is now
>> enabled.  Enjoy!\n"), KDE::StatusBar::Information );
>>
>>                  Playlist::instance()->clear();
> _______________________________________________
> Amarok mailing list
> Amarok at kde.org
> https://mail.kde.org/mailman/listinfo/amarok
>



-- 
http://www.sebruiz.net/