Re: [Kicad-developers] official web page

2015-06-19 Thread easyw
HI Cirilo, is there a repository for IDF 3d modules? Maurice On 20/06/2015 02.53, Cirilo Bernardo wrote: Hello everybody, Marcos Chaparro has added a screenshot to the wikipedia entry on KiCad: https://en.wikipedia.org/wiki/KiCad#/media/File:KiCad_3D_with_IDF.png The screenshot shows the

Re: [Kicad-developers] official web page

2015-06-19 Thread Nick Østergaard
2015-06-20 2:53 GMT+02:00 Cirilo Bernardo : > Hello everybody, > > Marcos Chaparro has added a screenshot to the wikipedia entry on KiCad: > https://en.wikipedia.org/wiki/KiCad#/media/File:KiCad_3D_with_IDF.png > > The screenshot shows the new 3D Viewer rendering of the video demo board > along wi

Re: [Kicad-developers] official web page

2015-06-19 Thread Adam Wolf
I was going to recommend the HackRF or Ubertooth One... Adam Wolf On Jun 19, 2015 9:39 PM, "Jared Boone" wrote: > I might be a bit biased here, but I would volunteer either the HackRF One > design: > > https://github.com/mossmann/hackrf/tree/master/hardware/hackrf-one > > or the Daisho F

Re: [Kicad-developers] official web page

2015-06-19 Thread Jared Boone
I might be a bit biased here, but I would volunteer either the HackRF One design: https://github.com/mossmann/hackrf/tree/master/hardware/hackrf-one or the Daisho FPGA main board design: https://github.com/mossmann/daisho/tree/master/hw/main_board Both are quite complex and dem

[Kicad-developers] official web page

2015-06-19 Thread Cirilo Bernardo
Hello everybody, Marcos Chaparro has added a screenshot to the wikipedia entry on KiCad: https://en.wikipedia.org/wiki/KiCad#/media/File:KiCad_3D_with_IDF.png The screenshot shows the new 3D Viewer rendering of the video demo board along with a VRML rendering of an exported IDF file. Perhaps thi

Re: [Kicad-developers] Eeschema toolbar button padding.

2015-06-19 Thread Nick Østergaard
It looks like they were added by JPC in rev 3119. 2015-06-20 0:14 GMT+02:00 Wayne Stambaugh : > Someone added the following code to all of the Eeschema toolbars: > > SetToolBorderPadding(2); // padding > SetToolSeparation(0); > > but none of the other app window toolbars have this (pcbnew, gerbvie

[Kicad-developers] Eeschema toolbar button padding.

2015-06-19 Thread Wayne Stambaugh
Someone added the following code to all of the Eeschema toolbars: SetToolBorderPadding(2); // padding SetToolSeparation(0); but none of the other app window toolbars have this (pcbnew, gerbview, cvpcb). I removed it and I cannot see any difference in the Eeschema toolbars. If no one can justify

Re: [Kicad-developers] [PATCH] Use new footprint selector for "Change Footprints"

2015-06-19 Thread Wayne Stambaugh
Chris, I'm not opposed to this patch. I actually prefer the footprint viewer over the footprint search dialog for two reasons. One, the footprint viewer uses lazy loading (it doesn't actually read the footprint files until you select a library) so there is no lag showing the viewer due to loadin

Re: [Kicad-developers] [PATCH] lib-cache-rescue upgrade

2015-06-19 Thread Wayne Stambaugh
I had a senior moment. You are correct. This should have been for your footprint exchange dialog patch. Sorry for the noise. I will reply to the correct email momentarily. On 6/19/2015 5:43 PM, Chris Pavlina wrote: > Am I just missing something, or did you reply to the wrong mail? ;) > > On F

Re: [Kicad-developers] [PATCH] lib-cache-rescue upgrade

2015-06-19 Thread Chris Pavlina
Am I just missing something, or did you reply to the wrong mail? ;) On Fri, Jun 19, 2015 at 05:37:16PM -0400, Wayne Stambaugh wrote: > Chris, > > I'm not opposed to this patch. I actually prefer the footprint viewer > over the footprint search dialog for two reasons. One, the footprint > viewer

Re: [Kicad-developers] [PATCH] lib-cache-rescue upgrade

2015-06-19 Thread Wayne Stambaugh
Chris, I'm not opposed to this patch. I actually prefer the footprint viewer over the footprint search dialog for two reasons. One, the footprint viewer uses lazy loading (it doesn't actually read the footprint files until you select a library) so there is no lag showing the viewer due to loadin

Re: [Kicad-developers] Questionable code

