Re: [Kicad-developers] "Fuzzy" antialiasing in eeschema

2019-01-05 Thread Vesa Solonen
Alex Lockwood kirjoitti 4.1.2019 klo 4.14: > I know this is solidly within in realm of minor complaints, but I > wonder, is there anything "easy" that can be done about this? > > https://misc.c4757p.com/fuzzy-wires.png > > A simple answer, I think, is to give eeschema and pcbnew separate > settin

Re: [Kicad-developers] Hoping to contribute but I have some questions

2019-01-05 Thread Wayne Stambaugh
On 1/4/19 6:18 PM, Tomasz Wlostowski wrote: > On 04/01/2019 18:51, Brian Piccioni wrote: >> I am still keen to attempt to incorporate geographical component annotation >> into KiCad. In general, it is preferable for component annotation to be done >> relative to the PCB and in some logical order

Re: [Kicad-developers] [RFC] Symbol library file format

2019-01-05 Thread Wayne Stambaugh
On 1/3/19 11:24 PM, Simon Richter wrote: > Hi, > > On 03.01.19 19:06, José Ignacio wrote: > >> I >> think useful comments to the proposed format should see beyond the >> actual low level representation of the data and talk about the overall >> model being used to store it. > > tl;dr: That's a se

Re: [Kicad-developers] [RFC] Symbol library file format

2019-01-05 Thread Wayne Stambaugh
Hi Mario, On 1/4/19 10:53 AM, Mário Luzeiro wrote: >> Now if you create a unique part number for every >> resistance value, tolerance, temperature coefficient, manufacturer, etc. >> that would be tens if not hundreds of thousands of unique part numbers. > > I know my intervention may be a bit off

Re: [Kicad-developers] [RFC] Symbol library file format

2019-01-05 Thread Thomas Pointhuber
My ERC Proposal was more like a: we should at least think about it a bit instead of writing the pin type near style and number/name. We can specify ERC hints in a future-proof way without extending the current implementation. Like: (erc_hints (pin_type power_in)) This would allow us to specify ne

Re: [Kicad-developers] Hoping to contribute but I have some questions

2019-01-05 Thread Brian Piccioni
Wayne My prior approach was to 1) verify that the was/is change list produces no errors on the schematic (since it is derived from the PCB there can be discrepancies). 2) if there were no errors, update the PCB and schematic reference designations 3) update the netlist with the new reference des

Re: [Kicad-developers] grammar.c not found,

2019-01-05 Thread Seth Hillbrand
I've pushed your patch. Thanks for tracking this down John! Best- Seth Am 2018-12-23 16:32, schrieb John Beard: Hi, It seems "make clean" might be the trigger here. The target for the libeval grammar is done with CMake add_custom_command with an OUTPUT. This means the output file will be clea

Re: [Kicad-developers] [PATCH] Pcbnew unit test framework

2019-01-05 Thread Seth Hillbrand
Hi John- Patch 0002 does not apply cleanly to qa/CMakeLists.txt even after applying 0001 -S Am 2019-01-04 09:36, schrieb John Beard: Hi, I have worked out how to do unit tests of the Pcbnew code. The first example test is a pretty unexciting one about the import plugin manager (which is wh

[Kicad-developers] 5.1 string freeze

2019-01-05 Thread Wayne Stambaugh
Is there any reason not to start the 5.1 string freeze? If so, please let me know. Otherwise we can officially freeze the strings so our translators can start work towards the 5.1 stable release. Cheers, Wayne ___ Mailing list: https://launchpad.net/

Re: [Kicad-developers] 5.1 string freeze

2019-01-05 Thread Seth Hillbrand
Am 2019-01-05 16:21, schrieb Wayne Stambaugh: Is there any reason not to start the 5.1 string freeze? If so, please let me know. Otherwise we can officially freeze the strings so our translators can start work towards the 5.1 stable release. For 5.0, the string freeze was RC2. Are we tagging

Re: [Kicad-developers] 5.1 string freeze

2019-01-05 Thread Jeff Young
I’m not aware of anything pending. Cheers, Jeff. > On 5 Jan 2019, at 21:21, Wayne Stambaugh wrote: > > Is there any reason not to start the 5.1 string freeze? If so, please > let me know. Otherwise we can officially freeze the strings so our > translators can start work towards the 5.1 stabl

Re: [Kicad-developers] [PATCH] Pcbnew unit test framework

2019-01-05 Thread John Beard
On Sat, Jan 5, 2019 at 4:23 PM Seth Hillbrand wrote: > Patch 0002 does not apply cleanly to qa/CMakeLists.txt even after > applying 0001 Hmm, that's odd: I can apply this with "git am 0002". I'm applying on top of 69fc301bf. Where are you applying it to? Do you still have the triangulation t

Re: [Kicad-developers] [PATCH] Pcbnew unit test framework

2019-01-05 Thread Nick Østergaard
I just did git am 000* and it worked fine for me, on master. On Sun, 6 Jan 2019 at 01:20, John Beard wrote: > On Sat, Jan 5, 2019 at 4:23 PM Seth Hillbrand wrote: > > > Patch 0002 does not apply cleanly to qa/CMakeLists.txt even after > > applying 0001 > > Hmm, that's odd: I can apply this with

[Kicad-developers] [PATCH] Remove unused code from legacy_gal

2019-01-05 Thread John Beard
Hi, Here is a really silly (since it's in legacy code) small patch for some unused code I was alerted to by Clang. But might as well get it off my patch stack! Cheers, John From 3f7aaef50dc0cc51d995450c6c6a7c5fca85f8d1 Mon Sep 17 00:00:00 2001 From: John Beard Date: Fri, 4 Jan 2019 14:20:47 +00

Re: [Kicad-developers] [RFC] Symbol library file format

2019-01-05 Thread Andrew Lutsenko
With the amount of data that KiCad handles performance of particular parser has minuscule impact. File IO delays would thwart any processing time. What Simon talked about is as he said a separate discussion and is orthogonal to the decision of how to define data model and what file format to use. A