About The Scriptsdk Main Window - Quantum Data 881 User Manual

About the ScriptSDK main window

882 Video Test Instrument User Guide (Rev. A.35)
Writing to a log file
In some applications you may wish to write data out to a text file for later examination. For
example you may want to create a script that measures the timing parameters of an
incoming HDMI signal and write them out to a file. Starting in Release 2.19 you can do
this. You will need to include three extern declarations at the top of the script:
extern int fopen();
extern int fclose();
extern int fprintf();
You will also need to include a File* declaration which points to a path where the log file is
stored. Examples are shown in this chapter.
Halting a script through the front panel during execution
When a script is executing, the top right soft key on the 882 is assigned to the STOP
function. If the STOP key is pressed, the sc.Canceled() method will return true. The script
must check this state in order to detect whether the STOP key has been pressed. A script
should always return true when exiting. See example programs testapi.cpp and tcan.cpp.
Some scripts may take over the top right soft key so it is not available for the STOP
function. The example program testapi is an example of this. Therefore, the generator's
OPTIONS key is always available to interrupt scripts that are running. After pressing the
OPTIONS key, pressing the bottom left soft key (!Yes) will stop the script.
The Quantum Data SDK GUI is shown below. It is centered around the text editor. The title
bar at the top indicates whether the program is currently set for ScriptSDK or ImageSDK.
Beneath the title bar is the menu bar, featuring pull-down menu categories of File,
Compile, Load&Execute, and Connection. The menu bar also contains a button for
toggling between ScriptSDK and ImageSDK modes.
447