-
Notifications
You must be signed in to change notification settings - Fork 679
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
Can not make RTL language application in WinUI 3 #8746
Comments
Just to be sure, have you tried adding the WS_EX_LAYOUTRTL EX style to the window, or have you called SetProcessDefaultLayout with LAYOUT_RTL? |
tnx, using SetProcessDefaultLayout and WS_EX_LAYOUTRTL EX working fine! |
First and foremost, welcome to the desktop environment. It has a lot of legacy behaviour that, at this point in time, is difficult to change. The biggest thing you did manage to verify is that WinUI 3 doesn't automatically apply the RTL layout to the underlying desktop window. |
ITNOA But I think WinUI can handle RLT/LTR change layout upper underlying Windows mechanism. and I think WinUI must have all good features and good behavior from UWP. because WinUI (if I understand correctly) wants to replace UWP framework. |
@soroshsabz |
Describe the bug
i want to make my winui 3 app RTL, this means All layouts, including the TitleBar and Custom TitleBar, should be right to left!
It is very strange that this was done easily in the previous versions.
But it is not possible in the latest version (1.3.2)
Steps to reproduce the bug
I did the following methods none of them change the language/layout of the app
Expected behavior
At least one of the above methods should change the language of the program, but nothing happens.
I also changed the Windows Language settings, but nothing happens
Screenshots
No response
NuGet package version
Windows App SDK 1.3.2: 1.3.230602002
Packaging type
Packaged (MSIX)
Windows version
Windows 11 version 22H2 (22621, 2022 Update)
IDE
Visual Studio 2022
Additional context
No response
Tasks
The text was updated successfully, but these errors were encountered: