AutoHotkey Community

does not work for me!

win xp sp3 on dell inspiron 1525

Hi,

I followed the guide but couldn't get it to work with the built in keyboard on my Macbook Pro (early 2008) in bootcamp. I'm presently running Windows 7 beta. When I run the register utility, I can get it to detect keypresses from most keys but the Fn and Eject keys don't do anything. I do notice that the numbers I get are different for keys modified by the Fn key. Eg. a different response for F5 vs Fn+F5 (which gets mapped to reduce keyboard backlight brightness).

I've tried uninstalling the Apple keyboard drivers and installing the generic Microsoft drivers. This disables the normal functioning of the Fn key, but the Fn and Eject keys still don't show up under the autohotkey utility.

Has anyone gotten this to work for remapping Fn or Eject on a Macbook/Macbook Pro? I've read various references to this only working in XP. Does that mean it won't work in Vista/Win7?

Thanks!

I'm looking for the same thing as tinaa. Don't suppose anyone has a solution? Looks like no response for more than a year, so I will guess no.

I have a solution for the wired mini Apple Tastatur. My eject key is working as delete now. I swapped the win button with the alt one, with "keymapper.exe".
In that file DEL&UNDO...ahk in that zip file, I included a hotkey for undo and the "eject" mapping. (^ = Ctrl+Z) I use it often for my daw. You can delete it, it's on the bottom.
Alu.HID.Key.Mapping.zip

What I can't get to work is the FN button. I don't recieve any value by A.H.RemoteControlDLL.ahk, ScriptRecorder or FNMapper.ahk. Though the eject button works and responds with the same value 8 like the here known Wireless Apple Keyboards.
So its kind of weird. I would love to swap FN with ctlr. So if anyone could confirm that its an issue only with the wired versions. I would be thankful. Because I think maybe my FN button is dead now.

I've looked up a few topics on these too.
Strangely enough when i get the
AutoHotkeyRemoteControlDLL.ahk
open, i either have lables in chinese, or solid blocks of ||||| and ||D|||

The word "HID" isn't in the set at all.

i'm
WinXpPro SP2
Autohotkey_L
and the latest "Arial Unicode MS" font available.
Desktop PC, with a Logitech g15 (model 1) keyboard.
and a Rii Mini "RT-MWK01" hand held keyboard/touch pad.
(which has the FN key)

When i press the FN key (on the Rii Mini), i want autohotkey to notice, so that it acts as a shift state for my macros (on the Rii Mini.)

But that tutorial is a tad long winded, and not very enlightening about what all the things in AutoHotkeyRemoteControlDLL.ahk GUI window are, or mean.

_________________
Code I write is free to use under 2 Conditions.
1: Do Not indicate me as responsible for the code, in any way!
2: Do Not willingly inconvenience anyone using code originated by me, period!
Violation of the above voids your eligibility to use my code.

got the same issue as tinaa, except on a macbook pro 2010 and with windows 7 home

also read the guide and tried it. could not find the code for the fn key.

anyone successful on this ?

Got the same issue as you guys. I've read the guide and it says that when you've read through it youäll be able to make the fn key act as any key that you'd like but I can't find any part in the guide explaining an example of that.

I can't detect any Fn key (nor specifically Fn+F4) scan code using AutoHotkeyRemoteControlDLL.ahk.

I'm running the latest version of AutoHotkey, installed to run in ANSI mode. (When I tried to install it opting for Unicode mode listed device names were all in Chinese and there were no descriptions nor default Usage+UsagePage settings offered.)

I've run through every device, selecting each one then clicked 'register' to register its default Usage+UsagePage, then pressed my Fn+F4 combo keys on the laptop's built-in kbd, but there is no response in the scancode result window. I get a response for other keys for a couple of the devices, but not the F4.

Maybe my 2007 HP laptop (dv6000t, Vista 32-bit) requires a Unicode version of AutoHotkeyRemoteControlDLL.ahk to be able to detect the scan codes correctly rather than the ANSI version? Or maybe the Fn key isn't visible by software at all, only being visible to the BIOS?

I'll cross-post this first message in both relevant forum threads:
http://www.autohotkey.com/forum/viewtopic.php?t=41397
(about AutoHotkeyRemoteControlDLL.ahk) and
http://www.autohotkey.com/forum/viewtopic.php?t=30483
(about Fn key detection successes & failures using AutoHotkeyRemoteControlDLL.ahk),
but I recommend only replying to the 1st thread since I think that seems the more relevant and active thread.

Thanks!

Craig in NJ