Move all hotkeys to the accelerator user control

[tannerhelland]

Move all hotkeys to the accelerator user control

[tannerhelland]

I am temporarily postponing this as a new SetFocus trick seems to have resolved VB's ability to handle its own shortcuts. If it proves successful after more testing, it will save me a ton of trouble rewriting shortcuts that theoretically should already work.

[tannerhelland]

Recurring issues with VB's in-built accelerator behavior have motivated me to re-open this issue. Hoping to have all accelerators moved to the custom control before 6.0 releases. This may also make it possible to someday have a hotkey editor, so users can assign their own hotkeys to various items.

[tannerhelland]

Postponing until 6.2. If I'm going to do this, I may as well do it right and build the dedicated hotkey handler. The goal is to build a small class that associates hotkeys with processor strings (e.g. "Blur image"). This would allow the user to assign any arbitrary hotkey combination to any arbitrary action, which would be pretty damn great. :)

[tannerhelland]

(This has become the most confusing issue ever.)

After multiple reports from users about problems triggering hotkeys, I am bumping this back to 6.0. ARGH.

I've already reworked Steve's accelerator control to store and process parameters relevant to PD. Basically, a single LoadAccelerators function will store a menu reference (e.g. FormMain.BlurMenu), accelerator code (e.g. Ctrl and B keys), and relevant processor string (e.g. "Blur image"). Accelerator shortcuts will be automatically rendered to the relevant menu using the supplied accelerator (previously they had to be manually drawn).

When a tagged accelerator is pressed, that processor string will simply be forwarded to the software processor. This will cut a good deal of code, while also fixing the ongoing issues with VB and keyboard accelerators. It will also prime the program for a custom hotkey interface (though I obviously won't be implementing that for 6.0).