|
|
 |
| Minimize a keyboard using a timer and scripting |
 |
| Minimizing a keyboard after a certain length of time with no keyboard input is very simple using a script procedure. |
| Changing event handlers at runtime |
|
| In some circumstances you may want different event handlers for the same event to be in effect depending on some external factor. For example, you may want a key to cause a page change to page x, but in some cases page y instead. There are many (simpler) ways to do this, but we’ll use this as a basis to demonstrate how you can change the event handler for a given event at runtime. |
| Scripting indicator state objects |
|
| Indicator state objects are named non-visual objects used to monitor different states. Think of them as “switches” that can be either on or off. The Runtime Keyboard automatically updates the states for the three built in indicator states – Caps Lock, Num Lock and Scroll Lock. The state of user defined indicator state objects must be maintained by either the keyboard itself through scripting, or an external application through COM. |
| Understanding the structure of the keyboard objects |
|
| This article gives a quick background explanation of the keyboard objects and the design decisions that have been made in the development process. |
| Using event handler parameters |
|
| Most of the events defined have only one parameter, Sender, however some events have more parameters to further describe the event that has occurred. In all, the keyboard objects use three different event types as described in this article. |
|
