|
From: Johan C. <jco...@j-...> - 2002-03-11 23:07:25
|
> <snip> > 2> > If you do a refresh on a tree then the the cursor doesn't go to normal > anymore (stays in wait) > </snip> > > This works for me. Is it any refresh (I.E. Does F5, menu option or clicking > the toolbar button make a difference)? For F5 does it make a difference if > your cursor is over the object tree or elsewhere? If i did a refresh pressing the button then the cursor did stay wrong i added a _cursor.restore() after i do the refresh now just to be sure. > <snip> > 3> > The tree will be expanded with all the children are loaded before (so not > really yhe expanded > state but the complete state of all the nodes that are onces expanded. > To go around this is a bit difficult at them moment. > </snip> > > Known bug. I'll be fixing this in the rewrite. As well as actually creating > the previously expanded nodes its supposed to display them. I already did a rewrite :-) That's why i added this as an bug that is introduced in my code. the problem with the previous approacher (TreeState object or something) was that this only stored treepaths and then say to the tree expand But the problem if you do a reload of the tree then that tree path isn't there anymore because it is not loaded yet. I fixed that because the refresh is now really done by the model and its nodes and not just a call on root.reload() (look at BaseNode) But i don't use the methods: getExpandedNodes(TreePath) or isExpanded() anymore so maybe i should first try to get those and the do the current refresh and then expand those. (but not really those? because that real objects treepath are removed and replaced with something else. johan |
