TonBERRY/micropython
3
0
Fork 0
Code Pull Requests Activity

docs/library/framebuf: Clarify docs for blit regarding palette.

Browse Source 
Clarified the behaviour when both key and palette are specified.
This commit is contained in:
TPReal
2022-11-16 12:37:43 +01:00
committed by Damien George
parent 4ff10b5976
commit 859d0e9529
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/library/framebuf.rst
View File

@@ -133,7 +133,9 @@ Other methods
Draw another FrameBuffer on top of the current one at the given coordinates. Draw another FrameBuffer on top of the current one at the given coordinates.
If *key* is specified then it should be a color integer and the If *key* is specified then it should be a color integer and the
corresponding color will be considered transparent: all pixels with that corresponding color will be considered transparent: all pixels with that
color value will not be drawn. color value will not be drawn. (If the *palette* is specified then the *key*
is compared to the value from *palette*, not to the value directly from
*fbuf*.)
The *palette* argument enables blitting between FrameBuffers with differing The *palette* argument enables blitting between FrameBuffers with differing
formats. Typical usage is to render a monochrome or grayscale glyph/icon to formats. Typical usage is to render a monochrome or grayscale glyph/icon to