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.
Explicit user-controlled pixel scale and HiDPI fix #579
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
base: master
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
Explicit user-controlled pixel scale and HiDPI fix #579
Changes from 12 commits
6ef31277daa3e8fb4adedb7e269f33101dd7667cd9c481e046c9937bac60e4b4b9b016f66f3c762fadadab27bf7File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this new persistent-canvas contract, the published docs still tell users the opposite:
docs/topics/hidpi.md:24-26says CF recreates the app canvas on resize/scale changes andcf_app_set_canvas_sizeis one-shot,docs/topics/application_window.md:100says the same, andinclude/cute_draw.h:2214-2215still says CF resets the projection on resize. Users following those pages won't callcf_app_update_display()aftercf_app_was_resized(), so their resizable windows keep the old canvas/projection and render stretched or clipped.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After this change,
cf_make_apptreatsw/has logical points and multiplies by the content scale before creating the SDL window. On Windows/X11 at 150% scaling, callers followinginclude/cute_app.h:224-225(pixels) who request 640x480 now get a 960x720 physical window; either the constructor docs/examples need to move to logical points along withcf_app_set_size, or this scaling should not happen here.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.