BeginMoveDrag - operation is done in dispatcher

[KrzysztofDusko]

Hello.
In this PR #14190 BeginMoveDrag action was moved to dispatcher.Post instead direct execution. This changind beharior in way that after call BeginMoveDrag cotrol is immediatyly returen to caller..
Sample real word issue wieslawsoltes/Dock#319

[kekekeks]

IIRC it's made for consistency with non-windows platforms where we the underlying platform doesn't introduce a nested event loop and doesn't send us "drag complete" notifications.

[KrzysztofDusko]

OK. But this introduce behavior change this is accepted in 11.1 ?

[timunie]

Crazy idea, would an async overload help you which is a Task? You could await it and then continue.

[kekekeks]

It's a bug fix, since platforms were behaving inconsistently.
Such changes are acceptable for x.y.0 releases

[kekekeks]

would an async overload help you which is a Task?

We can't have one for non-windows platforms, unfortunately.

[maxkatz6]

OK. But this introduce behavior change this is accepted in 11.1 ?

It's not a behavior change in general, since this behavior always existed on other platforms. We still might want to introduce another API that works better. BeginResizeDrag/BeginMoveDrag copied from WPF are just broken (even on Windows, when touch comes to action).

In general, I always was of opinion of adding some attached property like Window.DecorationType="Titlebar" API (with other options like ResizeGrip and Minimize button), where platform would do visuals hit test (which we already do), and depending on attached property value it would start relevant operation associating with the pointer.

[KrzysztofDusko]

thanks for the answers.