GxInspect has no way to press keys. Testing a GExperts feature that hooks Ctrl+C and Ctrl+X through the ToolsAPI's keyboard bindings needed real key presses, because such a binding only fires on keys that go through the IDE's own key handling; calling code or posting WM_KEYDOWN does not test that path. The tests used a PowerShell script with keybd_event instead.
Proposed syntax: KEYS <form-id> [<control-name>] <keys>, with keys written the way TextToShortCut reads them (Ctrl+C, Ctrl+Shift+F5, Esc) and several separated by spaces. It brings the form to the front and focuses the control (the edit control for an editor window) before pressing them.
Traps found while doing it by hand:
VK_F24) worked. The server runs inside the IDE, so it may be able to bring its own window to the front without any trick.TEditWindow), not part of TAppBuilder.The answer should say which window had the focus when the keys were sent.