Shift 2 not creating '@'

When I switched to battle.net login I noticed the following problem:

Typing Shift-2 works in game fine (switch to my 2nd action bar) but in the login screen it does @ on focused window and 2 on the others

Example of output of "show hotkey definition" when I type shift-2 :

<Hotkey Shift 2>
<SendPC local>
<SendWinM WoWtrio1>
<Key Shift 2>
<SendWinM WoWtrio2>
<Key Shift 2>



my script looks like

<KeyList ExList W, A, S, D, Q, E, 9, Enter, X, Space>
<KeyList MyList Period, B-C, F-P, R, T-V, Y-Z, 0-8, F1-F12, Tab, Comma, Esc, Backspace, Minus, Plus, Oem1, Oem7, Oem4, Oem6, Oem2, Home>
<Hotkey MyList; Shift MyList; Alt MyList; Ctrl MyList>
<SendLabel w0, w1>
<Key %Trigger%>




ps: it'd be so great if the admins could fix the damn UI so firefox "source code" mode doesn't have an empty first section that loose all your work when you hit submit after typing a long post in there - make the "source" frame uneditable or something or put focus into the second one; or put source at the bottom instead of the top; or no empty useless frame at all...

Quote:

---

Originally Posted by 'Moorea',index.php?page=Thread&postID=193567#post1 93567

ps: it'd be so great if the admins could fix the damn UI so firefox "source code" mode doesn't have an empty first section that loose all your work when you hit submit after typing a long post in there - make the "source" frame uneditable or something or put focus into the second one; or put source at the bottom instead of the top; or no empty useless frame at all...

---

The input box where you type out your posts? Yeah, can't change that, but I can let you know that change is on the way and this won't be an issue soon.

This is due to unfinished work. Some of the background modes always send shifted characters; others always send unshifted characters. The problem is documented in many places on HotkeyNet's website including the top of the list of unfinished features:

Known bugs and incomplete features.html

I recently started revising the background modes so they do this properly. I think SendWinS and SendWinSF are now handling this properly but only in the special test builds where the new work is getting introduced. You can download the latest test build (169-5) here:

Test build 169-5

If you decide to try the test build, please be aware that you may have to adjust a few things on the new Send Mode Settings panel. You may have to check a box there to turn on the new version of SendWinS .

thanks for the quick reply freddie - I'm not quite clear on what I would need to do to get it to work if I try the test build - should I change my SendWinM to SendWinS - which settings/checkboxes exactly are you referring too ? unless you need help reproducing/testing this maybe I'll wait for the stable release as now that I typed @ manually and remember login I don't really have an urgent problem (it's not like it breaks in game)

That's fine, you might as well wait. I'm planning to merge the new stuff into the regular builds very soon. (Yes you would have needed to change SendWinM to SendWinS in your script.)

I am guessing passing modified keys to HKN is also unfinished? I bound my mouse button to CTRL + ALT + F2 and it appears to send Just an F2 to HKN while CTRL + ALT + F7 sends CTRL + ALT + F7.

When you say "passing to HKN" do you mean using these keystrokes in a trigger like this?

Code:

---

<Hotkey Ctrl Alt F2>

---

That has always worked, so far as I know. Can you tell me more about the problem?

It's only output from HotkeyNet that's unfinished. In other words, the <Text> and <Key> commands are unfinished.