Using the lock keyboard object tag parameter

This PARAM NAME and VALUE pair is optional. If set to Yes, the BlueZone session keyboard state is initially locked when the session launches.

In an application where you are launching a BlueZone session from a web page via an object tag, and you are automating the session after it launches through a web page script, or when the BlueZone session itself is auto-playing a script or macro, you may find it desirable to lock the keyboard to prohibit user input during session startup and automation.

To accomplish this, the above <PARAM NAME="LockKeyboard" VALUE="Yes"> parameter can be manually added to the object tag to initially set the keyboard state to locked. When a session’s keyboard is locked, all user keyboard input is ignored.

Additionally, to unlock the keyboard, an external process can call the .LockKeyboard( False ) method of the BlueZone Host Automation Object. However, if BlueZone is playing a script or macro, BlueZone will auto-unlock the keyboard when the script or macro completes.

Refer to the BlueZone Host Automation Object Help, located in the BlueZone Advanced Automation Guide, for more information on BlueZone scripting.

Refer to Scripting parameters for information on other object tag parameters that can be used in conjunction with BlueZone scripting.