Posted 17 years ago by Keith Hill
We've run into a bit of a problem with keyboard shortcuts. If your command leaks an exception it brings down the whole process since it executes in the context of message processing (which causes Application.Run to exit). It would be nicer if the keyboard shortcut handling posted a custom message (WM_USER+xx) to some Actipro window and in that window's wndproc you raised the command. Then if the command leaks an exception, we could catch that via the Application.ThreadException event and the application could continue to run.