Closed GoogleCodeExporter closed 8 years ago
That is to be expected, since qua design the node HTML elements do not exist
until they are rendered the first time.
These possible solutions come to my mind:
- isn't that what live events where made for?
I wonder why these plugins do not use live events or event delegation...
- ekemo suggested a workaround in issue 171. I will include his 'onRender'
patch in version 1.0.4
- I am thinking of adding a tree.renderAll() function, that would create all
elements, so you can bind. (This wouldn't help with lazy loading trees however)
Original comment by moo...@wwwendt.de
on 20 Jan 2011 at 6:37
It might be useful to have a method that would allow you to render down from a
specific node that would deal with lazy loading. I don't know how feasible that
would be to implement, but then at least you could render only that part of the
tree after the lazy load.
Original comment by jonas.ba...@gmail.com
on 20 Jan 2011 at 3:53
The idea would be to have a node.renderChildren() function - or alike - that
the user can call in the onLazyRead handler.
(tree.renderAll() would be implemented as tree.rootNode.renderChildren())
Original comment by moo...@wwwendt.de
on 20 Jan 2011 at 5:06
Original comment by moo...@wwwendt.de
on 23 Jan 2011 at 8:44
New method tree.renderInvisibleNodes() forces creation of all HTML elements.
node.render() has new argument includeInvisible.
Original comment by moo...@wwwendt.de
on 23 Jan 2011 at 8:50
Also started issue 174.
Original comment by moo...@wwwendt.de
on 23 Jan 2011 at 9:45
considered verified
Original comment by moo...@wwwendt.de
on 17 Jul 2012 at 4:16
Original comment by moo...@wwwendt.de
on 17 Jul 2012 at 4:19
Original issue reported on code.google.com by
jonas.ba...@gmail.com
on 19 Jan 2011 at 3:29