Suggest: Remove original Key Map on [ Change ]

I love this update in 14b7: "Settings such as keyboard shortcuts and panel sensitivity controls are now stored locally on the machine instead of with the project." Fantastic!

However, I had somehow maintained my custom hotkeys from 12.5 through 14b6. But today, with this change, I'm now stymied by the error "S is already in use by editToggleSlipSlide" which has already been reported a few times; examples:
f=31&t=62084&p=352485
f=21&t=59707&p=342545
f=21&t=59707&p=342160

While adding Toggle Slip/Slide to the Hotkeys edit interface would be one way to solve this particular issue, I would also like to suggest that when we make a Keyboard Map change, if we press the [Change] button it remove the key from whatever it is was originally/currently mapped to. This will take care of missing Key Map options and make remapping easier and cleaner overall. As is, if I change something, I then have to go find and delete the original. It'd be awesome if the system took care of that for me.

Thanks for considering!

~Luke

That's an excellent suggestion.

Agreed

Current workaround is to export the keyboard mapping, edit the offending item, and reimport.

when we make a Keyboard Map change, if we press the [Change] button it remove the key from whatever it is was originally/currently mapped to.

I'm a little stymied how this doesn't already happen. C'mon BMD, these little stupidities aren't acceptable, not even in a beta.

Current workaround is to export the keyboard mapping, edit the offending item, and reimport.

Brilliant, Trevor. Thank you!