suspect-devices/circuitpython/shared-module/gamepad, branch 3.xCircuitPython - a Python implementation for teaching coding with microcontrollershttps://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=3.x2018-05-30T21:11:22+00:00Add gamepad_singleton to root pointers2018-05-30T21:11:22+00:00Radomir Dopieralskiopenstack@sheep.art.pl2018-05-24T09:25:21+00:00urn:sha1:b219ce6d377b6e00e1967c9b98966d4229f566edRemove volatile from the gamepad struct2018-05-23T19:49:20+00:00Radomir Dopieralskiopenstack@sheep.art.pl2018-05-23T19:49:20+00:00urn:sha1:42e36a883b4145e9f8b70022d6f13ceaab4fca2cAvoid uninitialized gamepad on exception2018-05-23T19:39:06+00:00Radomir Dopieralskiopenstack@sheep.art.pl2018-05-23T19:39:06+00:00urn:sha1:240678e71403f54ab31452a7138dfd8ddcfc7f0c
Raise exceptions before the gamepad_singleton is created.
Also, use mp_raise for creating the exceptions.
Cache pullup state in gamepad2018-05-23T09:26:16+00:00Radomir Dopieralskiopenstack@sheep.art.pl2018-05-23T09:26:16+00:00urn:sha1:52d05bbc37d063a1fdc359b18b9b112665f92276
Don't check the pin's pull direction on every tick, instead cache it
at the beginning. Also avoid a "can't get pull of output pin" error
when one of the pins passed is in output mode.
Respect pin's pull in gamepad2018-03-31T19:13:02+00:00Radomir Dopieralskiopenstack@sheep.art.pl2018-03-31T19:13:02+00:00urn:sha1:280374fa63e284f272b714358aac32b75a4bee6a
While it is traditional to have buttons on pins that are pulled up, and
have the button connect them to the ground, some CircuitPython boards
(notably the CPX) have the button pins pulled low and the button
connects them to VCC.
This patch makes the gamepad only change the pin's pull if it wasn't
already set when passed to the constructor, and also makes it consider
a button pressed when its value is the opposite of its pull.
Gracefully reset the gamepad module2017-10-23T03:54:10+00:00Radomir Dopieralskiopenstack@sheep.art.pl2017-10-21T22:50:58+00:00urn:sha1:1c97b7f4df63e5fcac655b2749e861eeba4ef79f
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
Add a `gamepad` module for handling buttons in the background. (#295)2017-10-03T20:35:57+00:00Radomir Dopieralskideshipu@users.noreply.github.com2017-10-03T20:35:57+00:00urn:sha1:f4981677b0b73d286f3af098a4111f8ba6d286bc
The `GamePad` singleton monitors buttons in the background to make sure a button press is never missed and debouncing happens consistently.