r2023-07-07

• Adds special handling for a new variant of Elecom Huge wireless trackball (056e:011c) so that Fn1, Fn2, Fn3 buttons work.
• Makes the "unique" device names a bit more unique. This means your device name will change after flashing this release.

r2023-05-26

• Input monitor. If you're not sure what inputs your device is sending for some buttons or axes, you can now check it in the "Monitor" tab. Especially useful for non-standard/vendor-specific usage codes.
• Keyboard LEDs support. Caps Lock, Num Lock, Scroll Lock etc. should now work and you can also remap them.
• GPIO pin inputs. Add extra buttons to your mouse or keyboard by wiring a switch directly to one of the Pico's GPIO pins.
• Device name suffix. If you have more than one HID Remapper, it is now easier to tell which is which.
• 32 macros. Up from 8.
• Fix for polling interval regression. At some point we lost the logic that rounded the polling interval to the nearest power of two. This restores the previous behavior.

Please note some of the features are not present in the Bluetooth version yet.

r2023-04-26

This release is a hotfix for the Feather USB Host board build. It adds driving pin 18 high (EN pin on the 5V boost converter).

It also pulls the latest TinyUSB changes, hopefully with no changes in behavior.

r2023-04-24

This release has no functional changes, but adds a firmware build for Adafruit's Feather RP2040 with USB Type A Host board.

Use the remapper_feather.uf2 firmware file for that board.

r2023-02-17

• Expressions! An advanced feature that lets you create complex mappings. Look for examples in the documentation.
• New version of the single Pico variant. Should be compatible with some devices that didn't work before.
• Web configuration interface reorganized into tabs.
• pico-sdk and tinyusb updated to latest versions.

r2023-01-27

Tap-hold is a mechanism that lets you map a button to one function when it is clicked and another when it is held. For example you could make the middle mouse button act as middle button when it is clicked, but trigger a layer (or a modifier like Shift) when it is held.

The threshold between tap and hold is configurable (globally, not per-mapping) and is set to 200ms by default.

A mapping with the "tap" flag set can also be sticky. For example you could make one "button X->layer Y" mapping with "tap"+"sticky" flags and another "button X->layer Y" mapping with the "hold" flag. That way the layer would latch on when the button is clicked, but would only activate temporarily when it is held.

r2023-01-19

• Multiple layer-activating sticky mappings on different layers with the same trigger button should now work. In particular this can be used to implement a "layer cycle" button, for example to emulate a DPI cycle button on a mouse.
• The user button on the Feather nRF52840 board should now work.

r2023-01-14

• It is now possible to define macros and trigger them through mappings. This allows for previously impossible things like mapping a button to double-click or having one key type some text.
• Mappings can now be present on more than one layer, which could reduce the number of mappings required in some configurations.
• Unmapped input passthrough now also works on layers other than 0 and can be enabled or disabled on each layer individually.
• Layer activating mappings are no longer implicitly present on all layers, but they are still forced to be present on the layer they activate.
• Some bugs related to sticky mapping handling were fixed.

r2022-12-29

This release makes it easier to flash B-side firmware on the custom boards. OpenOCD/picoprobe and non-standard USB cables are no longer required. Now you just flash the A side with remapper_board.uf2 and then click "Flash B side" on the web config tool. In the future it would be nice to eliminate that last step and make it automatic.

(It also works on the dual Pico version, but you have to connect two additional wires: GPIO2 on board A to SWCLK on board B and GPIO3 on board A to SWDIO on board B.)

r2022-12-16

r2022-12-16