On Fri, 27 May 2005, James Graham wrote:
Jeremy Sanders wrote:
There are a couple of places in the code which assume unix paths (mainly
just the settings handling part).
Just out of interest (I haven't looked at the code at all), what's the
reason for using a custom settings handling class rather than QSettings
(at least for settings that are to be saved)? Or is QSettings being used
somewhere I haven't noticed?
That's a good point. The only reason I can come up with for the current
setup, was that I had rewrote the whole settings code and I wanted to do
something quickly. There's probably a good reason to change the settingdb
code to use QSetting, which would be the registry in windows.
It's probably not much work to go and modify the settingdb.py code to use
QSettings instead.
Jeremy
--
Jeremy Sanders <[EMAIL PROTECTED]>
http://www.jeremysanders.net/ Cambridge, UK
Public Key Server PGP Key ID: E1AAE053
