Bug 12843 - DragMotion event not fired on windows
Summary: DragMotion event not fired on windows
Status: RESOLVED DUPLICATE of bug 16359
Alias: None
Product: Gtk#
Classification: Mono
Component: gtk-sharp ()
Version: 2.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-06-24 03:32 UTC by Sven
Modified: 2013-12-05 15:04 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
MainWindow with DragMotion handler (85.24 KB, application/octet-stream)
2013-06-30 13:26 UTC, Sven
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED DUPLICATE of bug 16359

Description Sven 2013-06-24 03:32:38 UTC
DragMotion is not fired on windows, but on linux.

How to reproduce:
1. Add DragMotionEventHandler to window
2. Drag a file to window
3. On linux, DragMotion gets fired, on windows not
Comment 1 Sven 2013-06-26 04:08:47 UTC
Also DragBegin is not fired. Is there a general problem with drag & drop on windows?
Comment 2 Sven 2013-06-30 13:26:42 UTC
Created attachment 4238 [details]
MainWindow with DragMotion handler
Comment 3 Cody Russell 2013-12-05 15:04:40 UTC

*** This bug has been marked as a duplicate of bug 16359 ***