Test Parameters

This option allows you to specify parameters to be passed to your publication when running in test mode using one of the Run commands. The parameters are passed to the publication via the Windows command line. Windows applications sometimes use the command line as a way of  accepting input from the user. For example, when you double click on a .doc file in Explorer and Microsoft™ Word appears, Windows uses the command line to pass the file’s name to Word.


A running publication can access the contents of the command line by examining the global [CommandLine] variable. The script below parses the [CommandLine] variable and separates the different parameters into variables [Param1], [Param2], [Param3], etc. The first variable ([Param1]) will always contain the path and file name of the publication. The variables after that ([Param2], [Param3], etc.) will contain any other command line items. The following script separates the command line elements and then displays a message for each one:

StrParse "[CommandLine]" "[#13]" "[Param]" "[Count]"

Loop "1" "[Count]" "[X]"

  AlertBox "Result" "Parameter [X] is [Param[X]]"

EndLoop


Debug Options

When the Keep a log of executed actions option is enabled, the debugger will record everything that  happens while your publication is running in test mode. Use the default log file name or enter one of your own in the space provided. After running your publication, using one of the App menu's Run options, view the log file in Windows Notepad or similar editor. The log file can be very useful for debugging complex scripts.


Note: These options are for testing purposes only and have no effect when running compiled publications outside of VisualNEO Win.