Problem with FTL Macro

[Bettysue]

Ya i was looking over the available keys link for WoW I think that just pertains to keybinding, I use the numberpad with a shift modifier in macros and have no known issues so far...then again I may actually have a problem and have never noticed becaue I usually stay on one toon when in vehicles.

[vorticone]

Sorry for the late reply, but I was out of town for work and have just today gotten back to fooling around with this.

Anyways, I tried your tips, changed a few things here and there, and well, it still doesn't work. So I started over, this time less complicated with only two characters and a new HKN mapping.

This is the macro I use on both characters:

/stopmacro [nomod]
/target [mod:ctrl,nomod:alt,nomod:shift,target=Beregond][nomod:alt,nomod:ctrl,mod:shift,target=Zillaya]
/follow

This is the HKN mapping:

//================================================================

//-----------------------------------------------------------
// DEFINE MAIL LABELS FOR SENDING KEY STROKES.
//-----------------------------------------------------------
<Label w1 Local SendWinM wow1>
<Label w2 Local SendWinM wow2>

//-----------------------------------------------------------
// FTL setup
//-----------------------------------------------------------
// %1% : Master Key
// %2% : Slave Key
// %3% : Modifier
// %4% : SlavesToSend
<Template SendMasterAndSlave>
         <SendFocusWin>
                  <Key %1%>         
         <Sendlabel %4%>
                  <Key %3% %2%>
<EndTemplate>

// %1% : master key
// %2% : slave key
// %3% : modifier
// %4% : Active window
// %5% : Slave Windows
<Template SendLeaderless>
        <If ActiveWinIs %4%>
            <ApplyTemplate SendMasterAndSlave "%1%" "%2%" "%3%" "%5%">
<EndTemplate>

// %1% : master-key
// %2% : slave-key
<Template FTL>
          <Hotkey %1%>     
                   <ApplyTemplate SendLeaderless "%1%" "%2%" "LCtrl" wow1 "w2">
                   <ApplyTemplate SendLeaderless "%1%" "%2%" "LShift" wow2 "w1">
<EndTemplate>
//-----------------------------------------------------------
// NEW STUFF
//-----------------------------------------------------------
<ApplyTemplate FTL "F10" "F10">

<Hotkey Space>
<SendLabel w1,w2>
<Key %Trigger%>

The macro is bound to hotkey F10 in both WoW clients, and I unmapped the old key of course.

The first instance wow1 is the character named Beregond, wow2 is Zillaya.

Now the really strange part:
The script DOES work when wow2/Zillaya is the active window and I press F10. In this case, I have wow1/Beregond follow me instantly. However, it does not work the other way around. If I press F10 with wow1/Beregond being the active window, nothing happens. This really is weird!

This is the output I get in HKN when I press the hotkey:

When I press F10 on wow1/Beregond I get this:

From this pc: <SendFocusWin><Key F10><SendWinM wow2><Key LCtrl F10>
    <SendFocusWin> completed
    <Key F10> completed
    <SendWinM wow2> completed: Window found. Target set to 0x701E2 "wow2"
    <Key LCtrl F10> completed

When I press f10 on wow2/Zillaya:

From this pc: <SendFocusWin><Key F10><SendWinM wow1><Key LShift F10>
    <SendFocusWin> completed
    <Key F10> completed
    <SendWinM wow1> completed: Window found. Target set to 0x3028A "wow1"
    <Key LShift F10> completed

I tried adding the <Wait 100> as suggested, but it did not change anything of the outcome at all. Any more ideas of what I can try?

[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.

[vorticone]

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."

I tested this by assigning Ctrl+F10 to jump on wow1 and Shift+F10 on wow2. When I now press F10 in one of the windows, the other character (the one not controlled) jumps. So the HKN mapping does work! So in fact it seems like my macro is somehow not correct, or I still have some key mapped to a different action. I will check this out now more thoroughly.

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.

I think we can rule this out since I am on WinXP. But I will keep it in mind since I will switch to Win7 some time later next month.

[vorticone]

YAY! I figured it out, thanks to you! It seems like Ctrl+F10 and Shift+F10 were bound to some WoW actions. That was the problem. One of my addons has this as a default hotkey, and I think I installed it after I started with my multiboxing. Very stupid mistake, but at least I have learned from it. A lot!

Thanks for your help, very much appreciated. Now all I have to do is to wait for my copy of Win7 64bit and my RAM modules to arrive and I can start with my five-headed hydra.

[Freddie]

YAY! I figured it out, thanks to you! It seems like Ctrl+F10 and Shift+F10 were bound to some WoW actions. That was the problem. One of my addons has this as a default hotkey, and I think I installed it after I started with my multiboxing.

Excellent! Grats on figuring it out.

Very stupid mistake, but at least I have learned from it. A lot!

Nah it wasn't stupid. When something doesn't work, it can be bewildering because there are dozens of possible reasons. In a case like that, it helps to have a systematic method for figuring out the real cause.

That's why I explained my reasoning in figuring out the little tests. That method can be used to debug many kinds of problems.

Now all I have to do is to wait for my copy of Win7 64bit and my RAM modules to arrive and I can start with my five-headed hydra.

Woot! Have fun.

[Freddie]

Deleted because posts crossed.