Quote:
Originally Posted by Wild.Bill.Kelso
Hmmm... Yes, I did miss that post, so I replied yesterday.. But I don't see my post! Maybe I didn't click submit??
Anyhow, the only thing I could think of is that maybe the Shift key is left pressed down by some other command. Is the Numpad 1 button the first one you try every time, or is there some other buttons you press first that may be leaving the shift key down?
In my FS9 profile there are several Shift keys used.
If TB is holding the Shift key down, then if you open notepad and type a letter: a, b, c... it should be in capital letters I would think. I just tried that with your 'Bingo' FSX profile and didn't get any caps. I also tried it with my FS9 profile, pressing buttons and the 'x' key and got this:
1xxxx7xxxxxxxxxxxxxxxxx7xx1xxxxxxxxxx1xxxxxxxx1xxx 7xxxxxxx1
No caps here, but of course I didn't press all of the buttons in the profile. I did search both profiles in notepad for the 'shift' command and didn't see any of them left down. But it appears my FS9 profile does send the numpad 1 and seven keys to notepad just fine.
Have you tried just making a simple profile with only these 2 trim buttons in it? That should be a good test on your 'pristine' FS9 computer.
WBK
|
WBK,
Thanks for your response!
I tried this command sequence (but not on my pristine system) and I did not find any evidence of the Shift key being held depressed. It was also the first command attempted. I verified this by only being able to type the lower case characters, I got no capital letters.
I did notice, that when pressing the touch buddy buttons, it would send either a "1" or "7" to Notepad no matter if the NUMLOCk key was on or off. If I purposely held down the shift key, nothing was sent to Notepad. However, Notepad would show either a 1 or 7 when TB sent characters if the SHift key was not depressed.
I will set up my "pristine" system again, but I believe I will get the same results.
This one is wierd,
Bill