> It happened to me when I open kicad on the commandline with a *.pro file in
> the same
> directory (essentially what jp said)
I missed that since I haven't used kicad.exe that way.
The next step on this topic is to remove all the wxSetWorkingDirectory() calls
and make
the software work wit
On 28 July 2014 07:16, Dick Hollenbeck wrote:
> On 07/28/2014 08:58 AM, jp charras wrote:
> > Le 28/07/2014 15:20, Dick Hollenbeck a écrit :
> >> Thanks Henner:
> >>
> >> I'll look at this now. The surprise is the inconsistency of the file
> dialog, which
> >> normally returns a full path, but h
On 07/28/2014 08:58 AM, jp charras wrote:
> Le 28/07/2014 15:20, Dick Hollenbeck a écrit :
>> Thanks Henner:
>>
>> I'll look at this now. The surprise is the inconsistency of the file
>> dialog, which
>> normally returns a full path, but here not. An assert would have caught
>> that assumption,
Le 28/07/2014 15:20, Dick Hollenbeck a écrit :
> Thanks Henner:
>
> I'll look at this now. The surprise is the inconsistency of the file dialog,
> which
> normally returns a full path, but here not. An assert would have caught that
> assumption,
> my mistake.
>
> In the multiple open projects
Thanks Henner:
I'll look at this now. The surprise is the inconsistency of the file dialog,
which
normally returns a full path, but here not. An assert would have caught that
assumption,
my mistake.
In the multiple open projects scenario, changing the directory (CWD) will go
away.
So I won'
Hi,
Opening a foo.pro file in the current directory
kicad foo.pro
gives an error message ("Directory not found").
The reason is simple: calling wxSetWorkingDirectory() with an empty string
causes that problem.
This might be due to version of wxwidgets; I have version 3.0 whatever is
currently o
6 matches
Mail list logo
