suspect-devices/circuitpython/shared-bindings/gamepad, branch 4.0.0-alpha CircuitPython - a Python implementation for teaching coding with microcontrollers https://git.suspectdevices.com/suspect-devices/circuitpython/atom?h=4.0.0-alpha 2018-05-30T21:11:22+00:00 Add gamepad_singleton to root pointers 2018-05-30T21:11:22+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-05-24T09:25:21+00:00 urn:sha1:b219ce6d377b6e00e1967c9b98966d4229f566ed Make the gamepad singleton long-lived 2018-05-30T21:11:22+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-05-24T09:16:30+00:00 urn:sha1:c37b69e1a5316956ce966cce6841f3d960e581b0 So that it is not later moved. Remove volatile from the gamepad struct 2018-05-23T19:49:20+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-05-23T19:49:20+00:00 urn:sha1:42e36a883b4145e9f8b70022d6f13ceaab4fca2c Raise an error if more than 8 buttons passed to gamepad 2018-05-23T19:41:56+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-05-23T19:41:56+00:00 urn:sha1:f17a235b4069c9e35a998da4d406354dfc1a220c Avoid uninitialized gamepad on exception 2018-05-23T19:39:06+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-05-23T19:39:06+00:00 urn:sha1:240678e71403f54ab31452a7138dfd8ddcfc7f0c Raise exceptions before the gamepad_singleton is created. Also, use mp_raise for creating the exceptions. Make gamepad.get_pressed work when gamepad was created from frozen code 2018-05-23T10:44:22+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-05-23T10:44:22+00:00 urn:sha1:edf2935ab166d3db765eec600ffccaedee79e5a5 For some reason, when the GamePad is created from frozen code, the get_pressed method would always return 0. This fixes it, and makes it work properly no matter how the object was created. Cache pullup state in gamepad 2018-05-23T09:26:16+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-05-23T09:26:16+00:00 urn: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. Add a type check to the gamepad module 2018-03-31T18:41:16+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-03-31T18:41:16+00:00 urn:sha1:6ca4fd82eddcaaf75b0052d6a14a5938ffce8153 Make sure that all the arguments passed are indeed DigitalInOut. This avoids crashes when the users pass something else. Fix example for gamepad 2018-01-11T16:06:53+00:00 Radomir Dopieralski openstack@sheep.art.pl 2018-01-10T21:50:10+00:00 urn:sha1:0ff128ec0309f910bf605cde17abb2b89f409a6f The example code for the gamepad module would skip detected button presses in the code that waits for a button to be released, because it would run it even when no button is pressed. Also updated the example pin names to not use RX and TX. Add a `gamepad` module for handling buttons in the background. (#295) 2017-10-03T20:35:57+00:00 Radomir Dopieralski deshipu@users.noreply.github.com 2017-10-03T20:35:57+00:00 urn:sha1:f4981677b0b73d286f3af098a4111f8ba6d286bc The `GamePad` singleton monitors buttons in the background to make sure a button press is never missed and debouncing happens consistently.