Non ItemsControls use PreviewEvents instead of Bubbeling-Event-Version

[rubenwe]

As already pointed out in #180, #159 and others:
The "wrong" events are used - this breaks the order in which the handlers should be called.

Example:
In my case the window handles a drop event for a "project" file,
while the nested project file view handles source files of the project.
Those source files will either NOT be rejected if I set dropInfo.NotHandled=true
(application does not show a rejecting symbol) or the inner controls handler will not be called.

This is not expected behavior for a bubbling event like DragOver.

DragDrop.Properties.cs / IsDropTargetChanged mentions this was changed for issue #85.

If I comment out the distinction between ItemsControls and others, the app works as expected.
But I don't know what else I might be breaking by doing so.

Would love to see this fixed. Thanks for all the hard work 👍

[smnrock]

Any update on this issue? Is it safe to comment out tunnelling evens and use bubbling events for all the controls inside IsDropTargetChanged()?

[rubenwe]

I didn't run into scenarios where this led to problems, but I didn't do that much... so you might just want to try it out for your project and see if it solves the issues you have.

In the end we could use some input from @punker76 on why this was changed in the first place.

@smnrock: Let me/us know if you find something strage after you make the change.

[smnrock]

@rubenwe After commenting out the difference, now #85 issue is back(as expected). ie., Dropping to textbox will not work. For now, i've modified like, If uielement is TextBoxBase, then use tunneling events else use bubbling events.

[punker76]

@rubenwe It's now possible to force which event should be used #300 thx to @Chri-s

[rubenwe]

Thanks for implementing and integrating the changes guys - I will have a look once 2.0.0 drops. This is a much appreciated addition :)