Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
This will create a series of toggle hotkeys saved into the user hotkey section. The user must then go in to the hotkey editor and assign the keys as they like.
There is also a default mapping for the hotkeys that one is able to use, but will overwrite any previously set hotkeys.
Re-writing the exact calls that the hotkey editor can perform such as querying if the key is valid, showing what is currently assigned, and custom mapping the commands is beyond the scope of this script. It seems foolish to re-write most of the editor when it is just as easy to use the editor.
The hotkey editor is called up by default if the user does not assign the keys, and is automatically forced to show the right category where the new commands will exist. Part of the hotkey editor script is appended into this in order to avoid sourcing the entire thing. I did take the liberty of hacking it down quite a bit.