I was just wondering why the AsynchTriStateNodeUI isn't the default behaviour in all cases?

I was puzzling for a while about why child checkboxes weren't checked when the parent is checked unless the parent had been expanded at least once. Is there a case where you would not want the child nodes to be toggled when a parent is toggled?

I just detected a bug using the TriStateTree version 1.2..
By including the TreeCheckbox.js into a index.html - the on('click') and some other events don't fire anymore - even when using just a normal tree without TriState checkboxes.

from index.html - the onclick event fires, but this is also browser specific:

With TreeCheckbox.js included, the on('click') seems to work in Firefox 2.0.0.18
but not in Opera 9.62 Konqueror 3.5.5, IE 6.0.3790.3959 and Firefox 3.
The on('dblclick') event seems to work in all five of them.

I attached a full example of my code including the latest ext - version here:

Waht are expected pros and cons of the widget

Hi,

Can we please know what can we expect from the widget in terms of pros (working) and cons(non-working) stuff of the current Tri-state widgets.

Between the this.emptyIcon in the renderElements function (At line 78) in the TreeCheckbox.js is pointing to "http://www.extjs.com/s.gif" which will obviously cause problems when the end-user using the widget is offline.

Between the this.emptyIcon in the renderElements function (At line 78) in the TreeCheckbox.js is pointing to "http://www.extjs.com/s.gif" which will obviously cause problems when the end-user using the widget is offline.

ColumnCheckboxTree

Hi!
I've extended this plugin to display columns like in sample ColumnTree.
Everything is the same except the names: ColumnCheckboxTree for TreePanel, ColumnCheckboxNodeUI for TriStateNodeUI and AsynchColumnCheckboxNodeUI for AsynchTriStateNodeUI.
Greets!