> > settingdb gives an exception on close, but other than that and the > > weird bug where the graph is postage-stamp sized > > That's probably because it can't find the geometry settings. Makes sense.
> I've had a look at moving SettingsDb to QSettings and it seems pretty > easy... Well I can get it to read and (possibly) write settings. The > question is whether we want the current interface or something more > complex / flexible. > > > I dealt with the issue where you do "import directory.pythonfile" by > > just putting everything in the same directory and changing it to > > "import pythonfile" > > That should work, no? Why do you need the hack? Well, I dunno why this is, but just running veusz.py gives the error: import windows.mainwindow ImportError: No module named windows.mainwindow and quits. And so on for all the other import dir.pyfile statements. So it doesn't work, but I don't know why that is... possibly something to do with this (mainwindow.py): # this allows modules relative to this one to be used, # allowing this program to be run from python, or using this script # please suggest a replacement for this sys.path.insert( 0, os.path.dirname(__file__) ) Or maybe I'm starting it wrong, or my setup is weird - which is pretty likely given that it's windows. > > ugly, but since this is more aimed at producing > > a binary I don't think it really matters. > > Well the source should be the same on all platforms so it's kindof a > problem... Well actually I bet that all 3 users have their own version of the source right now :) Fair enough though, if we can keep it totally cross platform with one set of source then we should. Jamie
