Should AHI Support Low-Level Interception of Huion Tablet Keys (F13–F24)?

[hsayed21]

Description

I have a keyboard that only supports F1–F12.
What I am trying to do is use my Huion Tablet buttons to extend this functionality by mapping them to F13–F24.

• With AutoHotInterception, I can intercept F1–F12 fine.
• But when I try to assign a Huion Tablet button to F13–F24 in the Huion driver, AHI does not intercept anything.

---

Example Script

Here’s a minimal AutoHotInterception script I use for testing:

#Include Lib\AutoHotInterception.ahk

AHI := AutoHotInterception()
keyboardId := AHI.GetKeyboardId(0x0C45, 0x5004)  ; Adjust VID/PID

; Intercept F1 and block it
AHI.SubscribeKey(keyboardId, GetKeySC("F1"), true, F1toF15)
return

F1toF15(state) {
    global AHI, keyboardId
    ToolTip("Intercepted F1 -> Sending F15`nState: " state)

    ; Send F15 (scan code)
    AHI.SendKeyEvent(keyboardId, GetKeySC("F15"), state)

    Sleep(100)
    ToolTip()
}

Esc::ExitApp

When I press F1 on the Huion to assign it as F15, but nothing is intercepted.

---

What I Want

I want to press a Huion Tablet button → and make Windows/AutoHotkey see it as F13–F24.
This way I can expand my shortcuts beyond F1–F12, since my main keyboard doesn’t have physical F13–F24 keys.

---

Question

Since AutoHotInterception is supposed to work at a low level, shouldn’t it also be able to intercept Huion’s F13–F24 mappings?

Is this a limitation of how Huion sends input, or should AHI still be able to capture and remap these at a lower level?

[evilC]

Is this a limitation of how Huion sends input, or should AHI still be able to capture and remap these at a lower level?

Probably a limitation of how the input is sent. Most likely the table communicates the input to the driver, and the driver then synthesises the input. AHI will only work with input that actually comes from hardware, not from software