2015-06-19 Thread Mark Roszko
So I haven't been active for the last few months but I have been running coverity weekly at least ;) I noticed this one three months ago 4bool PNS_DIFF_PAIR_PLACER::tryWalkDp( PNS_NODE* aNode, PNS_DIFF_PAIR &aPair, bool aSolidsOnly ) 245{ 246PNS_DIFF_PAIR best; 247double bestScore = 1

Re: [Kicad-developers] Questionable code

2015-06-19 Thread Maciej Sumiński
Committed in 5794, thanks! Cheers, Orson On 06/19/2015 06:50 PM, Tomasz Wlostowski wrote: > On 19.06.2015 18:35, jp charras wrote: >> Among issues detected by Coverity, 3 of them worried me. >> (see attached text for these 3 Coverity bugs or strange things) >> >> - In shape_collisions.cpp , Colli

Re: [Kicad-developers] Questionable code

2015-06-19 Thread Chris Pavlina
This section was rewritten in the updated version I sent in yesterday, but the same bug exists in another place. Here's an updated version of the new patch. Alternatively, if you'd rather fix the existing version instead of applying the new patch, just change the line in question: 280

Re: [Kicad-developers] Questionable code

2015-06-19 Thread Tomasz Wlostowski
On 19.06.2015 18:35, jp charras wrote: > Among issues detected by Coverity, 3 of them worried me. > (see attached text for these 3 Coverity bugs or strange things) > > - In shape_collisions.cpp , CollideShapes compares 4 shapes. > One case ( SH_RECT / SH_RECT ) is strange, because the actual compa

[Kicad-developers] Questionable code

2015-06-19 Thread jp charras
Among issues detected by Coverity, 3 of them worried me. (see attached text for these 3 Coverity bugs or strange things) - In shape_collisions.cpp , CollideShapes compares 4 shapes. One case ( SH_RECT / SH_RECT ) is strange, because the actual compaison is SH_CIRCLE / SH_RECT. Is it OK (if yes, a

Re: [Kicad-developers] [PATCH] Autosave assertion failure workaround

2015-06-19 Thread Wayne Stambaugh
Fix committed in product branch r5787. Thanks. On 6/18/2015 10:23 PM, Chris Pavlina wrote: > Oops, the same thing has to be applied in pcbnew. Patch attached. > > On Thu, Jun 18, 2015 at 02:43:56PM -0400, Wayne Stambaugh wrote: >> Patch committed in product branch r5782. Thanks. >> >> On 6/16/2

Re: [Kicad-developers] Clarification regarding D_PAD::TransformShapeWithClearanceToPolygon

2015-06-19 Thread Mário Luzeiro
Thanks JP, thats it (width = 2*aClearanceValue). I understand, my question was just for "visual / dimensional proposes" understanding, so I now understand what that code is doing. Mario Luzeiro From: jp charras [jp.char...@wanadoo.fr] Sent: 19 June 2015 11

Re: [Kicad-developers] Clarification regarding D_PAD::TransformShapeWithClearanceToPolygon

2015-06-19 Thread jp charras
Le 18/06/2015 22:53, Mário Luzeiro a écrit : > Hello Jean-Pierre || all, > > @file board_items_to_polygon_shape_transform.cpp > @function D_PAD::TransformShapeWithClearanceToPolygon > @line 613 > https://github.com/KiCad/kicad-source-mirror/blob/0cab3e47ad8097db7b898b3cef2cf9b235318ca3/pcbnew/boar

Re: [Kicad-developers] [PATCH] 3d-viewer: Fix grid update by calling CreateDrawGL_List

2015-06-19 Thread jp charras
Le 18/06/2015 23:10, Martin d'Allens a écrit : > Hi all, > > Changing the grid size in the 3D viewer currently hides the grid until > some other display parameter is toggled. The reason is that the grid > should be explicitely rebuilt by calling CreateDrawGL_List(). The > attached patch should fix

Re: [Kicad-developers] Eeschema field autoplacing: second rev

2015-06-19 Thread Alejandro Méndez A .
This seems a great addon to KiCad. It would be great to have the same thing in PCBNew. Thanks! 2015-06-19 3:22 GMT+02:00 Chris Pavlina : > Here's the second revision of my Eeschema field autoplacing tool. The > following changes have been made: > > - Autoplace understands text justification > -

Re: [Kicad-developers] [PATCH] Fix to closing polylines in DXF imports

2015-06-19 Thread easyw
Hi Nick, I just make the opposite diff :) thanks! please find attached the right one... this small attached patch that could improve the DXF importing understanding... I add to the DXF import menu the info (R12 fully supported, units mm) so users will have this info immediately... [ documentatio