| Build-A-Board®: for Windows; The Next Generation of Onscreen Keyboards; Version 2.20 Release 3; User's Guide | ||
|---|---|---|
| Prev | Next | |
These are the generic commands available for the Windows targets. As of the Version 2.20 Release 3, a full inventory of every command, its support on targets, and syntactic differences is not currently available. Check for updates, and with IMG technical support if there is a need beyond CLOSE, MINIMIZE, SAVEPOS, and NKBF on non-Windows platforms.
There are various commands (available in the Macro Builder):
[CMD:CLOSE] - When this is the Key Action, My-T-Soft will close.
[CMD:MINIMIZE] - When this is the Key Action, My-T-Soft will Minimize to the Tray (Shell icon).
[CMD:SAVEPOS] - When this is the Key Action, My-T-Soft will Save the current position to the KBF file (This will not work if the Window, Panel, Button, and Key file option is selected in Global Settings). Once the position is saved, the saved top, left setting will be used when this layout is opened in the future.
[CMD:NKBF=???.KBF] - When this is the Key Action, the ??? must be replaced by a valid Keyboard File (KBF File). For Example, the Command might be [CMD:NKBF=NUM.KBF]. If there is a NUM.KBF file in the same folder as My-T-Soft, this will change the currently displayed keyboard layout to the specified "new" keyboard layout.
[CMD:EXEC=???.EXE] - When this is the Key Action, the ??? must be replaced by a valid executable file. For Example, the Command might be [CMD:EXEC=NOTEPAD.EXE]. The following logic is used internally to run the named executable file: The current directory where the MYTSOFT.EXE is being run from is checked first - if the file is found, then it is run from that location. Otherwise, the file specified is handed off to Windows - Windows will search the the Windows folders, and then the path to find the file - if found, it will be run. If the file is not found, or there is an error, no other action will occur. The internal Windows API called is "ShellExecute", so a wide range of files can be run with this command - you can specify Bitmap files (.bmp), Documents (.doc), Shortcut files (.lnk), etc. For command line entries, and other properties, use a shortcut, then specify the shortcut as the EXEC file. Note that for Level 1 keys, there is a limit of 31 characters, so only a limited path could be used (e.g. [CMD:EXEC=C:\UTIL\ACTION.BAT]). When a long path is required, use a shortcut, and put the shortcut into the folder with MYTSOFT.EXE.
[CMD:SND=???.WAV] - When this is the Key Action, the ??? must be replaced by a valid Wave file name. The following logic is used internally to run the named wave file: The current directory where the MYTSOFT.EXE is being run from is checked first - if the file is found, then it is run from that location. Otherwise, it is handed off to Windows - Windows will search the Windows folders, and then the path to find the file - if found, it will be run. If the file is not found, or there is an error, no other action will occur. The internal Windows API called is "sndPlaySound" and any valid wave of multimedia file supported by that function will be played. Note that for Level 1 keys, there is a limit of 31 characters, so only a limited path could be used (e.g. [CMD:SND=C:\SNDS\ACTN.WAV]).
[CMD:MIDI=???.MID] - When this is the Key Action, the ??? must be replaced by a valid MIDI file name. The current directory where the MYTSOFT.EXE is being run from is checked for the file - if the file is found, then it is run from that location. If the file is not found, or there is an error, no other action will occur. The internal Windows API calls use the MCI commands with the MIDI device setup as the "sequencer". Note that for Level 1 keys, there is a limit of 31 characters, so only a limited path could be used (e.g. [CMD:MIDI=C:\SNDS\SQNC.MID]).
[CMD:MIDI=STOP] - When this is the key action, the MCI command will be used to send a STOP command to the device previously used to Play a MIDI file (i.e. [CMD:MIDI=???.MID]).
As seen in ...
