@leolodreamland it’s in maiden, refresh your catalog
yeah i’m super happy to help get widespread keyboard support if folks are willing to help test. i’m not interested in physically acquiring a bunch of keyboards myself, nor am i interested in using “virtual” keyboards? i’d worry about qa.
@tyleretters there are a few github issues around this. in short my hope is to get “keyboard support” implemented as a core lua library, which will require some negotiation with the device code layer in matron (ie, detecting keyboard devices at a low level and not passing them to the HID layer, but making them available via a standard function). layouts are indeed an issue, but can be overcome (i think) by simply having a layout selector, which uses a different lua translation table (it would be easy for people to contribute these for keyboard layouts).
you’ve already implemented a lot of this for your script, redundantly, i might say, given NISP and orca both also have much code overlap— which is why this stuff should go in the core lib. the secondary motivator is to have keyboard control over the menu system (navigation, wifi password entry, etc).
while i would like to work on this myself, i am (always) stretched insanely thin re: new features given my code time gets eaten by fixes/etc— so regard this as an open call for new contributors
