suspect-devices/circuitpython/shared-module/displayio, branch 6.2.xCircuitPython - a Python implementation for teaching coding with microcontrollershttps://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=6.2.x2021-03-25T16:21:39+00:00move to displayio_area_union and away from _expand2021-03-25T16:21:39+00:00Kevin Matochakmatocha@icloud.com2021-03-25T16:21:39+00:00urn:sha1:9485805b6aa6178f2b4abe0eaefc76c4ebfc4b6dupdate logic for transform_xy2021-03-22T21:38:56+00:00Kevin Matochakmatocha@icloud.com2021-03-22T21:38:56+00:00urn:sha1:24831a79d3564f88f06ef49093f042919454d06bMerge pull request #4432 from jepler/bitmap-dirty-improvements2021-03-20T18:09:59+00:00Jeff Eplerjeff@adafruit.com2021-03-20T18:09:59+00:00urn:sha1:e084a92671b01220c795d114bee9d5058dbfa680
Bitmap dirty improvementsswitch to > in displayio_area_canon2021-03-20T01:30:37+00:00Kevin Matochakmatocha@icloud.com2021-03-20T01:30:37+00:00urn:sha1:40829d4cc85394513ca631cff23254344e29786cFix PWMOut non-error handling and never reset2021-03-19T13:57:21+00:00Dan Halberthalbert@halwitz.org2021-03-19T13:57:21+00:00urn:sha1:1512ca520b3e78ebc5cf6d9e031ac24c9206f1bbMerge pull request #4429 from jepler/displayio-bitmap-memoryview2021-03-18T23:38:25+00:00Jeff Eplerjeff@adafruit.com2021-03-18T23:38:25+00:00urn:sha1:623ece2c73b1a7886695fc09bde82f79ae47b3d7
displayio.Bitmap: Make memoryview()abledisplayio: Move bitmap read-only checking to displayio_bitmap_set_dirty_area2021-03-18T14:20:56+00:00Jeff Eplerjepler@gmail.com2021-03-18T14:20:21+00:00urn:sha1:f5fd42c39340483bc781746fd0acd304abd888ae
This is a modest code savings, but more importantly it reduces
boilerplate in bitmap-modifying routines.
Callers need only ensure they call displayio_bitmap_set_dirty_area in
advance of the bitmap modifications they perform.
(note that this assumes that no bitmap operation can enter background
tasks. If an operation COULD enter background tasks, it MUST re-dirty
the area it touches when it exits, simply by a fresh call to
set_dirty_area with the same area as before)
displayio_bitmap_set_dirty_area: rewrite in terms of displayio_area2021-03-18T14:20:56+00:00Jeff Eplerjepler@gmail.com2021-03-18T14:09:29+00:00urn:sha1:36d608aa67229653c0be12fab407533d0d8b7d32
.. simplifying code in the process. For instance, now fill_region
uses area routines to order and constrain its coordinates.
Happily, this change also frees a modest amount of code space.
displayio: area: add displayio_area_canon2021-03-18T14:06:00+00:00Jeff Eplerjepler@gmail.com2021-03-18T14:06:00+00:00urn:sha1:3b506f0fa59872916b617083a3dad9cadd07c428
This routine will be used to simplify code that deals with ranges
of bitmap coordinates.
displayio: area: add displayo_area_copy_coords, displayio_area_empty2021-03-18T14:05:07+00:00Jeff Eplerjepler@gmail.com2021-03-18T14:04:53+00:00urn:sha1:f40c0c13adacf39bc9a21afd2d9ebbf29135e0f0
.. and simplify the implmentation of displayio_area_union
This _slightly_ changes the behavior of displayio_area_union:
Formerly, if one of the areas was empty, its coordinates were still
used in the min/max calculations.
Now, if one of the areas is empty, the result gets the other area's coords
In particular, taking the union of the empty area with coords (0,0,0,0)
with the non-empty area (x1,y1,x2,y2) would give the area (0,0,x2,y2)
before, and (x1,y1,x2,y2) after the change.