Wierd HKN problem (capitalization, modifiers)

[Fuzzyboy]

I'm experiencing the wierdest problem at the moment. When I have HKN enabled, sometimes the application just doesn't seem to send the right modifier. For instances when I type <shift> + q repeatedly in a notepad (or in the wow client chat box), the output is like this:

qQqQqQqqqQqQQQqqqqqqqqqqqqqQQQQQQQQQQQQQQQQQQQQQQQ QQQQqQQQQQQQQqQQQQQQqqqqqQQQQ

In the HKN applications, the keypresset sent are always correct, i.e.:

From this pc: <SendFocusWin><Key Shift Q>
<SendFocusWin> completed
<Key Shift Q> completed

But the output simply isn't always correct. At first I thought it might be my keyboard that was something wrong with so I tried another with the same result. Is this a known issue? I've attached the script I use:

//-----------------------------------------------------------
// SUBROUTINE TO RESIZE AND POSITION WINDOWS
//-----------------------------------------------------------

<Command ResizeAndPosition>
<SendPC %1%>
<SendWin %2%>
<SetWinSize %3% %4%>
<SetWinPos %5% %6%>

//-----------------------------------------------------------
// SUBROUTINE TO LAUNCH AND RENAME A COPY OF WOW.
//-----------------------------------------------------------
<Command LaunchAndRename>
<SendPC %1%>
<Run %2%>
<RenameTargetWin %3%>
<RemoveWinFrame>

//-----------------------------------------------------------
// HOTKEY TO LAUNCH AND RENAME THE WOW WINDOWS.
//-----------------------------------------------------------
<Hotkey Alt Ctrl L>
<LaunchAndRename Local "c:\WoW\Moonkin\Moon1\WoW.exe" WoW1>
<LaunchAndRename Local "c:\WoW\Moonkin\Moon2\WoW.exe" WoW2>
<LaunchAndRename Local "c:\WoW\Moonkin\Moon3\WoW.exe" WoW3>
<LaunchAndRename Local "c:\WoW\Moonkin\Moon4\WoW.exe" WoW4>
<LaunchAndRename Local "c:\WoW\Moonkin\Moon5\WoW.exe" WoW5>

<ResizeAndPosition Local WoW1 1920 1200 0 0>
<ResizeAndPosition Local WoW2 800 600 1920 0>
<ResizeAndPosition Local WoW3 800 600 1920 600>
<ResizeAndPosition Local WoW4 800 600 2720 0>
<ResizeAndPosition Local WoW5 800 600 2720 600>

//-----------------------------------------------------------
// DEFINE A MAIL LABEL FOR EACH WOW
//-----------------------------------------------------------
<Label w1 Local SendWinM WoW1>
<Label w2 Local SendWinM WoW2>
<Label w3 Local SendWinM WoW3>
<Label w4 Local SendWinM WoW4>
<Label w5 Local SendWinM WoW5>

//-----------------------------------------------------------
// DEFINE MAIN KEY LIST
//-----------------------------------------------------------

<KeyList MyList AllMainKeys except Tab, pause, up, down, left, right, a, w, s, d, NumLock, ScrollLock>

<Hotkey MyList; Shift MyList; Alt MyList; Ctrl MyList>
<If ActiveWinIsNot WoW>
<SendFocusWin>
<Key %trigger%>
<Else>
<Sendlabel w1,w2,w3,w4,w5>
<Key %trigger%>

//-----------------------------------------------------------
// DEFINE MOVEMENT KEYS
//-----------------------------------------------------------

<MovementHotkey ScrollLockOff up, down, left, right, a, w, s, d, Oem5>
<Sendlabel w1,w2,w3,w4,w5>
<Key %trigger%>

<Hotkey ScrollLockOn a, w, s, d>
<If ActiveWinIsNot WoW>
<SendFocusWin>
<Key %trigger%>
<Else>
<Sendlabel w1,w2,w3,w4,w5>
<Key %trigger%>

//-----------------------------------------------------------
// DEFINE SPECIAL KEYS
//-----------------------------------------------------------
<Hotkey pause>
<sendpc local>
<ToggleHotkeys>

//-----------------------------------------------------------
// DEFINE MOUSE CLICKS
//-----------------------------------------------------------

<Hotkey LCtrl LAlt LButton>
<Sendlabel w1,w2,w3,w4,w5>
<ClickMouse LButton>

<Hotkey LCtrl LAlt RButton>
<Sendlabel w1,w2,w3,w4,w5>
<ClickMouse RButton>

[Freddie]

This problem is documented in many places on HotkeyNet's website including all the pages about background send modes such as SendWinM and on the page called "Known bugs and incomplete features."

There are work arounds for the problem but please note, many people think sending chat-line commands to WoW from hotkey programs is a violation of the rules.

[Fuzzyboy]

Thanks for the reply (which is both fast and accurate considering it's free software). I don't really care about the capitalization thing since I pretty much always mute when I type on my main, it's more the special characters such as "/", "(", ")" that worries me since those are important for typing script commands in all 5 windows, but I appreciate the reply and I'll see if I can fix it. Thanks :-)

[Fuzzyboy]

There are work arounds for the problem but please note, many people think sending chat-line commands to WoW from hotkey programs is a violation of the rules.

Really? How is that different from typing the command into a macro, mapping the macro to a button and using a hotkey program to send the keystroke mapped to the button? People are odd :-)

[Freddie]

I won't try to explain their reasoning since I'm not sure I understand it. But many people here are convinced of this and vehement about it.

The issue is really whether the target application interprets keystrokes as shifted or unshifted, so the work arounds apply equally to special characters and to capitalization.