title: QObject based class has a queued connection to itself
body: <p>I was digging into some source code I am working on. I found a peculiar statement that someone had coded. The source code is a GUI application with a QML GUI and uses QT 4.7.x.</p>
  
  <p>The snippet below belongs to core application logic.</p>
  
  <pre><code>// connect signal-slots for decoupling
  QObject::connect (this, SIGNAL(setCurrentTaskSignal(int)), this, 
      SLOT(SetCurrentTaskSlot(int)), Qt::QueuedConnection);
  </code></pre>
  
  <p>It's strange that the object connects to itself via a queued connection which essentially means that the object may "live" in different threads at the same time?</p>
  
  <p>At first glance It didn't made any sense to me. Can anyone think of any reason why such a connection would be plausible or needed?. Would this even work?</p>