On Tue, Oct 21, 2008 at 5:28 PM, Edward K. Ream <[EMAIL PROTECTED]> wrote:
> I plan to leave the tree code as it is for now and concentrate on bugs > that make the qt plugin unpleasant to use. So the qt tree > optimization project was a one-day wonder. Great job! Still something to do, though: - Note that tree can be expanded with the mouse. For this, you have to hook into itemExpanded signal (i.e. you can't count on the key events in the core alone). - Now that we have a robust redraw-all behaviour, we can do the optimizations in a non-rushed fashion. That doesn't mean we shouldn't do them though, for optimal user experience. At least redraw-on-expand (a very frequent occurence) can be made insanely fast, since only need to redraw the child items of the current item. We can easily do that by discarding all the child Items of the current items (see QTreeWidgetItem::takeChild()) and generating the new ones. It doesn't matter whether there are more than one level expanded under the current item, we can do whatever we do to the full tree now to the subtree of current item. And after that, we already have redraw-subtree operation => we can use it for other planned optimizations :-). I can do it once I return from my holiday (me and my wife are travelling to Rome for our honeymoon on thursday :-). -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
