Can I use ANY to map such keys combination?

[ZaxonXP]

Information

• None of the other issue templates apply

Description

I was reading the documentation about QMK Configurator, but I still cannot figure out how to program following sequence:

I need to press and hold the * from the keypad, then press 1 from the keypad, then release the *. Can this be done with ANY command?

Kind regards,
Piotr

[noroadsleft]

This would be a macro command. You can't do this solely in QMK Configurator. What's the use case?

[ZaxonXP]

I have Keyboard Mouse switch (KM switch) attached to the keyboard and mouse with 4 PC connected. In order to switch between PC's I need to hold asterisk on the keypad and press 1/2/3/4 (to select respective PC) then release all the keys. However I do not know how to program such macro.

[noroadsleft]

Okay, you can compile this in QMK Configurator, but it can't be set up fully in Configurator.

1. Set up the keymap for your keyboard

Do this as you normally would, then instead of hitting Compile, download/export the keymap.json.

2. Add the macro functionality

When you download the JSON and open it in a text editor, you'll find something like this:

{
  "version": 1,
  "notes": "",
  "documentation": "\"This file is a QMK Configurator export. You can import this at <https://config.qmk.fm>. It can also be used directly with QMK's source code.\n\nTo setup your QMK environment check out the tutorial: <https://docs.qmk.fm/#/newbs>\n\nYou can convert this file to a keymap.c using this command: `qmk json2c {keymap}`\n\nYou can compile this keymap using this command: `qmk compile {keymap}`\"\n",
  "keyboard": "handwired/k_numpad17",
  "keymap": "handwired_k_numpad17_layout_numpad_5x4_mine",
  "layout": "LAYOUT_numpad_5x4",
  "layers": [
    [
      "KC_NLCK",
      "KC_PSLS",
      "KC_PAST",
      "KC_PMNS",
      "KC_P7",
      "KC_P8",
      "KC_P9",
      "KC_P4",
      "KC_P5",
      "KC_P6",
      "KC_PPLS",
      "KC_P1",
      "KC_P2",
      "KC_P3",
      "KC_P0",
      "KC_PDOT",
      "KC_PENT"
    ]
  ],
  "author": ""
}

Below the line that says "layout": "LAYOUT_numpad_5x4",, add the following:

  "macros": [
    [
      {"action": "down", "keycodes": ["PAST"]},
      {"action": "tap", "keycodes": ["P1"]},
      {"action": "up","keycodes": ["PAST"]}
    ],
    [
      {"action": "down", "keycodes": ["PAST"]},
      {"action": "tap", "keycodes": ["P2"]},
      {"action": "up","keycodes": ["PAST"]}
    ],
    [
      {"action": "down", "keycodes": ["PAST"]},
      {"action": "tap", "keycodes": ["P3"]},
      {"action": "up","keycodes": ["PAST"]}
    ],
    [
      {"action": "down", "keycodes": ["PAST"]},
      {"action": "tap", "keycodes": ["P4"]},
      {"action": "up","keycodes": ["PAST"]}
    ]
  ],

Then, somewhere in your keymap, assign the following keycodes:

• MACRO_0
• MACRO_1
• MACRO_2
• MACRO_3

These keycodes correspond to the macros defined – MACRO_0 to the first block (KC_PAST down, tap KC_P1, release KC_PAST), MACRO_1 to the second, and so on.

3. Import and compile

Import the keymap.json back into QMK Configurator, and compile as normal.

[donhilion]

Does this work with the online editor here? https://config.qmk.fm/#//

I tried this to get copy and paste keys.

{
  "layers": [
    [
      "MACRO_0",
      "MACRO_1"
    ]
  ],
  "macros": [
    [
      {"action": "down", "keycodes": ["LCTL"]},
      {"action": "tap", "keycodes": ["C"]},
      {"action": "up","keycodes": ["LCTL"]}
    ],
    [
      {"action": "down", "keycodes": ["LCTL"]},
      {"action": "tap", "keycodes": ["V"]},
      {"action": "up","keycodes": ["LCTL"]}
    ]
  ]
}

After importing, compiling and flashing the keys don't seem to do anything.

[noroadsleft]

@donhilion Yours can be done with the native keycodes present on QMK Configurator:

