Documentation

• Section: Basic Usage
• Section: A caveat
• Section: Command prompts
• Section: Transcripts
• Section: Notes on pasting commands from mouse input
• Section: Miscellaneous notes
• Section: Change Log
• Example: * Minimal - A very basic dual-window I/O setup. There are no tweaks to the standard behavior.
• Example: ** On the Edge - Another dual-window I/O example, but this time with a number of refinements. The input window clears after each command, to avoid scrolling, and is set off from the main window by a horizontal line (actually, a very narrow graphics window). To make up for the lack of command history in the input window, we echo each command in the output window before printing the result. The example also serves to illustrate a number of tweaks related to line spacing and transcript output.
• Example: ** Terminal - This example illustrates one use for changing the current text output window. Basically, the player must interact with a computer terminal, and during this interaction the game's interface apes the terminal. We open a new window (the terminal-output-window) in front of the main window, covering the latter completely. This new window is a text-grid window with reversed color-scheme and monotype font (both defaults for text-grid windows).

Text Window Input-Output Control allows an author to direct the game's main input and output--both of which would normally be directed to a game's "main window"--to any text window she chooses. We can, for example, split input and output, so that the player's input is entered into one window, while the game responds in another. Window input-output (I/O) can be changed at any time during the game. The extension also provides more control over transcript output.

Text Window Input-Output Control is built on, and requires, Jon Ingold's Flexible Windows extension.