Bug 304180

Summary: strange behavior when using drag and drop
Product: [Unmaintained] Necessitas Reporter: Marco Bernasocchi <marco>
Component: Android Qt4Assignee: BogDan Vatra <bogdan>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist CC: OUSSAMA.MLIKA
Priority: NOR    
Version First Reported In: alpha3   
Target Milestone: ---   
Platform: Android   
OS: Unspecified   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Marco Bernasocchi 2012-07-28 15:32:42 UTC
When using drag and drop, the screen goes black and it has a very strange behavior, I used dragdroprobot example to reproduce it.
https://sourceforge.net/p/necessitas/tickets/12/
Comment 1 OKTODEV 2012-11-25 19:56:54 UTC
I am porting a complex QT desktop application to android and faced the same drag and drop issue. I spent some time investigating the cause and would like to share what I found in order to help. 
In the QT documentation there is a note about drag and drop implementation and the event loop. 
Note: On Linux and Mac OS X, the drag and drop operation can take some time, but this function does not block the event loop. Other events are still delivered to the application while the operation is performed. On Windows, the Qt event loop is blocked while during the operation.

I think the gui is not painted during the drag operation due to paint event not processed. 
Looking at the QT source code I can see that the QDropManager implementation is platform dependent. You can see  src/gui/kernel/kernel.pri, where qdnd_XXX.cpp is different for X11, Win , Symbian and MacOs. 

In the ALPHA 4 necessitas kernel.pri, I was not able to see an android dependent qdnd_XXX.cpp.

I am not sure which one is used for the android build. I will try the X11 version and see if it solves the problem.
One quick way to reproduce the problem is to try any drag and drop QT example 
draganddrop/draggableicons
Comment 2 Andrew Crouthamel 2018-09-04 16:15:55 UTC
Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years and I will be closing this bug.