-
Notifications
You must be signed in to change notification settings - Fork 6
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
4K and Scaling #12
Comments
Hi, Thanks! I'm working on an AOT version but I'm waiting for some Microsoft's pieces improvements (namely C#/WinRT). It's not aware in the sense that the application's window will not scale when moved from say a 100% to a 150% screen but it's aware in the sense that it's declared as dpiAwareness PerMonitorV2, and it should not disfunction (as some UI framework do even when they are supposedly "aware") when moved over, ie: the whole window should display fine and identical when moved around, unless I've missed something. It also means you should be able to add some custom code, or override things to adapt if needed. Do you have a specific scenario in mind? |
Ok, I get it, it's related to the primary display, I have two and was doing my testing with a non-primary one. You have only one. When I change DPI for the primary one I also see bigger Rich Text Boxes. Rich Text Box is one of rare Wice components that rely on an underlying windows component (Richedit or Office Richedit https://learn.microsoft.com/en-us/windows/win32/controls/about-rich-edit-controls). Apparently this behaves in a way that causes the difference between Wice texts and Rich Text Box texts. I need to investigate this further. |
Ok I've made some changes in RichTextBox code (and also in titlebar which had some issues in hi-DPI contexts too). Can you try it? |
Kudos for the project!
I found that at least demo, is not scaling aware.
The text was updated successfully, but these errors were encountered: