Currently, it is not possible to use different keyboard layouts than US for the FLipMouse.
As we have limited resources in the FLipMouse (current master: 92% Flash, 79% static RAM usage),
we could implement a lookup of keys / text or keycodes via the ESP32 module (4MB flash -> we can store all supported keymaps of Teensyduino there).
In my opinion, we need following new features:
Detect if a compatible ESP32 module is connected
A dynamic table which contains the most recently used keycodes
Update mechanism to load a new keycode for a key from ESP32
Fallback solution (e.g. currently used static keymap) if dynamic update is not possible
Won't be implemented in v2 due to the problem that we cannot rely on a connected ESP32;
in v3 we could implement different keyboard layouts on the RP2040 already.
Currently, it is not possible to use different keyboard layouts than US for the FLipMouse. As we have limited resources in the FLipMouse (current master: 92% Flash, 79% static RAM usage), we could implement a lookup of keys / text or keycodes via the ESP32 module (4MB flash -> we can store all supported keymaps of Teensyduino there).
In my opinion, we need following new features: