SystemParameters.xml: corrects MenuDropAlignment #6780
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I believe this to be a documentation bug related to incorrect default values shipped in Windows Server at least versions 2012-2016. (Basically, if you took a fresh Windows Server install in a typical US localization and set up Remote Desktop Services, the menus inside RDS would all be right-aligned, which is opposite to how consumer systems typically ship in the US.) This is a one-word change which is confirmed by observed behavior when setting the HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\MenuDropAlignment key to 0 (false, left-aligned) vs 1 (true, right-aligned). This is also supported by the SystemParametersInfo documentation linked in Remarks.
dotnet-issue-labeler
bot
added
the
area-WPF
|
Docs Build status updates of commit 9303a4c: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
I believe this to be a documentation bug related to incorrect default values shipped in Windows Server at least versions 2012-2016. (Basically, if you took a fresh Windows Server install in a typical US localization and set up Remote Desktop Services, the menus inside RDS would all be right-aligned, which is opposite to how consumer systems typically ship in the US.)
This is a one-word change which is confirmed by observed behavior when setting the HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\MenuDropAlignment key to 0 (false, left-aligned) vs 1 (true, right-aligned).
This is also supported by the SystemParametersInfo documentation linked in Remarks:
https://github.com/MicrosoftDocs/sdk-api/blame/92b6682a0c74356473c471312bc114b2af8b3ff3/sdk-api-src/content/winuser/nf-winuser-systemparametersinfoa.md#L1619-L1629
https://github.com/MicrosoftDocs/sdk-api/blame/92b6682a0c74356473c471312bc114b2af8b3ff3/sdk-api-src/content/winuser/nf-winuser-systemparametersinfoa.md#L1652-L1662
Visual example for what it means to be left- or right-aligned relative to the current menu item:
dotnet-api-docs/xml/System.Windows/SystemParameters.xml
Line 4828 in a93d022
Left-aligned, standard in US/western locales using left-to-right text
Right-aligned, available as an accessibility setting in Windows and from the above-referenced registry setting being set to 1.
