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

Hi all, As some of you know, I've been working on some new features for Eeschema that expand the capabilities of buses. These features are not yet complete, but I wanted to share my progress to get early feedback. Since there are a number of things, I have made a ~4 minute demo video, in which I

[Kicad-developers] Jenkins build is back to normal : kicad-noscript-fedora20 #2374

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

[Kicad-developers] Jenkins build is back to normal : kicad-qa #3161

See ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help

[Kicad-developers] Build failed in Jenkins: kicad-qa #3160

See Changes: [tomasz.wlostowski] poly2tri use std::runtime_error, fixes builds on many Linux -- Started by an SCM change Building remotely on debian8 (clang gcc linux) in workspace

[Kicad-developers] Build failed in Jenkins: kicad-noscript-fedora20 #2373

See Changes: [tomasz.wlostowski] poly2tri: throw exceptions instead of crashing on non-supported polygons [tomasz.wlostowski] PROGRESS_REPORTER: KeepRefreshing shouldn't block on non-OpenMP systems

[Kicad-developers] Build failed in Jenkins: kicad-qa #3159

See Changes: [tomasz.wlostowski] poly2tri: throw exceptions instead of crashing on non-supported polygons [tomasz.wlostowski] PROGRESS_REPORTER: KeepRefreshing shouldn't block on non-OpenMP systems [tomasz.wlostowski]

Re: [Kicad-developers] Some thoughts on symbol remapping

On 12/13/2017 01:56 AM, Oliver Walters wrote: > I finally had a chance to try the symbol remapping on a real project, > and I have a few thoughts on how I think it could be improved from a > users perspective (with code to back up my thoughts!) > > 1. "Remap" should replace "rescue" > > The

Re: [Kicad-developers] Eeschema fields in Pcbnew (RFC)

Great! I was unaware it already exported all the fields. -- Justin Partain On Wed, Dec 13, 2017 at 3:44 PM, José Ignacio wrote: > The netlist format already exports all fields by default. my tool [1] uses > a .net file as an input to generate BOM and macrofab XYRS

Re: [Kicad-developers] Eeschema fields in Pcbnew (RFC)

The netlist format already exports all fields by default. my tool [1] uses a .net file as an input to generate BOM and macrofab XYRS files. [1]: https://github.com/iromero91/bomtool On Wed, Dec 13, 2017 at 2:16 PM, Justin Partain wrote: > As a user, I do all my

[Kicad-developers] Inconsistent copper zone filling

Hello, I am seeing inconsistent zone filling for zones that should fill exactly the same way. Here is a screen shot to illustrate the problem. The GND zones for the the three phases should be filled like the middle one. Thanks, -Martin -- Martin Stoilov SigmaDrone - The Drone PC

Re: [Kicad-developers] Eeschema fields in Pcbnew (RFC)

As a user, I do all my scripting outside of Kicad. From a developer's POV, since Value/Reference fields are available to Python scripting, I can see that these should be too. What do you think about a third tab in the module edit dialogue, 'Fields', for these read-only fields? How does everyone

[Kicad-developers] [PATCH] Import PCAD PCB improvements

Hello guys. Can you check fixes of importing PCAD PCB files? >From 2418e51a94d27d43277297f00c1eba7f23886891 Mon Sep 17 00:00:00 2001 From: Eldar Khayrullin Date: Sun, 10 Dec 2017 21:18:21 +0300 Subject: [PATCH 04/10] pcad2kicadpcb_plugin: import circles ---

Re: [Kicad-developers] Eeschema fields in Pcbnew (RFC)

Hi Justin, I also use an XML netlist and a python script to generate pick and place files. I agree it would be much better to have it done in one step, so you have my vote. Do you foresee any user interface to display the fields imported from netlist? I imagine the fields would be read-only for

Re: [Kicad-developers] Eeschema fields in Pcbnew (RFC)

Le 13/12/2017 à 17:56, Justin Partain a écrit : > I understand Kicad is in feature freeze and getting ready to release soon, > this is an RFC for a > feature for Kicad 6.0 (or whatever is next). > > Proposition: add the ability to import custom fields from Eeschema into > Pcbnew via the netlist

Re: [Kicad-developers] Eeschema fields in Pcbnew (RFC)

