I think I raised this before, without getting a very useful answer.
I would love to be able to extract the information contained in the Shortcut mapper in a form that could be manipulated - because I would like to order the information by hot-keys rather than by actions and general topic. In that way it would be easy to discover which hot-key is masking some desired action.
I'd be quite happy to access an API to get this information into a plugin, or a way to copy all the mapping information to a file.
This is something which I have been wanting for a long time already.
I would love for this to be considered and updated.
If we are taking a vote - You have mine!
Why is this information so hard to get at!
What kind of API did you have in mind? For a plugin? I once considered rewriting the shortcut mapper, but thought that it was too much work. An API which returns a copy of the entire shortcut structure, plus another API which allows a plugin to change shortcuts, could probably be done < 50 lines of code...
Are you talking about something that can be done in a plugin, or something that requires changes to the source? Obviously anything is possible if you hack the source, but I would like a way to access the data to create a plugin command!
It can't be in a plugin right now (as far as I know), so it seems like a natural step to add an API so plugins can get/change shortcuts.
Keyborad mappings used to be saved to a file named shortcuts.xml, which you can parse to get that info. However, I recently installed a fresh Notepad++ 6.5 version and my mappings seem not to be read nor saved to such file anymore. Would such file be enough for the plugin you have in mind?
shortcuts.xml is still used to save the mappings (it's in AppData\Roaming\Notepad++). The problem is that it doesn't show all shortcuts, only those the user has changed.
If you install a plugin, does that count as a change? If it does, I suppose one could start from a list of shortcuts typed in manually, and overwrite them with the changes. At least that way, you could identify what was interfering with what - even if you had to use the Shortcut mapper to fix it. A plugin could also move its own shortcuts to ensure they were visible.
Hi, David, Davey, Andreas, Iñaki, and All,
As for me, I solved the problem of a complete list of shortcuts, in my N++ configuration, by creating an Excel file, which contains 10 columns :
The group Reserved contains all reserved Windows shortcuts, NOT to be used by user, as Ctrl + Alt + Suppr, Alt + Tab, Shift + F10,...., and of course, the only hit on an alphabetic or number key, for example !
The suppressed state of a shortcut concerns a default plugin, part of the original version, that the user don't use any more
If a command/function is described on ONE line, of this Excel file, that means that THIS default shortcut of N++ has not been changed, yet.
If a command/function is described on TWO lines, that means that, for this specific command/function, :
Then, while using the option Automatic filter of Excel, it's very easy, for example, to see all the shortcuts which use the alphabetic key Y, OR all the shortcuts which use, both, the ALT et CTRL keys and their corresponding commands, or even to look for a specific combination, for example, Alt + Shift + F7, and verify the possibility of 2 or more commands/functions, attached to this Alt + Shift + F7 shortcut !
You can also sort this Excel list of shortcuts, in many ways !
This Excel file was realized with the last 5.9.8 ANSI version of N++ and contains 1070 lines about which corresponds to a set of 730 commands / functions, relative to N++, to the 35 created macros and to the 36 installed plugins on this ANSI configuration.
I haven't updated this Excel file, on my current 6.5 UNICODE version of N++ yet, because I'm always, in test phase, with up to 63 unicode plugins, installed on this configuration !!!
Of course, such a file is quite difficult to create, at beginning, but, afterwards, it doesn't really change, except when you add or delete a plugin / macro or when new options are added in a new version of N++ :-)
However, I agree with you, that the actual form of the shortcut Mapper could be improved !
BTW, as the number of possible plugins is quite important, on the UNICODE configuration of N++, could it be possible to use the Windows key in shortcuts? With that possibility, we would have plenty of new shortcuts, which wouldn't interfere with existent ones !
Of course, Microsoft OS ( Windows XP, W7 and W8 ) already use few Windows key shortcuts, like Windows + E, Windows + R ,..., which, certainly, would have priority to our N++ shortcuts !
What do you think of my suggestion ?
There is some discussion about it in the Plugin Development forum.
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.