Icon bitmaps: When running in Director 11 it is recommended to use 16 or 32 bit depth bitmaps for all icon operations in TreeView. Some 8 bit bitmaps might fail to display correctly on Windows Vista.

Unicode strings: When running in Director 11 TreeView will attempt to convert and render the supplied UTF8 string data. However, not all glyphs are available and some double byte languages might fail to load.

International fonts: TreeView does not support double-byte fonts. One user has reported mapping errors with some single-byte Hebrew fonts.

Callbacks: If both SingleClick and DoubleClick are enabled, the first click of a user's double-click action triggers the SingleClick callback.

Moving treeview sprite offstage: If you move a treeview sprite outside the stage boundaries, its old rect will still receive treeview events unless you also set its sprite's visibility to FALSE

sprite(treesprite).loc = point(-1000,-1000)

sprite(treesprite).visible = FALSE

Altering the size of the tree: If you alter the size of the tree content using Lingo, for instance with setExpandedXTV, or by changing the size of node icons, you must then use resetScrollbarsXTV to re-calibrate the scrollbars.

Scrolling to a particular node: There is no built-in command to scroll the tree down to a particular node. Although it is possible to do this using getNodeLocationXTV and setContentOffsetXTV, the scrollbars were not designed for this and will continue to consider the top of the tree as the beginning of the offset. If you use Lingo to scroll the tree to a particular node, you must also create your own scrollbars using sprites.

Scaling: TreeView does not completely support scaling. When shown on a magnified stage, the bounding box of a TreeView sprite scales, but the contents do not.

Callback crash: There are some Lingo operations that cannot be performed inside TreeView callback handlers because they cause a crash. This is a limitation of sprite Xtras in general, not TreeView Xtra in particular.

Number of nodes: TreeView can create and manage up to a million nodes per tree. That is the internal logical limit. However, available memory, CPU speed and graphic card performance will determine how large a tree your application can actually build and manage with acceptable performance. TreeView was tested at up to 10,000 nodes per tree.

The memory requirement per unnamed node is between 200 and 600 bytes depending on the total number of nodes in the tree. That does not include any additional storage taken up by the node name or custom user strings set for the node with setUserStringXTV.

Tree properties: All of the properties of a TreeView tree are stored with its sprite. If you move to a frame that does not contain the TreeView sprite, the properties will be reset when you return to the frame. If you want to maintain TreeView sprite properties between frames where the sprite should not appear, move it offstage (locV = -1000) but keep it in the sprite channel.