title: Slow repaint underneath dragged object on X... Can Qt force drag and drop operations to be internal only?
body: <p>I'm implementing <strong>Qt</strong>'s drag and drop API across <strong>Windows</strong> and <strong>X</strong>. When I pick up an object in the app running on <strong>X</strong> and drag it, it leaves a white ghost trail of itself on the window underneath, as if the window underneath is being slow to repaint where the dragged object was previously obscuring part of itself.</p>
  
  <p>I believe that this is symptomatic of the same problem that Qt has just solved with <a href="http://labs.qt.nokia.com/2007/08/09/qt-invaded-by-aliens-the-end-of-all-flicker/" rel="nofollow">resizing windows causing flicker in child widgets on X windows</a> - <strong>i.e. the dragged object is treated as a separate native window and therefore X handles the clipping from the dragged object to the window underneath.</strong> Since <strong>X</strong> does this in a different way to <strong>Qt</strong>, we get the ghosting effect.</p>
  
  <p>Has anyone experienced the same problems? One solution that comes to mind is to use the same technique as detailed in the blog article linked above and stop the dragged object being treated as a native window, presumably at the cost of drag and drop being limited to my application only (I have no problem with this). Would anyone know how to force drag and drop operations to be internal only?</p>
  
  <hr>
  
  <p><strong>EDIT:</strong> I'm using <code>QDrag::setPixmap</code> to set the graphical representation of the dragged object - it is important that I retain this in favour of a standard drag cursor as this interface is being used on a touchscreen device and will hence have no visible cursor.</p>