I have several custom functions and hotkeys defined inside the .InitializeFunctions procedure in my Custom Library. Everything has been working great.
I recently defined a new hotkey which triggers a Custom Statement from the same custom library. This is generating an error message when opening panorama.
The .InitializeFunctions procedure is running before the statement is registered. The result is the hotkey not being defined, but the custom statement being registered successfully. If I then manually open the custom library, the hotkey is defined as expected. Has anyone else encountered this situation?
Is it a solution having a Custom Library that registers Custom Statements first and then a second one running the .InitializeFunctions procedure?