Re: [Kicad-developers] DRC Dialog Improvements

I can update the text alignment of that field. I agree that it looks a bit weird. Anyone else have any thoughts? On Thu, Dec 1, 2016 at 1:24 AM, Clemens Koller wrote: > Looks good! > > Just a few comments: > > I'd prefer to have the text "Specific via diameters and track width,

Re: [Kicad-developers] configuration files for KiCad

Thanks Wayne. I will look in to wxConfig paths and see if I can see any compelling disadvantages to bring up vs. JSON (note that JSON could be handled by Boost.PropertyTree so no additional dependency). If I can see a clear way to achieve the things I want to propose using wxConfig, I'm fine

Re: [Kicad-developers] configuration files for KiCad

On 12/1/2016 11:44 AM, Jon Evans wrote: > Hi all, > > Per my recent email, I'm going to be looking in to various UI/UX things, > starting with Eeschema, and I thought of a topic that probably warrants > its own thread. > > Some of the things I want to propose would involve giving the user more >

Re: [Kicad-developers] eeschema status and features safe to work on

Hi Jon, Anything that requires access to the schematic objects is going to get changed so if you don't mind the disruptions to your work then feel work on things like your autorouter. If you don't need access to the schematic objects such as your color selection, then I would think the

Re: [Kicad-developers] configuration files for KiCad

Hi JP, You are correct, I'm talking about the "program configuration", not the "project configuration" or "library configuration". I understand your concern about adding more maintenance burden. I think there are possible solutions that would not be significantly more complicated than wxConfig

Re: [Kicad-developers] configuration files for KiCad

Le 01/12/2016 à 17:44, Jon Evans a écrit : > Hi all, > > Per my recent email, I'm going to be looking in to various UI/UX things, > starting with Eeschema, and > I thought of a topic that probably warrants its own thread. > > Some of the things I want to propose would involve giving the user

Re: [Kicad-developers] configuration files for KiCad

On 01.12.2016 17:44, Jon Evans wrote: > Hi all, > > Per my recent email, I'm going to be looking in to various UI/UX things, > starting with Eeschema, and I thought of a topic that probably warrants > its own thread. > > Some of the things I want to propose would involve giving the user more >

[Kicad-developers] configuration files for KiCad

Hi all, Per my recent email, I'm going to be looking in to various UI/UX things, starting with Eeschema, and I thought of a topic that probably warrants its own thread. Some of the things I want to propose would involve giving the user more options for customization of the tool (i.e. more

Re: [Kicad-developers] ransomware locky detected on version 4.0.4 and 4.0.3

Paolo, Does that firewall software of yours not provide any technical info about this? Like filenames or byte sequences or similar? Den 01/12/2016 16.41 skrev "Wayne Stambaugh" : > Paolo, > > This might be a false positive. We've seen this in the past. Would one > of our

Re: [Kicad-developers] ransomware locky detected on version 4.0.4 and 4.0.3

Paolo, This might be a false positive. We've seen this in the past. Would one of our windows package devs please verify the windows installer binaries on the kicad download page are still valid? In the future, please post your questions to the developers mailing list. Cheers, Wayne On

Re: [Kicad-developers] eeschema status and features safe to work on

Hi Orson, Thanks much for your feedback and news about plans for eeschema. I agree that having a common codebase for selection filtering and object inspection across the tools is a great idea (especially since the roadmap has plans for eventually combining the tools more than they are today). By

Re: [Kicad-developers] eeschema status and features safe to work on

Hi Jon, We really appreciate your offer. I am quite positive that most of people here would admit that KiCad begs for some UX improvements. GALifying eeschema is going to be a significant refactor, but it will not happen before v5 release, which is currently planned for Feb 2017. IIRC Wayne