Give a feeback about the progress of the filter process

when applying an ad-hoc filter via Message->Apply Filter to
many, many messages.
Now you can guess when your KMail will be back to normal work.

svn path=/trunk/KDE/kdepim/; revision=483598

kmcommands.cpp

@@ -1470,7 +1470,11 @@ KMCommand::Result KMFilterActionCommand::execute()
     if( msg->parent() )
       kmkernel->filterMgr()->tempOpenFolder(msg->parent());
 
+  int msgCount = 0;
   for (KMMessage *msg = msgList.first(); msg; msg = msgList.next()) {
+    QString statusMsg = i18n("Filtering message %1 of %2");
+    statusMsg = statusMsg.arg( ++msgCount ).arg( msgList.count() );
+    KPIM::BroadcastStatus::instance()->setStatusMsg( statusMsg );
     msg->setTransferInProgress(false);
 
     int filterResult = kmkernel->filterMgr()->process(msg, mFilter);

kmfilteraction.cpp

@@ -1,7 +1,4 @@
 // kmfilteraction.cpp
-// The process methods really should use an enum instead of an int
-// -1 -> status unchanged, 0 -> success, 1 -> failure, 2-> critical failure
-// (GoOn),                 (Ok),         (ErrorButGoOn), (CriticalError)
 
 #ifdef HAVE_CONFIG_H
 #include <config.h>

kmfilteraction.h

@@ -151,7 +151,7 @@ public:
   /** Automates the sending of MDNs from filter actions. */
   static void sendMDN( KMMessage * msg, KMime::MDN::DispositionType d,
 		       const Q3ValueList<KMime::MDN::DispositionModifier> & m
-		       =Q3ValueList<KMime::MDN::DispositionModifier>() );
+		       = Q3ValueList<KMime::MDN::DispositionModifier>() );
 
 private:
   QString mName;