On Tue, Aug 31, 2010 at 12:50 AM, VR <[email protected]> wrote:
> The initial problem is gone, i.e. Leo starts up properly. - However a > new > problem showed up. - Even if specifying '--gui=tk' Leo is started with > the Qt-Gui. Many thanks for this report, Viktor. Having such vigilant users is a big help. As I was thinking about this issue, it occurred to me that a significant improvement can be made in Leo's startup logic. Just after handling command-line args, and *before* processing plugins, Leo can (and imo should) determine the gui to be used. At present, the first plugin that sets g.app.gui determines the gui. If no plugin does this, there is fallback logic at the end of the startup logic. This may have made a tiny bit of sense in the days before the --gui option, but it seems to make no sense now. Setting g.app.gui "early" (before plugins load) should be all gain and no pain. It shouldn't break any plugin, it would simplify and clarify the startup logic and it would allow plugins to simplify their init logic. I'll do this for Leo 4.8 a1 unless I hear strong reasons why it is not a good idea. 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.
