Skip to content

Commit

Permalink
docs/library/framebuf: Clarify docs for blit regarding palette.
Browse files Browse the repository at this point in the history
Clarified the behaviour when both key and palette are specified.
  • Loading branch information
TPReal authored and dpgeorge committed Nov 17, 2022
1 parent 4ff10b5 commit 859d0e9
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion docs/library/framebuf.rst
Expand Up @@ -133,7 +133,9 @@ Other methods
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
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
formats. Typical usage is to render a monochrome or grayscale glyph/icon to
Expand Down

0 comments on commit 859d0e9

Please sign in to comment.