kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

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> /
> 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     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>