On 7/24/07, Darren Dale <[EMAIL PROTECTED]> wrote: > On Tuesday 24 July 2007 5:20:40 am Fernando Perez wrote: > > Hi all, > > > > if anyone is still following, please update the tconfig work. Run > > > > ipython -wthread > > %run mpltest.py > > mplconf2.tconf.edit_traits() > > > > Edit to your heart's content. > > I can't get edit_traits() working on my machine, but I can do it with the > command line.
Bummer. It's nice to see that GUI for the whole of MPL running ;) > > You can then save changes via > > > > mplconf2.write() > > The mpltest.py script expects there to be an mplrc2.conf file, but it isnt in > svn. So the script creates an empty mplrc2_copy.conf file, linked with a > default MPLConfig, but if I change some properties of mplconf2.tconf, and > then do mplconf2.write(), the mplrc2_copy.conf file remains blank. Are you sure? I just ran the test removing the mplrc.conf file from my disk, and the mpnlrc2_copy.conf file is indeed created blank, but after editing the tconf object and calling write(), I *do* get the changes I make written to it. I can't reproduce your problem... > If I copy mplrc.conf to mplrc2.conf, then I can run mpltest, change my tconf > properties, call write(), and those changes do get updated in > mplrc2_copy.conf. > > > ps - the auto-generated file now has all class docstrings as comments > > as well as traits handlers info. It should be a pretty good start for > > a manually tweaked one. > > I have not been able to auto-generate a default file. As above, the file is > blank after writing. How are you trying to generate it? Does the printout on-screen at least write a full config for you? Please update and try again, I added a little utility called tconf2File() to wrap this writing process; there's a small subtlety that I might not have been clear about before (one has to write the str() form of the tconf object to get the class docstring extraction). > > > pps - I'm done with this, for a while. I've sunk *way* too much time into > > it. > > Thank you Fernando. I'll have a look at the issues I reported when I get a > chance. Thanks. Cheers, f ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
