A number of ways exist to run a Binary Template. The easiest is simply to open a file and if 010 Editor has a Binary Template installed for that type of file the Template will be run automatically. 010 Editor comes preinstalled with Binary Templates for BMP, WAV, and ZIP files but other Templates can be installed (see Template Options or the Repository Dialog for more information). Templates can also be run by clicking on the name of a Template in the 'Templates' menu (Templates can be installed on this menu using the Template Options dialog or the Repository Dialog), or by using the Debug Menu.
Another method of running Binary Templates is to use the File Bar above each editor. When editing a binary data file, the File Bar will contain sections marked Run Script and Run Template as shown above. Click the Run Template area to display a drop-down list of Installed Templates, Open Templates, and Recent Templates. Click on a Template name in the list to execute that Template on the current file. Once a Template has been selected for a file, the Run Template area will indicate Run Template: <template_name> followed by the icon . Click this icon or press F5 to rerun the template.
At the bottom of the drop-down list are four icons which can be used for creating a new Template, opening a Template, editing the Template associated to this file, or editing the list of Installed Templates, respectively. Note that the drop-down list can be resized by clicking and dragging the handle at the bottom-right corner of the list and 010 Editor will remember the chosen size.
Templates are currently run in a separate thread, meaning the editor can still be used while a Template is running. Only one Template or Script can be run at a time and the current Template or Script must be stopped before another can be run. To stop a running Template click 'Templates > Stop Template' or press Shift+Esc.
When editing a text file that is not a Template or Script, the File Bar will contain the sections Run Script and Syntax. Use the Syntax section to choose which Binary Template to use for Syntax Highlighting as described in the Using Syntax Highlighting help topic.
When editing a Template (the Edit As area will display Edit As: Template) the File Bar will now contain the section Run on File as shown above. Clicking the Run on File area will display a list of all files currently open, but will not include any Scripts or Templates. Click a file in the drop-down list to run the current Template on that file. Once a file has been selected, this area will indicate Run on File: <file_name> and clicking the icon or pressing F5 will rerun the current Template. Clicking the Open icon at the bottom of the drop-down list allows opening a file and then immediately running the current Template on that file. The Repository section of the File Bar is discussed in the Repository Menu help topic.
If an error occurs while running a Template, an error message will be
displayed in the Output tab of the Output Window and a dialog will ask to start the debugger. Double-clicking on an error message in the Output tab
will move the cursor to the line where the error occurred.
Templates can also be run using the Command Line. Once a Template has been run the Working with Template Results help topic describes how to use the results.
Similar to running Templates, Scripts can be run by clicking on a script name in the 'Scripts' menu (see the Script Options dialog for information on placing a Script on this menu plus a list of all available scripts). Also, through the same dialog Scripts can be set to run when a certain file type is opened or can be set to run automatically on application startup or shutdown. See the Repository Dialog for information on installing Scripts that other people have submitted to the repository.
Alternately, Scripts can be run using the File Bar at the top of each editor. When editing a file that is not a Script or Template, the File Bar will contain two sections marked Run Script and Run Template. Click the Run Script area and select a script from the list of Installed Scripts, Open Scripts, or Recent Scripts to run that script on the current file. After a Script has been selected for a file, the Run Script area will display Run Script: <script_name> followed by the icon . Click this icon or press F7 to run the script again.
At the bottom of the drop-down list four icons exist. These icons can be used for creating a new Script, opening a Script, editing the Script associated with this file, or editing the list of Installed Scripts. The drop-down list can also be resized by clicking and dragging the handle at the bottom-right corner of the list.
Scripts are run in a different thread, meaning editing can still be performed while a Script is running. Only one Template or Script can be run at a time and the current Template or Script must be stopped before another can be started. To stop a running Script click 'Scripts > Stop Script' or press Shift+Esc.
If the current file being edited is a Script (the Edit As area will display Edit As: Script) the File Bar will now display a section Run on File. Click the Run on File section and select a file from the drop-down list of all open files to run the current Script on that file. Some Scripts may be run without a target file by clicking the icon or by selecting '(none)' from the drop-down list. After a file has been chosen, this area will show Run on File: <file_name> and clicking the icon or pressing F7 will rerun the current Script on the selected file. The Open icon at the bottom of the drop-down list can be used to open a file and immediately run the current Script on that file.
If an error occurs while running a Script, an error message will be
displayed in the Output tab of the Output Window and a dialog will ask to start the debugger. Double-click an error message
to view the line where the error occurred.
Scripts can be run using the Command Line as well. After a Script has been run (and assuming the Script is loaded in the interface) select the Script and click on the Variables tab of the Inspector to view the variables created by the Script.