This problem is actual for me too. Исходное сообщение От: Justin Partain Дата: 13.12.17 19:56 (GMT+03:00) Кому: Kicad Developers Тема: [Kicad-developers] Eeschema fields in Pcbnew (RFC) I understand Kicad is

Re: [Kicad-developers] Eeschema fields in Pcbnew (RFC)

Hi Justin, I am not a developer but I use KiCad for production too. I would love to see the custom fields propagated from the schematic to the board design. It would make P programming easier. I maintain some special keywords in the schematic custom fields for our manufacturing process too.

[Kicad-developers] Eeschema fields in Pcbnew (RFC)

I understand Kicad is in feature freeze and getting ready to release soon, this is an RFC for a feature for Kicad 6.0 (or whatever is next). Proposition: add the ability to import custom fields from Eeschema into Pcbnew via the netlist As a design engineer, I work closely with our production

Re: [Kicad-developers] OSX progress dialog patch

0001-A-different-workaround-to-the-OSX-progress-dialog-is.patch Description: Binary data On 13 Dec 2017, at 15:00, Nick Østergaard wrote:I don't see a patch attached to the forwarded email.2017-12-13 14:40 GMT+01:00 Jeff Young :(Resending with correct subject

Re: [Kicad-developers] All kinds of glitches because polygons don't have an origin. Also: Outline ?

Henner, Thank you for the message and your findings, I am sure they will be useful for fixing the problem. I turned this into a bug report, so it is not forgotten [1]. Cheers, Orson 1. https://bugs.launchpad.net/kicad/+bug/1738032 On 11/21/2017 06:26 AM, Henner Zeller wrote: > Hi, > I am

Re: [Kicad-developers] [PATCH] bugfix: OPENGL_GAL::DrawPolygon did not close closed polygons

Thank you Andreas, I have just pushed your patch to the master branch. Cheers, Orson On 12/10/2017 11:01 PM, Andreas Buhr wrote: > Dear Kicad developers, > > The polygon drawing routing in the OpenGL-GAL did > not plot polygons which are "closed", i.e. have a segment > from their last point to

Re: [Kicad-developers] OSX progress dialog patch

I don't see a patch attached to the forwarded email. 2017-12-13 14:40 GMT+01:00 Jeff Young : > (Resending with correct subject line.) > > > On 12 Dec 2017, at 22:53, Jeff Young wrote: > > > > Hi Maciej, > > > > Thanks for the workaround for the progress dialog on

Re: [Kicad-developers] remove outdated contribution

The latest another than Marco contributed to the kicad-i18n/it/kicad.po was about Jul 16, 2014. 2017-12-13 14:18 GMT+01:00 Wayne Stambaugh : > Marco, > > Before I apply this patch I need to certain that none or very few of the > Italian translations can be attributed to the

[Kicad-developers] OSX progress dialog patch

(Resending with correct subject line.) > On 12 Dec 2017, at 22:53, Jeff Young wrote: > > Hi Maciej, > > Thanks for the workaround for the progress dialog on OSX. The attached patch > is a similar workaround but preserves more of the progress window > functionality. Please

Re: [Kicad-developers] remove outdated contribution

Marco, Before I apply this patch I need to certain that none or very few of the Italian translations can be attributed to the translator that your patch removes. If there are still a significant number of translations that can be attributed to that translator, then your patch cannot be applied

[Kicad-developers] remove outdated contribution

This patch removes outdated translation contribution. The outcoming new version Italian translation was completely revised and updated so I think we can get rid of references to old and no more active contributors. TIA Regards, -- Marco Ciampa I know a joke about UDP, but you might not get

Re: [Kicad-developers] Partial fix for Bug #1737132

Hi Jean-Pierre, On 12/12/2017 07:00 PM, jp charras wrote: > Hi Orson, > > Could you have a look into this patch. > > It fixes the Bug #1737132 (component tree widget cleared in lib editor after > any change in symbol), > but there is still a minor issue. > > The reason the component tree

Re: [Kicad-developers] Some thoughts on symbol remapping

Le 13/12/2017 à 08:44, Oliver Walters a écrit : > jp, > > I was unaware of this new feature, that does perform a lot of the functions I > mentioned. This is a very recent feature. It was needed to allows global changes when a symbol has been renamed in a library or moved from a library to an