suspect-devices/circuitpython/shared-module/framebufferio, branch 6.0.0-beta.1

FramebufferDisplay: Don't set rotation via core_construct

2020-09-01T16:00:22+00:00

The expectations of displayio.Display and frambufferio.FramebufferDisplay are different when it comes to rotation. In displayio.Display, if you call core_construct with a WxH = 64x32 and rotation=90, you get something that is 32 pixels wide and 64 pixels tall in the LCD's coordinate system. This is fine, as the existing definitions were written to work like this. With framebuffer displays, however, the underlying framebuffer (such as RGBMatrix) says "I am WxH pixels wide in my coordinate system" and the constructor is given a rotation; when the rotation indicates a transpose that means "exchange rows and columns, so that to the Groups displayed on it, there is an effectively HxW pixel region for use". Happily, we already have a set_rotation method. Thus (modulo the time spent debugging things anyway:) the fix is simple: Always request no rotation from core_construct, then immediately fix up the rotation to match what was requested. Testing performed: 32x16 RGBMatrix on Metro M4 Express (but using the Airlift firmware, as this is the configuration the error was reported on): * initially construct display at 0, 90, 180, 270 degrees * later change angle to 0, 90, 180, 270 degrees * no garbled display * no safe mode crashes

Split pulseio.PWMOut into pwmio

2020-08-18T20:08:33+00:00

This gives us better granularity when implementing new ports because PWMOut is commonly implemented before PulseIn and PulseOut. Fixes #3211

Update shared-module/framebufferio/FramebufferDisplay.h

2020-08-12T17:50:08+00:00

Co-authored-by: Scott Shawcroft

sharpmemory: Implement support for Sharp Memory Displays in framebufferio

2020-08-12T12:32:18+00:00

framebufferio: add dirty row tracking

2020-08-12T12:32:18+00:00

framebufferio: Add getters for remaining displayio_display_core_construct arguments

2020-08-12T12:32:18+00:00

.. and introduce a convenience macro that helps many of them be required (if their values match defaults or are inapplicable)

framebufferio: Check early if framebuffer is big enough

2020-08-12T12:32:18+00:00

framebufferio: add "first pixel offset" and "row stride"

2020-08-12T12:32:18+00:00

framebufferio: handle sharp memory displays

2020-08-12T12:32:18+00:00

A bit of cheating; we need to add a protocol getter for reverse_bytes_in_word

framebufferio: Handle 1 (tested), 2, and 4 bpp displays

2020-08-12T12:32:18+00:00