D.R.racer 299a31b765 Generate exactly 1 userInput event when button pressed (and held) ... This PR is a different solution to what @gudnimg found in PR#233 / PFW-1404. The benefit of this approach is the fact, that the button press event is generated when the button is pressed and not after it has been released. The downside is obvious: CPUFLASH: +28B RAM: +1B		2022-11-15 07:19:20 +01:00
..
buttons	Optimise Catch2 V3 includes + fix a few cases of missing includes	2022-10-22 15:41:44 +02:00
leds	Optimise Catch2 V3 includes + fix a few cases of missing includes	2022-10-22 15:41:44 +02:00
motion	motion: Also test for the simplest case of a single+unplanned move	2022-10-22 17:40:28 +02:00
protocol	Optimise Catch2 V3 includes + fix a few cases of missing includes	2022-10-22 15:41:44 +02:00
pulse_gen	Optimise Catch2 V3 includes + fix a few cases of missing includes	2022-10-22 15:41:44 +02:00
speed_table	Optimise Catch2 V3 includes + fix a few cases of missing includes	2022-10-22 15:41:44 +02:00
stubs	Optimise Catch2 V3 includes + fix a few cases of missing includes	2022-10-22 15:41:44 +02:00
timebase	Optimise Catch2 V3 includes + fix a few cases of missing includes	2022-10-22 15:41:44 +02:00
user_input	Generate exactly 1 userInput event when button pressed (and held)	2022-11-15 07:19:20 +01:00
CMakeLists.txt	Fix unit tests	2022-06-20 17:03:40 +02:00