On Tue, Nov 15, 2011 at 11:16 AM, Ville M. Vainio <[email protected]> wrote: > why do you need leoQtFrame? It's recommended to use qwidgets directly, that > way your code won't break if Leo classes are modified. >
This is just one-off code with the intention of interactively playing with bits and pieces of Leo code. I find it helpful to be able to interactively discover the minimum requirements for instantiating pieces of the code. So I was hoping to be able to just instantiate, say the outline/tree portion. However, glancing at the code, it seems that leoBody and leoTree are very intertwined with each other and would not make good candidates for instantiating in isolation. I thought I would have better luck with leoFrame. I want the actual gui to be displayed so I can interact with it both via code and via mouse and keyboard events. Maybe leoQtFrame is the wrong target, but is there a way to attach a leoQtFrame to something that will be displayed on my screen? Or is there a better class I should target first? Brian -- 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.
