Compiling and Running a Script

Compiling and Running a Script

Run Will both compile and run the script unless it contains syntax errors, in which case it stops with an error message when compilation fails. Debug Starts the JavaScript debugger, JaDe to debug the script. Check Only compiles the script, reporting any errors found, and does not run it. Encrypt A script can be encrypted so that the source code is hidden but the script can still be run (when compiling and running the script PRIMER decrypts the file in memory). Once encrypted the source code cannot be retrieved by an ordinary user so make sure that you keep the original file somewhere safe. As a last resort contact Oasys Ltd Support, who can decrypt the script if required. If a script is split up into separate files by Use the files are all combined together into the main file before encrypting. Merge If a script is split up into separate files by Use the files are all combined together into a single file. This may be useful if you want to give the script so someone else and you do not want to have to give lots of different files. GUI Builder Opens the GUI Builder to interactively build GUIs for your script. Running Enables you to view (and kill) any scripts that are currently running

Prior to version 22 a memory textbox was available to set the memory allocated for garbage collection in the JavaScript engine. This has been removed in version 22 as the memory is now automatically expanded as required. Please see the garbage collection section for more details.

Initially the Run , Debug ... buttons will be greyed out. If you type a script location into the text box or select the location using the 'folder' button they will be enabled. Alternatively left clicking on a script in the tree will automatically run the script. Right clicking on the script will bring up a popup menu with the Run , Debug ... options.

Knowing which scripts are running

When scripts are running in PRIMER, they are shown in the Running submenu.

Use the Running button to toggle between the list of scripts that are currently running, and the tree of available scripts.

To kill/terminate a running script, highlight the script(s) in the tree and press Kill.

Alternatively, to kill all the scripts that are currently running use Kill all.

File encodings for scripts

Version 10.0 of PRIMER introduced the ability for unicode text to be used on widgets created in a script. Previous versions of PRIMER only supported English text so the default ASCII encoding was used for script files (this is still the default encoding for script files).

If you want to use unicode text in widgets then you must use a file encoding that is capable to representing the unicode 'characters' you require. The File encoding popup allows you to change the file encoding used when reading the script file. PRIMER supports the following file encodings:

Please contact Oasys Ltd Support if you have problems or require another encoding to be supported.

To show the unicode text the appropriate font must be used. This can be set using the preferences primer*cjk_unix_font and primer*cjk_windows_font .