31
Syntax Example 9. The Volume Down key location (keypad layer) plays the “Page up” action, delays 500 ms,
then plays the “home” action.
{vol-}>{pup}{d500}{home}
Syntax Example 10. The Hyphen key plays “F1” then delays one second (1000 ms = 500ms +500ms), then
plays the “mute” action.
{hyphen}>{f1}{d500}{d500}{mute}
Incorrect syntax or language
If incorrect syntax or language is used in a layout configuration file, the keyboard will usually resort to the
default action for that Location Token. However, in some cases pressing a key that has invalid programming
may not produce any key action at all. If problems arise, remaps and macros can be erased manually by
direct editing the problematic lines of “code” in the layout configuration file or by reversing any custom
programming using the appropriate onboard programming shortcuts, examples below.
Note: If multiple
remaps are assigned to the same Key Location, the keyboard will typically output the lowest line of code.
Restoring a key to its original action
Enter Program Remap Mode (progm + F12) and tap the target key twice– once to set it as the Source action
and once more to set it as the Destination key.
Erasing an existing macro
Press Program then F11 to enter Program Macro Mode, then tap the trigger key(s). Instead of recording
macro content, simply tap the Program Key to record an “empty” macro” and exit Program Macro Mode.
“Commenting Out” language in a layout file
If you wish to temporarily disable a specific macro or remap in a given layout, it is possible to simply add an
asterisk (*) in front of the appropriate line of code in the .txt file. The asterisk will cause that macro or remap to
be bypassed by the keyboard. To reactivate that macro/remap simply delete the asterisk, save the file, and
close the v-drive.
Storing notes in a layout configuration file
While it is possible to store notes and other “non-programming” text/language within a layout file, Kinesis
does not recommend doing this as it may have unintended consequences. Proceed at your own risk.
Tricks for fixing win-triggered macros
As mentioned in section 6.12, macros that use a Windows key as the only modifier to help trigger a macro
may need special optimization to play correctly. If you have trouble getting such a macro to play correctly at
the default playback speed (speed3) or if you want it to play back at a faster speed, try one of these tricks
using direct editing of the macro.
1. Place “
{d500}{escape}
” at the beginning of your macro contents
Example plays back “hello:” {rwin}{1}>{d500}{escape}{h}{e}{l}{l}{o}
2. Place “
{d500}{-win}{+win}{escape}
” at the beginning of your macro contents.
Example plays back “hello:” {rwin}{2}>{d500}{-win}{+win}{escape}{h}{e}{l}{l}{o}
Changes don’t take effect immediately
Changes made to a layout configuration file will not take effect until the .txt file is saved to the Active folder
and the v-drive is closed/unmounted. The drive can be unmounted either by using the onboard shortcut
(progm + F2) or by re-plugging the keyboard.
Note: To implement layout changes without closing the v-drive,
save the layout file and then use an onboard shortcut load a different layout. When you switch back to the
recently saved layout, that new layout file will be read by the keyboard and your changes will be implemented.