You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using UWP but the equivalent exists in WindowsAppSDK (needs checking).
If I call DragUI.SetContentFromDataPackage() on drag starting, and I have set the data package contents to a bitmap which isn't valid (probably even can set a valid image of some type but which Windows can't decode), then on DragOver (if drop allowed and accepted) the app will crash. There's no way to catch the error (except perhaps in the unhandled exception handler). I haven't tested it but I imagine this might crash another app if dragging between apps (not actually sure which app will crash in that case). This should not result in a crash. It should simply either show a generic image icon or just the drag cursor or whatever is appropriate, there is no need to crash, and one can't always easily verify that the bitmap data set in the data package is something that can be decoded by Windows.
The text was updated successfully, but these errors were encountered:
I'm using UWP but the equivalent exists in WindowsAppSDK (needs checking).
If I call
DragUI.SetContentFromDataPackage()
on drag starting, and I have set the data package contents to a bitmap which isn't valid (probably even can set a valid image of some type but which Windows can't decode), then on DragOver (if drop allowed and accepted) the app will crash. There's no way to catch the error (except perhaps in the unhandled exception handler). I haven't tested it but I imagine this might crash another app if dragging between apps (not actually sure which app will crash in that case). This should not result in a crash. It should simply either show a generic image icon or just the drag cursor or whatever is appropriate, there is no need to crash, and one can't always easily verify that the bitmap data set in the data package is something that can be decoded by Windows.The text was updated successfully, but these errors were encountered: