11–20 of 29 posts
Honestly, why Python? Writing a much faster equivalent in C really isn't any more complicated...
The hardware includes a QSPI flash which presents as an USB storage that stored Python source code, and you can modify Python directly.
BTW, It provides a new way to validate your hardware product ideas quickly.
Honestly, why Python? Writing a much faster equivalent in C really isn't any more complicated...
Just for fun :) The hardware includes a QSPI flash which presents as an USB storage that stored Python source code, and you can modify Python directly. BTW, It provides a new way to validate your hardware product ideas quickly.
Earlier quoted context omitted.
It is a bit slow. It takes 4 ms to scan the matrix once right now. With some optimizations, it may be faster.
Would Numpy be of use? Haven't looked at the source yet, but for a keyboard, 4 ms per matrix would be noticeably laggy, especially if you add debouncing (is that even a thing in keyboards?)
The controller is running CircuitPython which is a fork of MicroPython - a tiny re-implementation Python for microcontrollers.
Earlier quoted context omitted.
Would Numpy be of use? Haven't looked at the source yet, but for a keyboard, 4 ms per matrix would be noticeably laggy, especially if you add debouncing (is that even a thing in keyboards?)
It's a microcontroller. It has maybe 512k of storage and 128k of memory. The Numpy package probably is ~100Mb The controller is running CircuitPython which is a fork of MicroPython - a tiny re-implementation Python for microcontrollers.
Earlier quoted context omitted.
Would Numpy be of use? Haven't looked at the source yet, but for a keyboard, 4 ms per matrix would be noticeably laggy, especially if you add debouncing (is that even a thing in keyboards?)
How would 4ms be noticeably laggy?
Earlier quoted context omitted.
Would Numpy be of use? Haven't looked at the source yet, but for a keyboard, 4 ms per matrix would be noticeably laggy, especially if you add debouncing (is that even a thing in keyboards?)
The best usb keyboard should have 1ms latency due to USB HID interrupt interval. 4 ms is not that bad.
Nice, if I made it I would replace the capslock with control and "~" with escape. Make the least used keys require combinations, not the often used ones.
[1]https://needgap.com/problems/96-one-hand-keyboard-keyboard-a...