In both the 2.6.4.2 release and the 2.7.0.0 beta 1A, P2ATC does not recognize the "3 / #" key in a couple of the windows.  If, for example, I open the config window and try to change the callsign to "American 315" it misses the '3'.  Same thing if I try to fill in a flight level like FL350 in the "Sayit" dialogue window.  If I type in the speech text window (lower right hand corner) it sees the '3' key input just fine, as do any other programs on the PC.  This is the key on the top row of the keyboard--the '3 / PgDn' key on the numpad works normally.

 

This sounds like that key is mapped as a HotKey in either P2A or some other application on your PC and the key is not being sent to P2A. 

I don't know why it would work in the Speech Text window and not any others, but it does work in all windows in my environment.  Sorry I can't think of any other explanations.

 

It's really odd...if I turn on the caps lock, it works again, and if I turn caps lock off it keeps working until the window is closed...when I reopen the config or SayIt window the '3' key is not recognized until I hit the caps lock again.

Does the same thing with the Windows virtual on-screen keyboard, so it's not a hardware issue.

Only other user app running at the time is Wideclient.

That is strange.

The only other thing I can think of is to delete the AppConfig file that holds all the P2A HotKey assignments, along with all the other Config settings.  This will set all settings to default values and create a new file the next time you start P2A. 

You'll have to reset all your settings, but at least it will guarantee there are no HotKeys set in P2A.

The AppConfig.xml file is located at:
c:\users\<UserName>\AppData\Roaming\P2A_200\Settings\AppConfig.xml
where <UserName> is your PC user name.
Dave

Dave--I figured out what's causing this.

It was a hotkey issue, but it's being caused by a bug in the hotkey assignments in P2ATC.  I had a hotkey assigned for the SayIt button, CTRL-3.  When I click "Set" in the Config->Btns dialogue, a small set key window opens up, I press CTRL-3 and it shows up in the dialogue as "ctl-D3"  I press the "set" button and the window closes.  In the SayIt hotkey section in the Config -> Btns window, now there's a key code of "D3", not "ctl-D3"  D3 is apparently the keycode for "3".

So the hotkey assignments are being saved with the key modifiers (CTRL, SHFT) stripped off.  The same problem exists if I try assigning "SHFT-3"--it gets saved as "D3" without the modifier.

Thanks Bob.  I'll have a look and see what's going on.

Dave