On Nov 25, 8:10 pm, "Ville M. Vainio" <[EMAIL PROTECTED]> wrote:
> 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? Its not what it can do but how easy it is to do it. There is more code to interfaceto QTree than there is in the entire custom widget and the interface code is more complicated and convoluted, I wouldn't want to maintain or modify that code!. I had difficulty understanding it, thats why I started looking at the gtkDemo. Also the interface code is far from complete. On the custom widget, a simple hitTest determines exactly which part of the headline was hit and how, and can easily be converted to any number of custom signals or leo hooks. The canvas is accessible on a pixel by pixel basis for rubber banding etc or extra drawing. Eg it would be easy to add a bar with icons similar to the scintialla bar for bookmarks etc. The real question is, what does QTree do that the custom tree cant that justifies such huge amounts of complicated interface code. By the way the widget in the docking demo isn't as well advanced as the one in the modified qt plugin. I stress that the widget IS wired in and working in the qt plugin already (in the hag branch). Where as the current tree is not working. Don't take me to seriously, I get a little competitve sometimes 8-) > Ville M. Vainiohttp://tinyurl.com/vainio Thanks for the link. I think I might get one of those myself. -- Hag --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
