There are several other places where it might be nice to use the user's document folder instead of the CWD which is kicad executable path. I found two more places, new project in kicad and file open in pcbnew that use CWD which typically the user will not have write access. I fixed both of these cases along with your patch.
On 6/21/2015 5:14 PM, Martin d'Allens wrote: > I managed to build KiCad on windows, it works as far as I can tell. > > But to get it to work I had to remove a noname.pro <http://noname.pro> > that had been generated before my patch was applied. > And with regedit I cleared HKEY_CURRENT_USER/Software/KiCad/kciad/file1. > Otherwise the stray noname.pro <http://noname.pro> looks valid and there > is no reason to default to the home directory. > > I don't think we should refuse to open a project named "noname.pro > <http://noname.pro>", so the new behaviour will only apply to new > installations. > > I hope you missed this, or I should keep digging. > > On Mon, Jun 15, 2015 at 10:06 PM, Wayne Stambaugh <[email protected] > <mailto:[email protected]>> wrote: > > Hey Martin, > > Your patch does not seem to work on windows. When I try to open a new > project from kicad, the file open dialog still points to the kicad > executable path. In my case it's c:\mingw\bin. The Eeschema change > seems to work as expected. Is it possible the path is getting changed > in kicad somewhere before the file dialog is called? Please take > another look at your changes and see if you can resolve this issue. > > Cheers, > > Wayne > > On 6/14/2015 12:26 PM, Martin d'Allens wrote: > > Hi all, > > > > This recent bug complains about the default project path being in a > > read-only directory on Windows: > > https://bugs.launchpad.net/kicad/+bug/1463510 > > > > The attached patch changes the default project folder to wx's > > GetDocumentsDir(), which should translate to "$HOME", "...\My Documents" > > (Win), or "~/Documents" (Mac). > > I tested it solely on Ubuntu. > > > > There could be more scenarios where we want to do the same. I tried to > > extend this behaviour to Eeschema's standalone mode for starters, tell > > me if more needs be done. > > > > However the behaviour of writing to some default directory without > > asking is unsettling. I suppose most noname.pro > <http://noname.pro> <http://noname.pro> / > > noname.sch wouldn't exist if a "Save as" popup was shown the first time. > > > > Martin > > > > > > _______________________________________________ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : [email protected] > <mailto:[email protected]> > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : [email protected] > <mailto:[email protected]> > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > > _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
