Conversation
The fbdev backend was creating a screen using the caller-supplied dimensions (640x480 from main.c) instead of the actual framebuffer resolution, causing coordinate space mismatch and clipped rendering on smaller displays like the STM32F429 Discovery QVGA (320x240). In no-WM mode, the single window now unconditionally covers the entire screen rather than merely clamping to it. The screen dimensions are authoritative and come from the backend -- hardware resolution for fbdev, window size for SDL, etc.
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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
1 participant
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.
The fbdev backend was creating a screen using the caller-supplied dimensions (640x480 from main.c) instead of the actual framebuffer resolution, causing coordinate space mismatch and clipped rendering on smaller displays like the STM32F429 Discovery QVGA (320x240).
In no-WM mode, the single window now unconditionally covers the entire screen rather than merely clamping to it. The screen dimensions are authoritative and come from the backend -- hardware resolution for fbdev, window size for SDL, etc.
Summary by cubic
Make the no-WM window always match the backend’s screen size and use the real framebuffer resolution in fbdev. This fixes coordinate mismatches and clipped rendering on smaller displays.
fb_var.xres/yresinstead of caller-provided width/height.Written for commit 125e617. Summary will update on new commits.