Using Klusters over a Slow Network Connection
By default, any change you make triggers an immediate update of all visible views. However, this may not be desirable when using Klusters over a slow network connection. A good example is when you need to simultaneously display multiple clusters: normally, Klusters will quickly redraw all the views every time you select a new cluster ― but this is not appropriate when using Klusters over a slow network connection, as transmitting the data to redraw can take a substantial amount of time.
In order to prevent Klusters from automatically redrawing all views after a change, select ->. Updates must then be triggered manually by selecting -> or clicking on
. To revert to the default behavior, select ->.
