Tcc menus

• File menu
  
• Edit menu
  
• View menu
  
• Configure menu
  
• Step menu
  
• Reset menu
  
• Run menu
  

This menu is for actions which read, write and print files.

• New menu entry
  
• Open menu entry
  
• Save menu entry
  
• Save As menu entry
  
• Page Setup... menu entry
  
• Print menu entry
  
• Refresh menu entry
  
• Exit menu entry
  

This entry is reserved for creating a new (empty) tcl script window. The current tcl script is replaced with an empty one, with no filename assigned.

This menu entry is capable of reading the following files:

• .tcl replaces current tcl script with new file contents (unimplemented).

  The new script is compiled. Sensor, Control, Signal and Variable windows all change to match the new script.

• .tcp extracts CTC data from another tcp file. (may not be readable in future versions).

  The .tcp file may be a regular tcp file produced when exiting tcc, or may be produced by Save As. These files are considered suitable for short term storage. This is a binary format that can change as tcc evolves. This change is a function of the Java libraries used and is unavoidable.

• .ctc reads CTC data from ascii file.

  This type of CTC file is written in plain text and can be produced in any text editor. The file format will only evolve in a backwards compatible manner.

Save the contents of the frontmost script window (.tcl or .qtu). Not currently implemented for tcl scripts.

This can export the following file data:

• .tcl save a copy of the current tcl script to a new file (unimplemented).
• .tcp save the CTC data as a new tcp file. See the warning under Open menu item, above.
• .ctc save the CTC data as a plain ascii file.
• ctc blocks: A list of ctc window coordinates for each defined block is saved as plain text.
  This can be used to make $COLOUR BLOCK/$COLOUR TRACK statements.

Setup page attributes ready for printing.

Prints the contents of the foremost window.

This can print the following data:

• .tcl: The main tcl script is printed (unimplemented).
• .qtu: The frontmost qtu script is printed.
• CTC: The CTC window graphic is printed.
  The window is scaled to fit the page, and printed as it appears on the screen. X and Y values are added to the top row and left column.
• Network: The network window is printed as it appears on the screen, unscaled. (unimplemented)

Exits the tcc program. The following data is automatically preserved in the <&OB>script>.tcp file:

• Which windows are open.
• Where each window is, or was last shown.
• The size of each window.
• The contents of all CTC windows.
• The interface configuration defined in the Network Configuration window.
• Input filtering configuration.

The following data is preserved in the tcc.tcp file:

• Which script was last read. This script is re-opened next time tcc is started if no script name is specified.
• The size and locatin of the main desktop window.
• Page format used for printing.

The following files are also produced:

• stdout.txt: Application debug messages produced during the run. Only useful when reporting bugs.
• stderr.txt: Crash dump data. This file should normally be empty.
• tcc.log: The contents of the log window.

• Variables
• Sensors
• Controls
• Throttles
• Tracks

• Configure Network

  This allows you to define which modules are attached to each serial port, and which pins are used or spare. You can also control baud rate.

• Configure Filtering

  This allows you to filter the input lines received from input modules so that short glitches do not cause the script to take erroneous actions.

• Configure Logging

  This configures the debugging of the script. You can select the level of logging output sent to the Log window.

• Start Network

  Start all serial interfaces. All interfaces defined in the Network Configuration window are started. Inputs are read and outputs despatched. Until the network has been started the script cannot control the hardware.

• Stop Network

  Stop communicating on all serial interfaces. When the network is stopped no further inputs are read from the hardware, nor outputs sent. The script can still read the last value the inputs had taken, and you can control the inputs manually using the Sensors window.

Single step the TCL script. This means that each WHEN statement gets a chance to run just once. All the tests are evaluated once and those statements that are then eligible to be executed are executed.

The Reset menu

Return to the state just after the script was loaded and compiled. Reset all variables and outputs to zero. Return the CTC panels back to their startup state. Does not stop the network interfaces.

The Run menu

Start running the TCL script.