Screen View Class
Screen Name A thumbnail view of this screen (if open) will be displayed by the Screenview object. This can be a public screen name or an AmigaOS pattern matching a screen title.

The screen being displayed (the source screen) may be a register based or a truecolor (16/24 bit) screen mode. Also, the screen displaying the Screenview object (the target screen) may be either a register or a truecolor mode. Palette remapping is performed for register modes.

Fastest performance is available when the target screen is a 16 bit truecolor screen mode, and the source screen is either an 8 or 16 bit graphics card screen mode. If the target screen is a register mode, palette remapping will slow rendering. If either screen is on a low performance graphics device such as an ECS or AGA screen mode, performance will suffer greatly.

Performance is largely independent of the resolution of the source screen, but it does depend heavily on the size of the Screenview object itself.
Antialiasing The amount of antialiasing to use in the thumbnail display. Higher numbers will result in a better quality image, but take longer to compute since more pixels must be read from the target screen. Generally, settings of 2 or 3 are sufficient, and 1 is best with slow machines or graphics modes.

Various Antialiasing Values
Unless you are viewing this on a 16 or 24 bit screen, the actual differences may be obscured by your browser's color mapping.
Antialiasing=1 Antialiasing=2
Antialiasing=4 Antialiasing=8

Smart Update If this is selected, the thumbnail is recomputed only if the contents of the screen has changed. Checking for changes is done rapidly. Some very minor changes may be missed.
Smart Threshold If a screen contains some small regularly changing areas (clock hands, IBrowse transfer animations, etc), you might not want the Screenview to update on these minor changes. The higher this number, the more changes are required to the screen before an update is triggered.
Subtask priority Since palette remapping is a time consuming operation, it is done in a subtask. This is the priority of that task. Note that the task will be set to this priority while it is rendering, but while waiting, it will be set to a higher priority.

It may take a moment to close a window containing ScreenView objects if the subtask is currently rendering a thumbnail since the task must be killed.
Update Interval The time period between checks. If Smart Update is turned on, this will not necessarily result in the Screenview object updating its contents.

Due to the relative CPU expense of recomputation and palette remapping, a Screenview object which has been resized will not re-render its thumbnail until the next Update Interval. This is to allow opaque resizing to be performed smoothly.