On Oct 18, 5:43 am, "Edward K. Ream" <[EMAIL PROTECTED]> wrote: > On the list for today:
> - Whatever else crops up that makes it difficult to use the qt plugin. I have been happily debugging the logic that opens a second Leo window. 1. Call QTreeWidget.repaint in leoQtTree.redraw_now the first time called. This forces an immediate redraw after loading the .leo file but before loading the derived files. 2. Call proper ctors for subclasses in Window ctor. I had hoped that this would make a difference in point three, but no luck. 3. When opening a second Leo window, the call to g.app.gui.qtApp.setStyleSheet generates errors from QObject::disconnect and QObject::connect about null params. I'm not sure what is going on. Initing QMainWindow twice might be dicey. I'll probably ask for help. 4. Properly inited leoQtTree in leoQtFrame.finishCreate rather than in initAfterLoad. I hadn't done this before because Leo's core was QTreeWidget.bind. But the trick is to set leoQtTree.canvas to self, that is, the leoQtTree itself, **not** its QTreeWidget component. This allows us to define a do-nothing leoQtTree.bind method. This is actually an important step forward, although no doubt it seems incomprehensible. Init code can get pretty hairy... Anyway, most of the code required to load a second .leo file is operational, but perhaps per-widget stylesheets must be used instead of per-app stylesheets... 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 -~----------~----~----~----~------~----~------~--~---
