suspect-devices/circuitpython/shared-bindings, branch 4.1.0-beta.1CircuitPython - a Python implementation for teaching coding with microcontrollershttps://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=4.1.0-beta.12019-06-18T23:44:50+00:00Fix reference to Bitmap in fontio.Glyph docs.2019-06-18T23:44:50+00:00Craig Forbescpforbes@starlake.org2019-06-18T23:44:50+00:00urn:sha1:09e7f4db00c13dd7fcea0fac3ced5ce9749ba331Fix docs in digitalio.2019-06-18T21:59:05+00:00Craig Forbescpforbes@starlake.org2019-06-17T16:58:05+00:00urn:sha1:e442efbdecf35066412efc155e20ee280c5449f3Fix displayio.Display docstring type for display_bus.2019-06-18T21:59:05+00:00Craig Forbescpforbes@starlake.org2019-06-14T20:30:38+00:00urn:sha1:db74b92e77757caab7c5f2bb1d6ae09f5be3ed97
Add docs for group parameter for Display.show.
Add baudrate to FourWire and shorten delay.2019-06-18T00:48:05+00:00Scott Shawcroftscott@tannewt.org2019-06-18T00:48:05+00:00urn:sha1:4013bcde9eeab3dd2f8fd15a156c32f866a637b9Merge pull request #1943 from adafruit/4.0.x2019-06-13T19:26:04+00:00Scott Shawcroftscott@adafruit.com2019-06-13T19:26:04+00:00urn:sha1:6d388a34eb909e27acd508dc001ae1fe94a530de
Merge in gamepadshift fix to master.Minor tweaks based on Dan's feedback2019-06-13T07:34:19+00:00Scott Shawcroftscott@tannewt.org2019-06-13T07:34:19+00:00urn:sha1:6f6dcafd906b2ac49291f4220f3fcc7cea6112e1When clearing gamepad buffer, use the last button state, not 02019-06-12T18:42:41+00:00Radomir Dopieralskiopenstack@sheep.art.pl2019-06-12T08:06:39+00:00urn:sha1:5e265f4fbd11e1bc099f2a0860aac2ac72eaf854
When reading the accumulated button presses in gamepad and gamepadshift,
don't clear the buffer to "no buttons pressed", but instead set it to
the current (last checked) state. This clears the accumulated presses,
but retains any ongoing ones.
This fixes #1935
Refactor deinit check to reduce code size.2019-06-12T18:36:43+00:00Scott Shawcroftscott@tannewt.org2019-06-12T08:00:59+00:00urn:sha1:a35d9b469d4ed65fd992771aa98ac57241983794Add partial display update support.2019-06-12T18:32:39+00:00Scott Shawcroftscott@tannewt.org2019-06-06T22:11:02+00:00urn: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.
Merge latest 4.0.x fixes into master2019-06-11T20:16:29+00:00Dan Halberthalbert@halwitz.org2019-06-11T20:16:29+00:00urn:sha1:4fc189b60c800f097db55c16768fa8c73eb72ccf