User guide

53
3. Change to: debug = true
4. Rename autorun.bas file to “run.bas” for example, so it doesn’t start automatically
a) If you are testing a playlist, the main playlist must be named “autoplay.bsp”
b) If you are testing a .csv file, it must be named “autoplay.csv”
5. Insert your CF card into the BrightSign, and add power
6. At the Roku prompt, type the following:
script run.bas
Testing Custom Scripts
To make troubleshooting your custom scripts much easier, we recommend adding checks
and print statements like those found in the autorun.bas script. Here are a few examples:
• Add print statements telling you which portion of the script you are currently in
• Add print statements showing the type of event that just occurred
• Add print statements showing names of files read from the flash card
• Add print statements showing the coordinates of a mouse click
To begin testing your custom script:
1. Copy your content and script file to the compact flash card.
2. Name your script run.bas. You can call it anything, as long as it’s not autorun.bas,
so it doesn’t start automatically.
3. Add a debug statement to the top of your script, like the autorun.bas. Now, we’ll see
output from the print statements you added to your script.
debug = true
4. Insert your CF card and Add power to the Brightsign.
5. At the Roku prompt, type the following:
script run.bas
Mult-run Script Limitations
Currently when a script terminates, it does not free resources allocated by Roku Objects.
This means that if you use the “script” shell command to run a script, and the script exits,
you may not be able to run it again successfully. You will need to reboot your
BrightSign between script tests.