title: Using processEvents() in Qt
body: <p>I am writing a small application in Qt (with PySide in Python), which makes extensive use of QGraphicsView and displays animations (sort of). There are a few buttons to start/stop/pause and a few other widgets. </p>
  
  <p>At first, I thought I should use QThread to handle the graphics and send signals to the main thread to QGraphicsScene etc., so I began implementing it. It worked, but I was not very satisfied with it - I tried a few different ways, but I think I overcomplicated it too much and the signal/slot mechanism and locking QMutexes was not even that fast.</p>
  
  <p>Then (I am new to PySide), I found the <code>processEvents()</code> method in the docs. I tried implementing it and it works just the way I want, it's fast and simple.
  Right now I am using it and everything is done on the main thread, and the GUI is responsive.</p>
  
  <p>My questions are: Is it wrong to use that method in that way? Should I just stick to QThreads?</p>
  
  <p>These questions are related to these...</p>
  
  <p><a href="https://stackoverflow.com/questions/1386043/how-to-make-qt-work-when-main-thread-is-busy">How to make Qt work when main thread is busy?</a></p>
  
  <p><a href="https://stackoverflow.com/questions/2150966/should-i-use-qcoreapplicationprocessevents-or-qapplicationprocessevents">Should I use QCoreApplication::processEvents() or QApplication::processEvents()?</a></p>
  
  <p>... where others say it should not be used.</p>