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

Window.Current.Bounds contains more information about Position, not just Size #3319

Open
michael-hawker opened this issue Aug 26, 2021 · 0 comments
Assignees
Labels
design/tech doc-enhancement feedback is about suggested additions/improvements to the article, but customer is not blocked Pri2 uwp/prod

Comments

@michael-hawker
Copy link
Contributor

In the Make code portable across windowing hosts table, the guidance for CoreWindow.GetForCurrentThread().Bounds and Window.Current.Bounds is to use uiElement.XamlRoot.Size. That's fine if you're just trying to get the size of the window; however, Bounds also contained the X,Y position on screen.

More guidance should be provided here on how to retrieve the coordinates properly when hosted in scenarios with multiple window potential. i.e. translating this scenario

FYI @marb2000

Linkback: CommunityToolkit/WindowsCommunityToolkit#3650


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@hkhmsft hkhmsft added the doc-enhancement feedback is about suggested additions/improvements to the article, but customer is not blocked label Sep 17, 2021
@PRMerger5 PRMerger5 added the Pri2 label Dec 1, 2021
learn-build-service-prod bot added a commit that referenced this issue Mar 1, 2023
…c_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design/tech doc-enhancement feedback is about suggested additions/improvements to the article, but customer is not blocked Pri2 uwp/prod
Projects
None yet
Development

No branches or pull requests

5 participants