applied the patch generated by the optimize_connect script from

TT.

1 files changed, 2 insertions, 2 deletions

diff --git a/library/qcopenvelope_qws.cpp b/library/qcopenvelope_qws.cpp
index 8f58787..63efb13 100644
--- a/library/qcopenvelope_qws.cpp
+++ b/library/qcopenvelope_qws.cpp
@@ -59,26 +59,26 @@
 
   The \c{channelname} of channels within Qtopia all start with "QPE/".
   The \c{messagename} is a function identifier followed by a list of types
   in parentheses. There is no whitespace in the message name.
 
   To receive a message, you will generally just use your application's
   predefined QPE/Application/\e{appname} channel
   (see QPEApplication::appMessage()), but you can make another channel
   and connect it to a slot like this:
 
   \code
       myChannel = new QCopChannel( "QPE/FooBar", this );
-      connect( myChannel, SIGNAL(received(const QCString &, const QByteArray &)),
-               this, SLOT(fooBarMessage( const QCString &, const QByteArray &)) );
+      connect( myChannel, SIGNAL(received(const QCString&,const QByteArray&)),
+               this, SLOT(fooBarMessage(const QCString&,const QByteArray&)) );
   \endcode
 
   See also, the \link qcop.html list of Qtopia messages\endlink.
 */
 
 /*!
   Constructs a QCopEnvelope that will write \a message to \a channel.
   If \a message has parameters, you must then use operator<<() to
   add these parameters to the envelope.
 */
 QCopEnvelope::QCopEnvelope( const QCString& channel, const QCString& message ) :
     QDataStream(new QBuffer),