-
Notifications
You must be signed in to change notification settings - Fork 703
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DragUI.SetContentFromSoftwareBitmap() does not show the bitmap #4528
Comments
I observe the same problem with |
I believe @jschwizer99 is correct that this is the same as #4545. The comment I just added to that one:
In theory it is possible to avoid the issue if you can avoid any awaits (and taking a deferral) in your DragStarting handler. But that likely isn't reasonable for most uses to already have the bitmap ready. |
@codendone Will the window fix also be applied to older Windows versions? WinUI Desktop is supposed to work on older Windows versions as well. |
Backporting will be considered, but I can't guess whether it will be approved, or how far it might be backported. |
ProjectReunion 0.8.0-preview regresses even more. Even the default drag UI bitmap never shows up. This was working 1 out of 5 times in Reunion 0.5.7. Overriding the bitmap still does not work. And I still get random crashes while dragging: 0xC000027B: An application-internal exception has occurred |
The OS fix for this issue went live on Windows Update over the last month, so fully updated machines should no longer experience this issue. |
The problem is easily triggered when I use StartDragAsync . |
@codendone this seems to still be happening on windows 11 so it seems that the OS fix from a few years ago wasn't enough? |
When setting the drag bitmap in the DragStarting event handler, the bitmap is not displayed.
To set the bitmap, I use args.DragUI.SetContentFromSoftwareBitmap(...)
Steps to reproduce the bug
Expected behavior
The bitmap should be visible
Version Info
NuGet package version:
Microsoft.ProjectReunion 0.5.0-prerelease
The text was updated successfully, but these errors were encountered: