| The Programmer's Interface |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
| |
 |
Using the programmer's interface, you can write short programs
to control Streets On A Disk from another application. This can
also be used to automate routine mapping tasks.
There are two ways to send commands to Streets On A Disk:
1. Use the programmer's interface menu found in the EDIT
menu. This is an easy way to test any commands without
having to write custom software. When completed, you can
use the same commands to drive the Text File Interface.
2. Use the Text File Interface to send commands. While
Streets On A Disk is running, it is constantly looking for the
presence of a command text file with the name "Prog.txt".
When found, Streets will automatically process the
commands and then erase the file to indicate that it's finished.
Any results are stored in a "Prog.log" file.
to control Streets On A Disk from another application. This can
also be used to automate routine mapping tasks.
There are two ways to send commands to Streets On A Disk:
1. Use the programmer's interface menu found in the EDIT
menu. This is an easy way to test any commands without
having to write custom software. When completed, you can
use the same commands to drive the Text File Interface.
2. Use the Text File Interface to send commands. While
Streets On A Disk is running, it is constantly looking for the
presence of a command text file with the name "Prog.txt".
When found, Streets will automatically process the
commands and then erase the file to indicate that it's finished.
Any results are stored in a "Prog.log" file.
