> Leo will soon do more than what you are > asking directly. rue the day.
On Oct 25, 10:16 am, "Edward K. Ream" <[email protected]> wrote: > On Mon, Oct 24, 2011 at 9:14 AM, ne1uno <[email protected]> wrote: > > is there any way extra options could be passed onto QApplication(sys.args)? > the optparse docs effectively hid from me any hint of extra options or turning off errors on non existent options. so I wasn't able to actually try --style or --stylesheet I was prepared to give up on -stylesheet, after hearing the argument in another thread, about exposing too much of the implementation. though you only really care about the base widgets. flip a coin. @data stylesheet solorize contrast+=3 works for me too. I see now that --stylesheet would have to be intercepted, I doubt the one given on the commandline would override any stylesheet set programmaticly by Leo. I also thought stylesheets were cumulative. --stylesheet-replace could be the default --stylesheet-append would be another good option a script to output the current widgets and style would be nice to have. anything from a simple brace check to a full syntax check on the qss/ css probably should be done. I haven't seen any code for that. void setStyleSheet() apparently is no error on bad stylesheet. so no help. dejavu on Tk Tiles & Tix without the install & setup problems. you can also set style. not every OS will have every style. unknown styles are ignored. Plastique & Cleanlooks set a small radius on widgets. either might easily be the default without offending anyone. it's a subtle change. you can create custom styles but I never looked into exactly how. maybe with QML or QScript you can script a new style. """ setStyle() """ from PyQt4 import Qt #these are usually active in Windows styles = "Windows,WindowsXP,Motif,CDE,Plastique,Cleanlooks".split(',') #get styles styles= list(Qt.QStyleFactory.keys()) #pick one i = 4 g.es( styles[i] ) Qt.QApplication.setStyle(styles[i]) #e > 1. Imo, it is time to consider adding a typical "startup" file to Leo, ~/leo_config.py and cmdline --config=workflow_config.py would be especially nice to change a few runtime options for the workaday Leo allowing subsequent clicks on a shortcut to open another leo using the default out of the box config. though there are numerous ways around that already. config files are a little problematic. when they error, Leo will print an error message and exit python taking the command prompt down with it unless you start Leo from a command prompt directly. but, any additional capability will be appreciated. not limited to problems in a config file, some python errors before Leo gets rolling will pause the display if started with python -i launchLeo, but disappear as well if using pythonw. it would be nice if python would trap all errors. maybe Leo returning a known error code would do it? unless in batch mode, a pause would give some time to actually read the error message. could bring back a real live popup error message too. -- 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.
