<feed xmlns='http://www.w3.org/2005/Atom'>
<title>suspect-devices/circuitpython/shared-module/gamepad, branch 3.0.0-alpha2</title>
<subtitle>CircuitPython - a Python implementation for teaching coding with microcontrollers</subtitle>
<id>https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=3.0.0-alpha2</id>
<link rel='self' href='https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=3.0.0-alpha2'/>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/'/>
<updated>2017-10-23T03:54:10+00:00</updated>
<entry>
<title>Gracefully reset the gamepad module</title>
<updated>2017-10-23T03:54:10+00:00</updated>
<author>
<name>Radomir Dopieralski</name>
<email>openstack@sheep.art.pl</email>
</author>
<published>2017-10-21T22:50:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=1c97b7f4df63e5fcac655b2749e861eeba4ef79f'/>
<id>urn:sha1:1c97b7f4df63e5fcac655b2749e861eeba4ef79f</id>
<content type='text'>
If a soft reset happens while the gamepad module is scanning for button
presses, there is a moment when the pins get de-initialized, but the
gamepad module is still trying to read them, which ends in a crash.
We can avoid it by disabling scanning on reset.

(cherry picked from commit 470a23d4c9345785bbaa830fdc036b4e982496c6)

Conflicts:
	atmel-samd/main.c
</content>
</entry>
<entry>
<title>Add a `gamepad` module for handling buttons in the background. (#295)</title>
<updated>2017-10-03T20:35:57+00:00</updated>
<author>
<name>Radomir Dopieralski</name>
<email>deshipu@users.noreply.github.com</email>
</author>
<published>2017-10-03T20:35:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.suspectdevices.com/suspect-devices/circuitpython/commit/?id=f4981677b0b73d286f3af098a4111f8ba6d286bc'/>
<id>urn:sha1:f4981677b0b73d286f3af098a4111f8ba6d286bc</id>
<content type='text'>
The `GamePad` singleton monitors buttons in the background to make sure a button press is never missed and debouncing happens consistently.</content>
</entry>
</feed>
