03-19-2020 03:57 AM
Decided to double check. Just having a custom menu (that does not need to be visible) is enough. There's no need to reassign CTRL+W, as long as there's no APP_CLOSE item. But if you do add APP_CLOSE, regardless the shortcut you give it, CTRL+W will close the windows.
So what works (the RT menu does not need to be visible):
1) Discard "Menu Selection? (App)" event (or just the APP_CLOSE item)
2) Create a RT menu that doesn't have an APP_CLOSE item
3) Create a RT menu that has an APP_CLOSE item, but CTRL+W attached to another item.
4) Catching and discarding key combinations ("key down?" and perhaps "key repeat?" events).
What doesn't work in an executable (but does work in the dev.env.😞
+ CustomShortcurt key (=";APP_CLOSE,") in the exe's ini file.
+ A RT menu with APP_CLOSE and no shortcut key, CTRL+W not assigned to another item.
03-19-2020 10:20 AM
Nice.
Did you try loading a runtime menu at runtime?
03-19-2020 10:44 AM
@zou wrote:
Nice.
Did you try loading a runtime menu at runtime?
Didn't even recall you can do that. I usually build my menus from a string. I don't like those rtm files.