Well, I'm going to try adding flags="dont-build-content" to all the trees and see what happens. To be honest, I don't remember why it's not there to begin with... probably because I had little idea what I was doing at the time (was brand new to XUL).
[just tried]... JS errors on tree.builderView (some kind of init problem with the tree?) but otherwise everything looks OK. Container state (open/closed) is *still* not maintained. Do I need to delete localstore.rdf or persist="open" or ...? --- Neil <[EMAIL PROTECTED]> wrote: > Neil Deakin wrote: > > > Eric H. Jung wrote: > > > >> Thanks HJ and Neil for the replies. This has been very helpful. I > >> will implement it myself then, with an observer. > >> > >> Any idea why I'd get an NS_NOINTERFACE exception with: > >> > >> var treeBuilder = > >> > tree.builder.QueryInterface(Components.interfaces.nsIXULTreeBuilder); > >> > >> The line before it calls tree.builder.rebuild() -- and works -- so > > >> I'm fairly certain tree.builder is valid... > > > > Because nsIXULTreeBuilder is only implemented by tree builders > > (flags="dont-build-content") > > Bah, of course, when you don't use those flags you only get a boring > template builder. Maybe you could use an attribute change listener to > > look for changes in the "open" attribute instead? > _______________________________________________ > Project_owners mailing list > [email protected] > http://mozdev.org/mailman/listinfo/project_owners > _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
