Problem with FTL Macro

[Freddie]

Based on the info you posted, we can state the problem in a single sentence:

HotkeyNet says it's sending LCtrl F10 to wow2, but wow2 isn't doing what you expect.

Please correct me if I'm wrong (I may be confused because I don't play WoW) but I think that's the problem in a nutshell.

The next step is to think of each factor that could cause that sentence to happen, and devise a little test to see if that's the cause.

I'll follow the data flow backwards. (In other words, start with WoW and work my way upstream to HotkeyNet.) Here are three possible places where this could be failing:

1. Maybe LCtrl F10 is getting received by WoW, but for some reason (bindings, something about the macro syntax, etc.) WoW isn't reacting as you expect. You can test this possibility by changing wow2's macro for LCtrl F10 to something extremely simply like "jump."

2. Maybe there's something peculiar about the way WoW handles LCtrl F10. You can test this possibility by changing the LCtrl F10 (in both the script and binding) to something else, perhaps LAlt F10 or simply F10.

3. Maybe HotkeyNet is sending LCtrl F10 to the wrong window. You'll notice in HotkeyNet's status messages, it tells you the handle (the hex number) of the window to which it's sending keystrokes. If you're on Vista or Win 7 it's possible under cetain rare circumstances for HotkeyNet to accidentally target a thumbnail of the desired window instead of the real one. To rule out this possibility, you need to compare the hex number (handle) that HotkeyNet is targeting with the hex number (handle) of the real wow2 window. You can identify the real hex number (handle) with a little utility that's built into HotkeyNet's action menu.

Number 3 was reported by a user not long ago who had the habit of sweeping the mouse over the task bar after clicking windows to bring them to the foreground. This caused the thumbnail to pop up after the window was activated.