On Tue, Feb 3, 2009 at 12:39 AM, [email protected] <[email protected]> wrote:
> > > let me still insist :-). One can set up file association, write batch > files or shell scripts in order to automatically pass the --gui=qt > argument to leo but, as far as I know, it doesn't mean that the > default gui for leo is the qt gui. Yes, I see what you mean. >From looking at runLeo.py, it appears that Leo creates the gui as follows: 1. Use the gui specified in the --gui=qt option, if it exists. 2. Otherwise, use a gui if it is created by a plugin. 3. Otherwise, use the tk gui. This should be good enough. True, the tk gui is the ultimate "default", but in practice that default isn't going to be used because many plugins will create a gui if none is in effect. This includes the tkGui and qtGui plugins *themselves*. Note that plugins are loaded in the order in which they appear in the "active" @enabled-plugins node. So to make the qtGui plugin the default *for you*, put either qtGui or tkGui plugin first on the list. It would indeed be possible to add a @string default-gui-name setting--Leo processes settings before loading plugins. However, this would cause even more confusion. The natural way to force a gui is either to use the --gui option or to put the desired gui plugin at the start of the @enabled-plugins node. 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 -~----------~----~----~----~------~----~------~--~---
