Resolve TFT Null Pointer issue. #471
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
…here there is no code/data placed in the .bin_storage section.
|
/clang-format-run |
ftariqAnalogTx
approved these changes
Mar 6, 2023
Jacob-Scheiffler
approved these changes
Mar 6, 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.
See MSDK-1061. The TFT driver did not properly handle the case where there is no code/data placed in the .bin_storage section. The fix was to initialize the image data structure so that the number of bitmaps, fonts, and palettes are initialized to 0. All functions were then checked to make sure they confirmed the image ID they were asked to use was less than then number of objects.