Drag the LCTL() keycode (Quantum tab under Mod key combinations) onto the desired keys, then drag C and V, respectively, into the inner boxes on the keymap.

[donhilion]

That works, thanks!
But there remains the question: What is wrong with this configuration or the steps taken?

[Esnos33]

@noroadsleft Hi, I have problem with my macro. I wanted to have macro to make "->" arrow, but it doesn't work. I modified my json file like this

"keymap": "esnos",
  "macros": [
    [
      {"action": "tap", "keycodes": ["KC_MINUS", "KC_GT"]}
    ]
  ],
  "layout": "LAYOUT_split_3x5_2",
  "layers": [
    [
      "KC_ESC",

and later in code I have:

      "KC_ENT",
      "QK_MACRO_0",
      "KC_LPRN",
      "KC_RPRN",

and in qmk configurator uploaded json file looks like this:
https://imgur.com/a/zaABNMJ
but it doesn't work. Also, if I use MACRO_0 instead of QK_MACRO_0, I have this compilation error:
gmake: *** ap_introspection.o] Error 1

After uploading firmware to my keyboard, this button doesn't work, it doesn't send any signal according to KeyboardStateView.

Could you please help me? I can't find anybody on internet who have macro with json file.

[noroadsleft]

@Esnos33,

For your tap action, try this:

       {"action": "tap", "keycodes": ["MINS"]},
       {"action": "tap", "keycodes": ["GT"]}

[Esnos33]

@noroadsleft I have something like this:

  "macros": [
    [
      {"action": "tap", "keycodes": ["MINS"]},
      {"action": "tap", "keycodes": ["GT"]}
    ]

and QK_MACRO_0 in code, but still it doesn't work

[Jefferycheng]

@Esnos33

I want to input "=>" through one key, the same idea as you.
I thought this is a bug of qmk configurator.
I directly use the qmk firmware to compile that works!
In layers, the keycode is set to 'QK_MACRO_0 ' that is correct

The following are my macros.

"macros": [
    [
      {
        "action": "tap",
        "keycodes":["EQL"]
      },
      {
        "action": "down",
        "keycodes":["LSFT"]
      },
      {
        "action": "tap",
        "keycodes":["DOT"]
      },{
        "action": "tap",
        "keycodes":["LSFT"]
      }
    ]
  ]

The qmk firmware overview is here : https://docs.qmk.fm/#/newbs?id=overview
For more macros information is here : https://docs.qmk.fm/#/feature_macros?id=macros

[Esnos33]

@Jefferycheng Ok, I will try directly compile firmware and see what happens, thanks for answer.

[Esnos33]

@Jefferycheng I must admint, whole process is very hard just to have this one arrow, I will use other software to have this arrow

[Jefferycheng]

@Esnos33 I agree with you the whole process is long and complex.

Even though I have run the process before, I often forget how to do this.

So now, I am recording the whole process in my blog here: https://medium.com/p/9b9bc0bad275

Wish this can help you.

[Esnos33]

@Jefferycheng It works! Thanks for help, I really appreciate it.

[Nairda015]

I've conducted some tests on my end. Here are the observations:

• When compiled locally, the macro works as expected.
• When the same file is uploaded to https://config.qmk.fm/, the compilation succeeds, but the keyboard does not recognize the macro.

Sidenote:
@Jefferycheng, the QMK documentation provides a tip on simplifying the process. It suggests assigning a default keyboard and keymaps. This allows you to run the following command: QMK compile -e BUILD_DIR="./builds"

Additional Information:
The entire local build process took me approximately 10 minutes. However, installing QMK from Homebrew took over an hour, which I'm not sure is typical behaviour.

[marcoXbresciani]

Same issue for me here, right after one year.
I'm using online Configurator and it fits me very well, with (at the moment?) absolutely no need to go with the code.

I'm trying to add 6 macros to write capital accented letters we sometimes use here in Italy: À (Alt+0192), È (Alt+0200), É (Alt+0201), Ì (Alt+0204), Ò (Alt+0210), Ù (Alt+0217).
Same process as above, my macros are:

  "macros": [
    [
        { "action": "down", "keycodes": [ "KC_LALT" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P1" ] },
        { "action": "tap", "keycodes": [ "KC_P9" ] },
        { "action": "tap", "keycodes": [ "KC_P2" ] },
        { "action": "up", "keycodes": [ "KC_LALT" ] }
    ],
    [
        { "action": "down", "keycodes": [ "KC_LALT" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P2" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "up", "keycodes": [ "KC_LALT" ] }
    ],
    [
        { "action": "down", "keycodes": [ "KC_LALT" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P2" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P1" ] },
        { "action": "up", "keycodes": [ "KC_LALT" ] }
    ],
    [
        { "action": "down", "keycodes": [ "KC_LALT" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P2" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P4" ] },
        { "action": "up", "keycodes": [ "KC_LALT" ] }
    ],
    [
        { "action": "down", "keycodes": [ "KC_LALT" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P2" ] },
        { "action": "tap", "keycodes": [ "KC_P1" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "up", "keycodes": [ "KC_LALT" ] }
    ],
    [
        { "action": "down", "keycodes": [ "KC_LALT" ] },
        { "action": "tap", "keycodes": [ "KC_P0" ] },
        { "action": "tap", "keycodes": [ "KC_P2" ] },
        { "action": "tap", "keycodes": [ "KC_P1" ] },
        { "action": "tap", "keycodes": [ "KC_P7" ] },
        { "action": "up", "keycodes": [ "KC_LALT" ] }
    ]
  ],

because I have to use Alt+numpad numbers to write them, with Italian (142) layout on my (Windows) PC since they are not present on the keyboard.
Compiles perfectly, but no key sent.

Hints for me? Shall I move to code? :(

[marcoXbresciani]

@Esnos33 I agree with you the whole process is long and complex.

Even though I have run the process before, I often forget how to do this.

So now, I am recording the whole process in my blog here: https://medium.com/p/9b9bc0bad275

Wish this can help you.

Also, following the steps listed in your blog @Jefferycheng I have warnings and errors as well:

Warnings are

Generating: .build/obj_omkbd_ergodash_rev1__develop-it/src/info_config.h                            [WARNINGS]
 |
 | ⚠ omkbd/ergodash/rev1/: Layout "LAYOUT_2key" should not contain name of keyboard.
 | ⚠ omkbd/ergodash/rev1/: Layout "LAYOUT_3key_1us" should not contain name of keyboard.
 | ⚠ omkbd/ergodash/rev1/: Layout "LAYOUT_4key_2u_inner" should not contain name of keyboard.
 | ⚠ omkbd/ergodash/rev1/: Layout "LAYOUT_3key_2us" should not contain name of keyboard.
 | ⚠ omkbd/ergodash/rev1/: Layout "LAYOUT_4key" should not contain name of keyboard.
 |

while errors are

Compiling: quantum/keymap_introspection.c                                                          In file included from quantum/keymap_introspection.c:5:
./.build/obj_omkbd_ergodash_rev1__develop-it/src/keymap.c: In function 'process_record_user':
./.build/obj_omkbd_ergodash_rev1__develop-it/src/keymap.c:33:1: error: \x used with no following hex digits
   33 |                 SEND_STRING(SS_DOWN(X_KC_LALT)SS_TAP(X_KC_P0)SS_TAP(X_KC_P1)SS_TAP(X_KC_P9)SS_TAP(X_KC_P2)SS_UP(X_KC_LALT));
      | ^
./.build/obj_omkbd_ergodash_rev1__develop-it/src/keymap.c:33:1: error: \x used with no following hex digits
./.build/obj_omkbd_ergodash_rev1__develop-it/src/keymap.c:33:1: error: \x used with no following hex digits
./.build/obj_omkbd_ergodash_rev1__develop-it/src/keymap.c:33:1: error: \x used with no following hex digits
./.build/obj_omkbd_ergodash_rev1__develop-it/src/keymap.c:33:1: error: \x used with no following hex digits
./.build/obj_omkbd_ergodash_rev1__develop-it/src/keymap.c:33:1: error: \x used with no following hex digits
./.build/obj_omkbd_ergodash_rev1__develop-it/src/keymap.c:36:1: error: \x used with no following hex digits

but I have no idea what to do next.

[marcoXbresciani]

Damn, stupid me!
It's because macros don't use KC_ in the keycodes. 🙄