| Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
So that one can easily access the underlying data of the frame buffer, eg
to write the data out to a display.
|
|
These are basic drawing primitives. They work in a generic way on all
framebuf formats by calling the underlying setpixel or fill_rect C-level
primitives.
|
|
Fill is a very common operation (eg to clear the screen) and it is worth
optimising it, by providing a specialised fill_rect function for each
framebuffer format.
This patch improved the speed of fill by 10 times for a 16-bit display
with 160*128 pixels.
|
|
For backwards compatibility. It simple creates a frame buffer with the
MVLSB format.
|
|
Rename FrameBuffer1 into FrameBuffer and make it handle different bit
depths via a method table that has getpixel and setpixel. Currently
supported formats are MVLSB (monochrome, vertical, LSB) and RGB565.
Also add blit() and fill_rect() methods.
|
|
One can instead lookup __name__ in the modules dict to get the value.
|
|
Adds horizontal scrolling. Right now, I'm just leaving the margins
created by the scrolling as they were -- so they will repeat the
edge of the framebuf. This is fast, and the user can always fill
the margins themselves.
|
|
So that users of framebuf don't need to have stmhal directory in their
path. (Eventually the font can be moved elsewhere.)
|
|
There was a bug in `framebuf1_fill` function, that makes it leave a few
lines unfilled at the bottom if the height is not divisible by 8.
A similar bug is fixed in the scroll method.
|
|
|
|
|