Fixed issues relating to Fullscreen #249
Open
Conversation
This file contains 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
I'm not gonna sugar coat it, my mood suffered greatly from these
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I'm not gonna sugar coat it, my mood suffered greatly from these Pull Requests. I hope it gets easier for me in v4 and 5+U.
Anyways, this fixes a few issues with Fullscreen and rendering kinda that have been brought up before. These include #177, #234, and this issue that came up while I was updating the MacOS build
Not only does it fix some of the rendering issues, but it also adjusts calculations for inputs like touch controls to match. Here are a few examples, first with 240 screen width, second with 384 width, and last with a 480 width, all on a 1440x900 resolution monitor and Hardware Renderer enabled.
