Config Tool: Requests

General
1

Love the convenience of the Config Tool on-line: HID Remapper Configuration. A few wishes for improvements:

  1. Drag and drop option for the mappings list. So you can better group together mappings.

  2. An option to rename the GPIO ports to something more user-friendly (thinking of someone using a HID Remapper that has clear labels on a 3D printed case).

  3. Luxury request: A quicker way to select all layers for a mapping (if I have a lot of mappings that need to be on all four layers, that’s a lot of clicking).

They’re all luxury requests really, but I think would help users. Keep up the great work!

2

Not exactly what you’re asking for, but you can rename the input on an existing mapping by manually editing the JSON file.

Say you have a mapping like this:

        {
            "source_usage": "0xfff40001",
            "target_usage": "0x00090001",
            "layers": [
                0
            ],
            "sticky": false,
            "tap": false,
            "hold": false,
            "scaling": 1000,
            "source_port": 0,
            "target_port": 0
        }

You can add a source_name field:

        {
            "source_usage": "0xfff40001",
            "source_name": "Whatever",
            "target_usage": "0x00090001",
            "layers": [
                0
            ],
            "sticky": false,
            "tap": false,
            "hold": false,
            "scaling": 1000,
            "source_port": 0,
            "target_port": 0
        }

And it will show up instead of the default name in the input column.

But it will only apply to that single mapping, not that input in general, and it’s not stored on the device, so if you click “Load from device”, it gets lost.

1 Like
3

Thank you,

would you consider…

common.py

KC_A = “0x00070004”
KC_B = “0x00070005”
KC_C = “0x00070006”

…

KC_Z = “0x0007001d”

and then write to json something like

{
“source_usage”: KC_A,
“target_usage”: KC_Z,
“layers”: [
0
],
“sticky”: false,
“tap”: false,
“hold”: false,
“scaling”: 1000,
“source_port”: 0,
“target_port”: 0
},

4

That’s perfect for what I was looking to do. Thank you.

1 Like
5

I’ve got a small feature request as well: it would be really useful to have a button in the web interface to restart the device, especially when changing the output type.