Key mapping stops working after remote desktop connection.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Log on locally.
2. Log on from remote machine using remote desktop.
3. Log on again locally.

What is the expected output? What do you see instead?
The key mapping no longer works. I mapped capslock to ctrl, which after remote 
connection can only turn on capslock but not off.

What version of the product are you using? On what operating system?
Windows XP3. Most recent version of Keymapper.

Original issue reported on code.google.com by zhu....@gmail.com on 10 Mar 2011 at 10:20

[GoogleCodeExporter]

Hi

For my remote connections I set it up as both types of mappings - User and Boot 
mappings - as one way or another the remote connection wipes out my mappings; 
either they don't work in the remote session or they don't work afterwards. Use 
the Mappings menu to do this.

I map CapsLock to Ctrl, but I haven't seen behaviour like reported: I also 
disable NumLock, though, and after I have connected remotely it still gets set 
off so nothing surprises me.

Which reminds me - in the Toggle Lock Keys meny of KeyMapper you can change the 
current value of Caps and Num Lock, in case you have the key disabled but 
WIndows is using the wrong value.

As a defect, I'm not sure if this is fixable. There's a whole issue with 
Windows 7 - where per-user mappings simply don't work any more - and if there 
ever is a KeyMapper 2 it can take this into account.

--stuart

Original comment by stua...@gmail.com on 11 Mar 2011 at 12:20

[stuartd]

I log in remotely on a regular basis, and it has never affected stored my key mappings. Closing.