Re: [Kicad-developers] Recent wxConfig changes.

2018-12-29 Thread Maciej Suminski
Hi, On 12/29/18 12:45 AM, Mark Roszko wrote: > The error is from this patch: > > https://github.com/KiCad/kicad-source-mirror/commit/24f9bfa13b54267417ec971dca6cac005ce8b857 Apologies for the mistake, obviously it was not an intentional change. I see that John Beard has already fixed the problem

Re: [Kicad-developers] Recent wxConfig changes.

2018-12-28 Thread Mark Roszko
The error is from this patch: https://github.com/KiCad/kicad-source-mirror/commit/24f9bfa13b54267417ec971dca6cac005ce8b857 May I suggest whoever updates it, also adds a comment about intentionally using wxFileConfig? Is there even a point in typecasting the pointer from GetNewConfig to wxConfigB

Re: [Kicad-developers] Recent wxConfig changes.

2018-12-28 Thread Eeli Kaikkonen
See https://bugs.launchpad.net/kicad/+bug/1809442 la 29. jouluk. 2018 klo 1.21 Wayne Stambaugh (stambau...@gmail.com) kirjoitti: > Someone has completely broken configuration settings on windows. Most > likely caused by using wxConfig instead of wxFileConfig which used to be > the default until

[Kicad-developers] Recent wxConfig changes.

2018-12-28 Thread Wayne Stambaugh
Someone has completely broken configuration settings on windows. Most likely caused by using wxConfig instead of wxFileConfig which used to be the default until recently. Who ever made this change, please fix it. We do not use the windows registry to save KiCad configuration settings. This was a