I’m trying to launch a particular window whenever a key is pressed, by putting fpmi.nav.windowName in a Global Event Keystroke script. I’ve found that the key press doesn’t work unless the user first interacts with a control on the window or clicks on the runtime menu bar at the top of the window first.
Is there any way to correct this behaviour?
You mean after they login, but before they click on anything, the key actions don’t fire?
After they open a window, they have to interact with it (or the menu bar) in some way before the key actions fire.
hrm…I’ll have to replicate this and investigate. You can try to programatically give input focus to the window in the internalFrameActivated script using event.source.requestFocusInWindow()
This only seems to be a problem when launching a system as an applet (Firefox and IE8).
Ah, that makes sense. Applet mode has been known to act a bit differently than the traditional launch mode. In this case, my guess is that the browser itself is getting the keyboard input until the user directs it to the applet by clicking inside. If this is the case, it might be hard for us to “fix”. We’ll look into it.