displayio.Bitmap: Make memoryview()able #4429
Merged
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 makes a displayio.Bitmap usable as a read-only buffer.
It enables this to work:
By having a buffer-like Bitmap we can now get bitmap data INTO ulab efficiently, just as we recently became able to get it OUT efficiently by addng
bitmaptools.arrayblit
.The docs explain that this is really only "defined" for 8/16/32-bit bitmaps where a row is a multiple of 4 bytes. For other cases, we pack bits in odd ways, and/or add padding bytes to the end of a row. I could throw an error in these cases instead, or we could fully document the in-memory format of the bitmap. I'm open to thoughts.