Resolution adjustments v2 - #78
Merged
CaitlynMainer merged 2 commits intoAug 24, 2026
Merged
Conversation
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.
[ Rewrite of #68 using a different driver extension strategy. ]
Multi-item PR to make using higher tier screens nicer:
hardwareResolution()andhardwareDepth()- that always return the GPU's maximum supported resolution and depth respectively, regardless of the limits of the attached screen.This allows software to sanely query for the true maximum capabilities of your graphics hardware and be able to inform the user if one side or the other is bottlenecking the system. This is theoretically something you could have already done, but it required grovelling through
computer.getDeviceInfo()and knowing the precise values of the 'product name' for each GPU and APU and their max resolution widths, and would break if any of these predicating assumptions ever changed (unlikely, but still annoying)./bin/resolutionprogram to be able to query for maximum supported system resolution, and using the new driver features, whether or not you have a bottleneck.It just plain wasn't able to do this before; it could only set a chosen resolution or return the current resolution. A sorely needed QoL enhancement that's been a decade coming.