On Oct 4, 11:43 pm, "Ville M. Vainio" <[EMAIL PROTECTED]> wrote:
> This will be pretty slow (though it's probably too early to optimize
> it).
I agree. It's tricky to call populate_tree: iirc it can't be done in
the leoQtTree init code because the tree hasn't been read at that
time. So I fell back to using c.frame.tree.redraw_now, i.e.,
leoQtTree.redraw_now.
It may be worthwhile to really provide methods to set node /
> subtree "dirty", so only that part of the tree would need to be
> regenerated. Moreover, if clones are detected, the subtrees of all the
> clones would need to be recreated as well.
This seems like an heroic solution if done in Leo's core. Another
possibility would be to try to compute the diffs within
leoQtTree.redraw_now. For now, I'll leave possible optimizations to
you.
I would propose the following division of labor: you continue to use
the gui designer to updated Ui_MainWindow; I'll work on the leoQtX
adapter classes. Does that seem reasonable?
Edward
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---
