Skip to content
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

Add warning that DragEnter does not work unless Canvas Background is set #1490

Open
techfan101 opened this issue Aug 2, 2022 · 0 comments
Open
Assignees
Labels
doc-bug Problem with the content; needs to be fixed [org][type][category] dotnet-framework/svc okr-health Content-health KR: Concerns article defects/freshness or build warnings. okr-quality Pri3 Low priority 📌 seQUESTered Label to indicate an item has been imported. wpf/subsvc

Comments

@techfan101
Copy link

techfan101 commented Aug 2, 2022

Type of issue

Missing information

Description

For the most part, this page was very helpful and clearly written. However, there is one "gotcha" that can cause a huge headache for your readers.

It occurs with controls like the Canvas control. In addition to setting the AllowDrop property, it is also necessary to set the Background property. Otherwise, the Canvas is not recognized as a valid drop target, the "not allowed" cursor is displayed, and the DragEnter and Drop events never fire.

Adding a simple warning about the Background property could save developers a lot of time.

I recently spent an afternoon re-discovering this entirely non-obvious requirement. It would be great if you could help other developers avoid this time waste :) Thank you.

Page URL

https://learn.microsoft.com/en-us/dotnet/desktop/wpf/advanced/drag-and-drop-overview?view=netframeworkdesktop-4.8

Content source URL

https://github.com/dotnet/docs-desktop/blob/main/dotnet-desktop-guide/framework/wpf/advanced/drag-and-drop-overview.md

Document Version Independent Id

ca183356-078d-1538-1aa4-d3d7d604231b

Article author

@adegeo


Associated WorkItem - 341102

@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Aug 2, 2022
@PRMerger5 PRMerger5 added dotnet-framework/svc wpf/subsvc Pri1 High priority, do before Pri2 and Pri3 labels Aug 2, 2022
@techfan101 techfan101 changed the title Set Canvas Background Add warning that DragEnter does not work unless Canvas Background is set Aug 2, 2022
@adegeo adegeo added the doc-bug Problem with the content; needs to be fixed [org][type][category] label Sep 12, 2022
@dotnet-bot dotnet-bot removed the ⌚ Not Triaged Not triaged label Sep 12, 2022
@dotnet-policy-service dotnet-policy-service bot added the okr-health Content-health KR: Concerns article defects/freshness or build warnings. label Jan 19, 2024
@adegeo adegeo added the 🗺️ reQUEST Trigger label to import an issue into Quest label Nov 7, 2024
@adegeo adegeo self-assigned this Nov 7, 2024
@adegeo adegeo added Pri3 Low priority and removed Pri1 High priority, do before Pri2 and Pri3 labels Nov 7, 2024
@dotnetrepoman dotnetrepoman bot added 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. and removed 🗺️ mapQUEST Only used as a way to mark an issue as updated. RepoMan should instantly remove it. labels Nov 7, 2024
@sequestor sequestor bot added 📌 seQUESTered Label to indicate an item has been imported. and removed 🗺️ reQUEST Trigger label to import an issue into Quest labels Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-bug Problem with the content; needs to be fixed [org][type][category] dotnet-framework/svc okr-health Content-health KR: Concerns article defects/freshness or build warnings. okr-quality Pri3 Low priority 📌 seQUESTered Label to indicate an item has been imported. wpf/subsvc
Projects
Status: 🔖 Ready
Development

No branches or pull requests

4 participants