Adding HEX support for set_pixel #144
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
Gadgetoid
requested changes
Feb 10, 2022
| g = int("0x"+hexstr[3:5], 16) | ||
| b = int("0x"+hexstr[5:], 16) | ||
|
|
||
| return (r, g, b, ) |
There was a problem hiding this comment.
Sufficient to just return r, g, b which implicitly returns a tuple.
| :param hexstr: Hex string like FFB4C0 | ||
| """ | ||
|
|
||
| r = int("0x"+hexstr[0:2], 16) |
There was a problem hiding this comment.
int(hexstr[0:2], 16) should work here, the 0x is ignored. eg:
>>> int("ff", 16)
255
>>> int("f", 16)
15
>>> int("01", 16)
1
>>>
Might want to look at handling other cases like "#FFFFFF", "FFF" and "#FFF" but this is a start at least.
In hindsight set_pixel(0xFF, 0xFF, 0xFF) is quite a lot less trouble 😆
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.
per #130