Jump to content

Spire

Members
  • Posts

    3
  • Joined

  • Last visited

Spire's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I suspect there's more to it than that. I'm able to remap arbitrary keys on my keyboard to F13 using the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layout(Or by using a GUI utility such as SharpKeys that does the registry editing for me.) When I do so, I'm successfully able to capture F13 keystrokes using EventGhost or AutoHotkey when I press the remapped key on the keyboard. The F13 key on the “Full Keyboard” controller in the Flirc GUI app even lights up when I press the remapped key. However, the Flirc unit itself still fails to emit any F13 keystrokes when I press the remote button associated with F13. BTW, there are also keyboards available that have an F13 key, such as the Apple Keyboard with Numeric Keypad. I would be surprised if the F13 key on these keyboards didn't work under Windows.
  2. That's very interesting and I may very well end up doing as you suggest. Thanks! That said, it would still be nice to get an answer to my original question: Why does F13 not work when mapped using the Flirc GUI app? It's from HID usage table 7 (just like any regular keyboard key), and the GUI explicitly exposes it, so I would expect it to work.
  3. I just received my Flirc the other day and am enjoying it so far. I would like to program my Flirc to emit keystrokes that are not present on my physical keyboard; for example, the function keys F13‒F24, or even “reserved” keys, such as those in the 0xA5‒0xAF range (as documented in the HID spec). My idea is to intercept these keystrokes using something like EventGhost or AutoHotkey and transform them into useful complex actions, without having to worry about the actual keystrokes conflicting with those that might happen to be used in normal applications. I'm having trouble getting this to work. For example, if I use the Flirc GUI app to map something to F13 (using the “Full Keyboard” controller), it appears to take, but then I don't get an F13 when I press the associated remote button. Neither EventGhost nor AutoHotkey sees any keystroke at all. Microsoft Spy++ doesn't see any messages generated either. Same thing happens when I use flirc_util to map, say, 0xA5 using the following command line: flirc_util record_api 0 165Am I doing something wrong? Or have I run into a limitation or bug in Flirc, the HID driver, or the OS? I'm using Flirc 1.3.6 with firmware version 3.6 [07F892FC] under Windows 8.1 Update 1 (x64). In the meantime I've set things up using unlikely keystrokes (such as Ctrl+Alt+Shift+F1), but I'd really prefer to do things the way I described.
×
×
  • Create New...