[V12] Drag'n'Drop Changes: Pressed vs Move

[LaurentInSeattle]

Context:

In my "world" of Drag and Drop, it only begins when there has been a bit of mouse (or finger) move, therefore once both a press and a significant move have been detected, Drag and Drop effectively starts. Sadly at this point, DoDragAndDrop now asks for a PointerPressedEventArgs. It used to be just PointerEventArgs in V12-rc1. And since the app is now dealing with PointerMove events, there is some trouble.

"My" (temporary?) Work-around:

The app saves the original PointerPressedEventArgs and pass it later to DoDragAndDrop. Timestamp is broken for sure, same for position, inaccurate since there has been a move, etc...

It seems to "work on my machine", but...

Questions:

Is it a valid solution?
If not, what should be done to handle correctly this (quite common) scenario?
Work-around only tested on Windows 10 x64. Will that even work on 11 ? Other platforms ?

Thanks!

[torum]

I'm also curious about this.

Relevant merged pull request (Change DoDragDropAsync trigger event to PointerPressedEventArgs): #20988