Wrap UG_FONT struct byte array access with macro in case an accessor function is needed #11
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
function is needed, as is the case on AVR if you use the PROGMEM attribute in the __UG_FONT_DATA declaration
|
Thank you! |
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.
Just a simple macro to allow for an alternative font data storage location that doesn't kill SRAM/RAM space. In AVR if you don't use the PROGMEM attribute in __UG_FONT_DATA, the font data takes up more than the available SRAM on the chip, but using the PROGMEM attribute requires accessing the font bytes with
pgm_read_byte(&(font->p[index++])). The macro allows configuring this accessor from ugui_config.h