JTraffic Screensaver


$USECACHE <Simple>

Determines the usage of a cache file.

This command checks the value of the field "Cache in the Configuration window.  Valid settings are:

0 No Does not use a cache.  Pictures are always loaded directly from the hard disk.
1 Use Pictures are loaded from the hard disk at program start-up and held in the memory cache as long as the program runs.
2 Load As 1, but the files are loaded from a *.tca  cache file when the program starts.
3 Load & Save As 2, but subsequent new pictures are saved to the cache file.

The purpose of this command is to offer different ways of dealing with the picture collection - adding and modifying pictures - and for using the program like a screensaver.  

The use of a memory cache can become bothersome when you are testing out pictures; creating new pictures, testing them and then editing them.  Once the source picture is added to the cache, Traffic doesn't refresh it in the cache until the program is restarted or, if option 3 is turned on, the "Delete Cache" button is pressed in the Configuration window.

On the other hand, using a cache can increase the program's speed in generating new trains whenever the program is run as a screensaver - especially, when the pictures are stored as individual graphic files (in .gif or .bmp format). If you use only .tvl picture libraries, then the usage of the cache does not cause any noticeable enhancement.

The normal way to control the usage of the cache is the radio button field in the configuration window. This timetable file command overrides that setting for the time the timetable file is running in a window or full screen.

The Configuration Window
Program Window
Stock List
Description Editor
Graphic Testpad
Timetable Editor
Timetable Syntax and Semanics
The timetable header
Sections, Groups, Lines, Scenes
Stock List File