Add a rendering quality property to the map canvas #4488
Merged
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
|
🎉 Ta-daaa, freshly created APKs are available for da248af: arm64-android |
m-kuhn
approved these changes
Jul 29, 2023
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.
This PR implements a map canvas quality property which allows users to trade rendering sharpness in favor of lower memory usage and rendering time. The UI is found in the settings panel below the language combobox:
Three quality settings are available: Best quality (current rendering), lower quality, and lowest quality.
Behind the scene, what we are doing is lowering the rendered output size to create smaller images resulting in smaller memory footprint (very useful for devices with low RAM) and less CPU cycles spent rendering (i.e., lowering battery drain).
Fixes #1447