On Tue, Nov 25, 2008 at 9:44 PM, leo_hag <[EMAIL PROTECTED]> wrote: > Try doing expand all nodes and then collapse all nodes.
That was immediate on qleolite as well, when it was still using leoBridge. The core imposes requires some things to be done, and that's what takes the time. > I am convinced. At the moment the custom widget out performs the > native widget by miles. And it doesn't need any nasty hacks! Again, the same was with qleolite... > By the way I have already included the tree widget in the qt plugin in > the hag branch, run leo with gui=qt in this branch and you will see it > working. Not technically feasable indeed :-) I'm glad no one told > Edward that when he started leo! I don't say it isn't doable - just that it would be a bad idea IMHO (but that's just MHO), in that it's better to put the work into making a "normal" tree widget work well. Of course code does speak louder than words, and you seem to be doing great, but just out of curiosity - what does your tree widget do that QTreeWidget doesn't? Also, attach screeshots for those who can't test it right now ;-) -- 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 -~----------~----~----~----~------~----~------~--~---
