Known issues: Difference between revisions

From GLOW Visualization
Jump to navigationJump to search
No edit summary
Line 9: Line 9:


==Duplicated leaf nodes==
==Duplicated leaf nodes==
There is a known issue with spurious duplication of leaf nodes. Under a certain parent, a leaf node might appear multiple times.
There is a known issue with spurious duplication of leaf nodes, if multiple inheritance exists higher up in the class hierarchy. Under a certain parent, a leaf node might appear multiple times.


'''Workaround:''' There is no workaround.
'''Workaround:''' There is no workaround. When counting individuals, enable the display of labels for leaves in order to spot duplicates.


==Modifier buttons cause spurious panning==
==Modifier buttons cause spurious panning==

Revision as of 22:57, 5 April 2010

As is expected with pre-release software, there are bound to be some errors and other issues.

The known issue list is as follows:

Ati Radeon HD problems with Inverted Radial Tree layout

Some newer ATI Radeon HD cards exhibit problems when choosing the "Inverted Radial Tree" layout. The problem causes spurious textures to be drawn, and may cause the GLOW user interface to "freeze" for seconds.

Workaround: Do not use the Inverted Radial Tree layout. Select another layout using the "layout" drop-down at the bottom of the plug-in. It may take some time for the interface to become responsive.

Duplicated leaf nodes

There is a known issue with spurious duplication of leaf nodes, if multiple inheritance exists higher up in the class hierarchy. Under a certain parent, a leaf node might appear multiple times.

Workaround: There is no workaround. When counting individuals, enable the display of labels for leaves in order to spot duplicates.

Modifier buttons cause spurious panning

Laptops may not have a middle/right mouse button which are used to perform zooming and rotation of the graph. OPTION and COMMAND are modifiers that can be combined with a left-click to do zooming and rotation, but while this functions, the graph pans simultaneously.

Workaround: Connect a mouse, or pan the graph back to its oroginal location using only the left mouse button, after it has been incorrectly moved.