CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=5.0.0 2019-06-12T18:32:39+00:00 2019-06-12T18:32:39+00:00 Scott Shawcroft scott@tannewt.org 2019-06-06T22:11:02+00:00 urn:sha1:eb21fc3e31790cee094d5c11811b55a57625340a Different operations to the display tree have different costs. Be aware of these costs when optimizing your code. * Changing tiles indices in a TileGrid will update an area covering them all. * Changing a palette will refresh every object that references it. * Moving a TileGrid will update both where it was and where it moved to. * Adding something to a Group will refresh each individual area it covers. * Removing things from a Group will refresh one area that covers all previous locations. (Not separate areas like add.) * Setting a new top level Group will refresh the entire display. Only TileGrid moves are optimized for overlap. All other overlaps cause sending of duplicate pixels. This also adds flip_x, flip_y and transpose_xy to TileGrid. They change the direction of the pixels but not the location. Fixes #1169. Fixes #1705. Fixes #1923. 2019-05-22T22:00:47+00:00 Scott Shawcroft scott@tannewt.org 2019-05-22T22:00:47+00:00 urn:sha1:7a117f52ed81999261fae3d43dfeb572c5e9887e 2019-05-22T00:41:06+00:00 Scott Shawcroft scott@tannewt.org 2019-05-16T23:45:38+00:00 urn:sha1:3fad7de8db7f1f317ab6d00a00a82e406ec6fb33 This changes the displayio pixel computation from per-pixel to per-area. This is precursor work to updating portions of the screen (#1169). It should provide mild speedups because bounds checks are done once per area rather than once per pixel. Filling by area also allows TileGrid to maintain a row-associative fill pattern even when the display's refresh is orthogonal to it.