On Tuesday, August 6, 2013 8:52:49 AM UTC-5, Edward K. Ream wrote: >> 4. No need to change Leo's core. The plugin will have to replace Leo's body pane with a QStackedWidget. It won't be fun, but it should be doable.
> I would be willing to make *simple* changes to Leo 's core if it would make the plugin's job much easier. My first thought is to have some (all?) of the free_layout panes have a QStackedWidget as a parent. This would add lots of flexibility. However, I know from experience that such innocent-looking changes can create problems. For example, the recent bug involving inconsistent window titles was intractable until I saw that the LeoTabbedTopLevel was the parent of the DynamicWindow, and not the other way around. Still, having the body pane have a QStackedWidget as a parent might unlock some real possibilities. This *might* qualify as a simple change. Or not. EKR -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
