VFleet Known Bugs and Work-Arounds

This document lists known bugs and work-arounds for VFleet version 1.0 .

Motif Window Sizing Bug #1

This bug arises in constructing complex transfer functions by loading parts from files into an existing SumTransferFunction. When the new sub-transfer-function of the SumTransferFunction is loaded, the Transfer Function Editor window may not enlarge to show the new parts. The new parts are actually there; they are just not visible or editable. The work-around is to add the new parts, save the whole transfer function to a file, and then reload the whole transfer function (replacing the existing, half-hidden transfer function). This bug will only arise when constructing transfer functions multiple levels deep.

Motif Window Sizing Bug #2

The window size setting options in the Image pulldown menu sometimes fail to produce a window of the currect size. Two work-arounds are possible. The first is to use the menu to set the window size before loading the first data volume. The second work-around is to simply resize the window by dragging the corner of the window frame. The current window size appears in the message displayed when a render is initiated.

Tcl script crash error

Some Tcl scripts, which contain loops that execute very quickly, cause VFleet to crash. This problem is not repeatable, and may in fact no longer occur. If you have a Tcl script that does this in a repeatable fashion, please send it in! Work-arounds consist of making small changes to the script, for example saving the current image to a non-writable location in each loop iteration.

Entering text in number slots of dialogs

Some dialog entry areas require a number for input. Typing text into these slots can under some circumstances confuse VFleet. The work-around is to not do that.