Merged
Conversation
Contributor
Author
|
P.S. you should make a post on the Nim forum too! The 1.0 release is pretty cool. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Took a bit of working with Codex/GPT5 to get Wayland scaling working properly. Especially for fractional scaling. I've tested it with wayland and xwayland with both siwin examples/ and neonim.
The window sizes aren't the same between x11/wayland, but the content sizes match. Manually setting HDI appears to be working as well.
Events computed on wayland now also report using "raw pixel" size matching other platforms (x11, macos). I don't have Windows to verify windows follows it as well.