Re: [Kicad-developers] [RFC] Eeschema bus upgrades and new connectivity algorithm

2017-12-18 Thread Marco Ciampa
Hi Jon, first of all, thanks for listening my thoughts. I waited to send this letter a few days to wait for things to clear up to me. I think that this still apply although some things might be a little clearer now, so, in a way it is a little obsolete. I am sending it the same because I do not

[Kicad-developers] Information regarding unit tests.

2017-12-18 Thread kristoffer Ödmark
Hello! I just went through the ML and the docs. I found some tests in the qa folder that seemed related to the python scripting interface and some different documentation regarding testability from tomasz and the thread "simple C++ tests". Has there been added anything for doing tests in cpp

Re: [Kicad-developers] Library Editor Question

2017-12-18 Thread Wayne Stambaugh
Seth, This is mostly historical baggage. In my view, there should have been a SYMBOL_LIB_SCREEN to store and manipulate LIB_ITEM objects. Technically, LIB_ITEM objects should not be stored in an SCH_SCREEN object. The only reason we got away with it is both SCH_ITEM and LIB_ITEM are derived

Re: [Kicad-developers] New records with zone filling.

2017-12-18 Thread Wayne Stambaugh
Heikki, Thank you for the clarification. Merry Christmas and Happy New Year to you as well. Cheers, Wayne On 12/18/2017 8:22 AM, Heikki Pulkkinen wrote: > Hi Wayne, > > It is not in that way, and I did not ask that. > > Merry Christmas and happier new year for everyone. > > Heikki > > >

[Kicad-developers] Library Editor Question

2017-12-18 Thread Seth Hillbrand
​Oliver noticed an issue with the double-click handling as it is implemented in the Library Editor. The bug report is at https://bugs.launchpad.net/bugs/1738694 The issue comes down to the differences in how the library editor was tracking the current item as opposed to how this is done in the

Re: [Kicad-developers] [PATCH] Minor string fixes

2017-12-18 Thread jp charras
Le 18/12/2017 à 17:15, Simon Richter a écrit : > --- > common/page_layout/page_layout_reader.cpp | 2 +- > pcb_calculator/pcb_calculator_frame.cpp | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) I committed your patch. Thanks. -- Jean-Pierre CHARRAS

Re: [Kicad-developers] Question about zone to polygon transformation

2017-12-18 Thread jp charras
Le 18/12/2017 à 17:01, Andreas Buhr a écrit : > Hi all, > > when converting a zone to a polygon, the function > TransformRoundedEndsSegmentToPolygon > is called on each segment of the polygon describing the zone. This is > done to enlarge the polygon. This leads to a large number of polygons >

[Kicad-developers] [PATCH] Minor string fixes

2017-12-18 Thread Simon Richter
--- common/page_layout/page_layout_reader.cpp | 2 +- pcb_calculator/pcb_calculator_frame.cpp | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/common/page_layout/page_layout_reader.cpp b/common/page_layout/page_layout_reader.cpp index c7ce07a22..c96a775b7 100644 ---

[Kicad-developers] Question about zone to polygon transformation

2017-12-18 Thread Andreas Buhr
Hi all, when converting a zone to a polygon, the function TransformRoundedEndsSegmentToPolygon is called on each segment of the polygon describing the zone. This is done to enlarge the polygon. This leads to a large number of polygons describing the zone. Why isn't the polygon enlarged using the

Re: [Kicad-developers] macOS 3d-viewer improvements

2017-12-18 Thread Maciej Sumiński
Hi Bernhard, I tested your patches on Linux and Windows 7 and I have not noticed any problems, so I pushed them to the master branch. Thank you! Regards, Orson On 12/17/2017 10:55 PM, Bernhard Stegmaier wrote: > Hi Wayne, > > sorry, I obviously have copied a wx-3.1 only constructor. > Please

Re: [Kicad-developers] New records with zone filling.

2017-12-18 Thread Heikki Pulkkinen
Hi Wayne, It is not in that way, and I did not ask that. Merry Christmas and happier new year for everyone. Heikki On Sun, Dec 17, 2017 at 9:41 PM, Wayne Stambaugh wrote: > Heikki, > > I am replying to you directly to avoid any potential issues on the > developers