Re: [Kicad-developers] 5.1.3 release

[Frank Severinsen]

Hi Eeli

Jeff disabled it during this fix: 


It's reenabled in nightlies, but I'm not sure if the router improvements are 
too big to put in V5.1 branch

Den 5. august 2019 kl. 15.42.16 +02.00, skrev Eeli Kaikkonen 
:

> 
> 
> 
> ma 5. elok. 2019 klo 16.02 Eeli Kaikkonen () 
> kirjoitti:
> 
> > A very quick notice and maybe alert. I just tried 5.1.4-4-g450dac4b1from 
> > Windows testing downloads. I can't drag vias with D. I will test further. 
> > It it's really a bug it may affect 5.1.4.
> > 
> > 
> I'm not sure what this is, but here's a screencast. What I do:
> 1. Press D on a via which is attached to tracks. Nothing seems to happen 
> until the cursor reaches a point where the via can be moved. Before that it 
> looks like non-functioning.
> 2. Press D on a stitching via. It doesn't move and nothing happens. 
> (Previously it was moved, although there was a bug which let it be placed to 
> violated DRC. So, maybe this is on purpose?)
> 3. Press G on a stiching via. It moves. Very good.
> 
> Because none of them was moved when I tried quickly with D I thought there's 
> some problem.
> 
> Ubtp0AruRO.mp4 
> 
> 
> Eeli Kaikkonen
> 
> 
> ___
> Mailing list: 
> Post to : 
> Unsubscribe : 
> More help : 
> 

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

Re: [Kicad-developers] 6.0 Zone filling differences

[Frank Severinsen]

hi Jeff

This actually also solves this: 

Den 21. juni 2019 kl. 00.49.55 +02.00, skrev Jeff Young :

> On the master branch in my repo 
> () I have pushed the new zone 
> algorithm, new solder mask shape generation, and new pad painting (which now 
> is the same as the plot code).
> 
> These changes address:
> 
>  (Anti-pad area should not 
> exclude spokes)
>  (Zone vs. Soldermask 
> clearance collisions at corners)
>  (Pcbnew: Zone clearance 
> inconsistency on rounded rectangle pads)
> 
> If folks could test it out on some of their boards that would be great.
> 
> Cheers,
> Jeff.
> 
> 
> 
> 
> 
> > On 20 Jun 2019, at 21:24, Jeff Young <> wrote:
> > 
> > 
> > Turns out there’s a slightly unintended side effect.
> > 
> > Before:
> > 
> > 
> > Note the two truncated thermal spokes to the surface-mount pads at the 
> > lower right.
> > 
> > After:
> > 
> > 
> > 
> > 
> > 
> > 
> > The bug is fixed, but not that the junctions between the spokes and the 
> > zone body are no longer chamfered.
> > 
> > I’d say the “after” is better in that respect too, but again it’s 
> > definitely different.
> > 
> > Thoughts?
> > 
> > Cheers,
> > Jeff.
> > 
> > 
> > 
> > 
> > > On 20 Jun 2019, at 19:50, Reece Pollack <> wrote:
> > > 
> > > 
> > > Memory is the second thing to go as one ages.
> > > 
> > > I can't remember what the first one is.
> > > 
> > > 
> > > 
> > > From:"Jeff Young" <>
> > > To:"jp charras" <>
> > > Cc:"KiCad Developers" <>
> > > Sent:Thursday, June 20, 2019 2:46:58 PM
> > > Subject:Re: [Kicad-developers] 6.0 Zone filling differences
> > > 
> > > 
> > > Wow. That’s sobering. I wrote the board outline clearance changes….
> > > 
> > > Age sucks.
> > > 
> > > 
> > > 
> > > 
> > > 
> > > > On 20 Jun 2019, at 19:04, jp charras <> wrote:
> > > > 
> > > > 
> > > > Le 20/06/2019 à 19:24, Jeff Young a écrit :
> > > > 
> > > > > I believe we now have a warning, but I can’t remember what change it 
> > > > > was for. I thought it was for the outline changes, but from what I 
> > > > > can find on the mailing list archive it looks like we were satisfied 
> > > > > that one wouldn’t change anything.
> > > > > 
> > > > > So remind me what the warning is for?
> > > > > 
> > > > AFAIK, it is for board outline clearance change (taking in accounf or
> > > > not the edge cut graphic items thickness, if I correctly remember).
> > > > Zone outline changes (only activated if the kicad_advanced
> > > > "ForceThickZones=0" option enables it), do not need any warning.
> > > > 
> > > > 
> > > > > 
> > > > > The reason behind this request is that I have a new fill algorithm 
> > > > > which fixes a long-standing bug regarding one pad’s thermal ring 
> > > > > knocking out another pad’s thermal spoke. It also allows thermal 
> > > > > spokes on custom pad shapes (and would allow us to support custom 
> > > > > number of spokes if we wished).
> > > > > 
> > > > > While this should only change zone fills which would have been 
> > > > > considered errors in the past, it nevertheless changes them. What’s 
> > > > > the prescription for that?
> > > > > 
> > > > > Cheers,
> > > > > Jeff.
> > > > > 
> > > > 
> > > > 
> > > > --
> > > > Jean-Pierre CHARRAS
> > > > 
> > > > ___
> > > > Mailing list:
> > > > Post to :
> > > > Unsubscribe :
> > > > More help :
> > > > 
> > > 
> > > ___
> > > Mailing list: 
> > > Post to : 
> > > Unsubscribe : 
> > > More help : 
> > > 
> > ___
> > Mailing list: 
> > Post to : 
> > Unsubscribe : 
> > More help : 
> > 
> ___
> Mailing list: 
> Post to : 
> Unsubscribe : 
> More help : 
> 

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

Re: [Kicad-developers] [PATCH] Crash Reporter

[Frank Severinsen]

Hi Wayne

Im guessing this one



Den 29. maj 2019 kl. 15.00.19 +02.00, skrev Wayne Stambaugh 
:

> Tom,
> 
> On 5/28/2019 12:13 PM, Tomasz Wlostowski wrote:
> 
> > On 27/05/2019 17:39, Seth Hillbrand wrote:
> > 
> > > On 2019-05-02 17:41, Tomasz Wlostowski wrote:
> > > 
> > > > On 02/05/2019 07:06, Wayne Stambaugh wrote:
> > > > 
> > > > > 
> > > > > By chance did you build with OCC instead of OCE which is what I am
> > > > > using? Please fix this when you get a chance, I would like to get this
> > > > > merged but I need to be able to test.
> > > > > 
> > > > > Why did your remove the GDK_* and GTK_* environment variables from
> > > > > APP_KICAD ctor? Wont this break the compatibility support we currently
> > > > > have?
> > > > > 
> > > > > I noticed quite a bit of trailing whitespace in patches 5 and 10 so 
> > > > > that
> > > > > will need to be cleaned up.
> > > > > 
> > > > > Please send me the link to your remote branch for this. It's easier 
> > > > > for
> > > > > me to just pull a branch into my repo than apply a large patch set 
> > > > > using
> > > > > `git am`.
> > > > > 
> > > > Hi Wayne,
> > > > 
> > > > Probably I screwed something up while rebasing the code on top of fresh
> > > > master. I'll check/fix the errors in the evening.
> > > > 
> > > > Greetings from CO,
> > > > Tom
> > > > 
> > > Ping!
> > > 
> > Done (tom-crash-reporter-may27 on my Github)!
> > 
> > Tom
> > 
> > 
> What is your github user name? I'm have trouble finding your crash
> reporter repo to test.
> 
> Thanks,
> 
> Wayne
> 
> ___
> Mailing list: 
> Post to : 
> Unsubscribe : 
> More help : 
> 

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

Re: [Kicad-developers] Via stitching

[Frank Severinsen]

Oops
one of the bug links should be: <https://bugs.launchpad.net/kicad/+bug/1731763>


Den 21. maj 2019 kl. 00.48.55 +02.00, skrev Frank Severinsen 
:

> Hi Guys
> 
> I'm currently attempting to add a smarter way of doing via stitching/fill.
> My plan is to make a new zone style, which will add vias in a preselected 
> grid, wherever DRC allows to.
> (related bug reports here: <https://bugs.launchpad.net/kicad/+bug/1754001> & 
> <https://bugs.launchpad.net/kicad/+bug/1754001> )
> More on this when it might seem likely I'll ever finish it.
> 
> Since I'm quite new at this, I'm trying to break it in to smaller pieces.
> First thing is to have the hasDRCViolation( VIA* aVia ) function handle the 
> minimum hole to hole distance set in DRC settings.
> 
> I have attached a patch which should add this functionality.
> 
> Any advice, critique etc is more than welcome.
> 
> PS:
> When using clang-format on the entire file, it more or less changed every 
> line in one way or another.
> should this be committed as well or is git clutter worse than codingstyle 
> issues?
> 
> kindest regards
> Frank Severinsen
> 
> ___
> Mailing list: <https://launchpad.net/~kicad-developers>
> Post to : 
> Unsubscribe : <https://launchpad.net/~kicad-developers>
> More help : <https://help.launchpad.net/ListHelp>
> 

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

[Kicad-developers] Via stitching

[Frank Severinsen]

Hi Guys

I'm currently attempting to add a smarter way of doing via stitching/fill.
My plan is to make a new zone style, which will add vias in a preselected grid, 
wherever DRC allows to.
(related bug reports here: <https://bugs.launchpad.net/kicad/+bug/1754001> & 
<https://bugs.launchpad.net/kicad/+bug/1754001> )
More on this when it might seem likely I'll ever finish it.

Since I'm quite new at this, I'm trying to break it in to smaller pieces.
First thing is to have the hasDRCViolation( VIA* aVia ) function handle the 
minimum hole to hole distance set in DRC settings.

I have attached a patch which should add this functionality.

Any advice, critique etc is more than welcome.

PS:
When using clang-format on the entire file, it more or less changed every line 
in one way or another.

should this be committed as well or is git clutter worse than codingstyle 
issues?
kindest regards

Frank Severinsen
From 4870ecae05c55f192aa14df3cd88864ff8dd10fa Mon Sep 17 00:00:00 2001
From: Frank Severinsen 
Date: Tue, 21 May 2019 00:28:03 +0200
Subject: [PATCH] Added Minimum hole to hole distance checking in via placing
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="2.20.1"

This is a multi-part message in MIME format.
--2.20.1
Content-Type: text/plain; charset=UTF-8; format=fixed
Content-Transfer-Encoding: 8bit

---
 pcbnew/tools/drawing_tool.cpp | 42 ---
 1 file changed, 29 insertions(+), 13 deletions(-)


--2.20.1
Content-Type: text/x-patch; name="0001-Added-Minimum-hole-to-hole-distance-checking-in-via-.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="0001-Added-Minimum-hole-to-hole-distance-checking-in-via-.patch"

diff --git a/pcbnew/tools/drawing_tool.cpp b/pcbnew/tools/drawing_tool.cpp
index b7f4f8345..e9a845535 100644
--- a/pcbnew/tools/drawing_tool.cpp
+++ b/pcbnew/tools/drawing_tool.cpp
@@ -750,7 +750,7 @@ int DRAWING_TOOL::DrawGraphicPolygon( const TOOL_EVENT& aEvent )
 SCOPED_DRAW_MODE scopedDrawMode( m_mode, MODE::GRAPHIC_POLYGON );
 
 m_frame->SetToolID( m_editModules ? ID_MODEDIT_POLYGON_TOOL : ID_PCB_ADD_POLYGON_BUTT,
-wxCURSOR_PENCIL, _( "Add graphic polygon" ) );
+wxCURSOR_PENCIL, _( "Add graphic polygon" ) );
 
 return drawZone( false, ZONE_MODE::GRAPHIC_POLYGON );
 }
@@ -1531,13 +1531,13 @@ int DRAWING_TOOL::DrawVia( const TOOL_EVENT& aEvent )
 {
 BOARD_ITEM* item = static_cast( it.first );
 
-if( !(item->GetLayerSet() & lset ).any() )
+if( !( item->GetLayerSet() & lset ).any() )
 continue;
 
 if( auto track = dyn_cast( item ) )
 {
 if( TestSegmentHit( aVia->GetPosition(), track->GetStart(), track->GetEnd(),
-( track->GetWidth() + aVia->GetWidth() ) / 2 ) )
+( track->GetWidth() + aVia->GetWidth() ) / 2 ) )
 possible_tracks.push_back( track );
 }
 }
@@ -1572,6 +1572,9 @@ int DRAWING_TOOL::DrawVia( const TOOL_EVENT& aEvent )
 
 view->Query( bbox, items );
 
+int holeToHoleMin = m_frame->GetBoard()->GetDesignSettings().m_HoleToHoleMin;
+
+
 for( auto it : items )
 {
 BOARD_ITEM* item = static_cast( it.first );
@@ -1594,7 +1597,16 @@ int DRAWING_TOOL::DrawVia( const TOOL_EVENT& aEvent )
 }
 }
 
-if( auto mod = dyn_cast( item ) )
+if( auto via = dynamic_cast( item ) )
+{
+if( KiROUND( GetLineLength( aVia->GetPosition(), via->GetPosition() ) )
+< aVia->GetDrillValue() / 2 + via->GetDrillValue() / 2 + holeToHoleMin )
+{
+return true;
+}
+}
+
+if( auto mod = dynamic_cast( item ) )
 {
 for( auto pad : mod->Pads() )
 {
@@ -1608,14 +1620,22 @@ int DRAWING_TOOL::DrawVia( const TOOL_EVENT& aEvent )
 net = pad->GetNetCode();
 clearance = pad->GetClearance();
 }
+if( pad->GetDrillSize().x
+&& pad->GetDrillShape() == PAD_DRILL_SHAPE_CIRCLE )
+{
+if( KiROUND( GetLineLength( aVia->GetPosition(), pad->GetPosition() ) )
+< aVia->GetDr

Re: [Kicad-developers] 5.1.1 issue

[Frank Severinsen]

a non-dev-lead +1 ;)

As a small side note there is a discussion on the forum to get a V5.1 branch 
"nightly" going.

This would hopefully help avoiding bugfix enduced bugs making it to stable.
I can imagine alot of people (including myself) who wants to help testing, but 
can't use nightlies due to the file fomat changes.



Den 21. april 2019 kl. 23.18.53 +02.00, skrev Wayne Stambaugh 
:

> It's looks like 5.1.1 has a serious issue which was fixed and will be
> released in 5.1.2. Since folks have already started downloading 5.1.1,
> I don't think changing the 5.1.1 tag is a good idea. How much trouble
> would it be to spin 5.1.2 and skip formally releasing 5.1.1? I'm fine
> if we use the 5.1.1 libraries, documentation, and translations as
> nothing has change since 5.1.1 that would effect anything. I figure
> this will give Adam some more time to get the macos release out. I
> apologize in advance for dropping the ball on this.
> 
> Cheers,
> 
> Wayne
> 
> ___
> Mailing list: 
> Post to : 
> Unsubscribe : 
> More help : 
> 

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

Re: [Kicad-developers] There seems to be an serious issue with netlist handling in KiCad 5.1.1

[Frank Severinsen]

Hi ThomasI have experienced this as wellIsn't it this issue?https://bugs.launchpad.net/kicad/+bug/1824764Kindest regards Frank Severinsen 21. apr. 2019 11.08 skrev Thomas Pointhuber :Hi,

 

I made a KiCad beginner workshop yesterday (with about 45 people), and at least two of the participants appared to run into serious issues regarding netlist handling. One of my colleguages as well (I hope he creates an bug-report soon).

 

The Issue appeared on KiCad 5.1.1, but it could be a regression already present in 5.1. Basically, it causes some nets to be not connected, which results in missing ratsnets in pcbnew as well as ERC errors (not-connected pads). Visually, all pins are shown as correctly connected in eeschema. In pcbnew those pads are not connected at all (so no ratsnets bug).

 

Dunno if this fix works for all people, but closing eeschema and opening it again causes a corrupted file warning (I think warning about an invalid netlist), which causes KiCad to create the netlist again and building a valid one which resolves the issue.

 

As summary: it seems there is a serious bug in KiCad 5.1.x which causes netlist errors and file corruptions.

 

I told everyone which had this problem to create a bug-report on launchpad to give some additional informations. If the issue is not found until KiCon, I would suggest to have one of the main-developers attend the beginner workshop to look for anyone having this issue and reproduce it.

 

Regards, Thomas

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

Re: [Kicad-developers] [PATCH] Option to not render 3D models for footprints

[Frank Severinsen]

Relateret bug report is here:bugs.launchpad.net/kicad/+bug/1766323The model preview does not remove it from the 3d view. Only in the footprint editor ___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] 5.1.0-rc1

[Frank Severinsen]

Thank you JS
Could you also enable GTK3, Phoenix etc for Nightly builds?

Kindest regards

Frank Severinsen

Den 11. februar 2019 kl. 17.11.51 +01.00, skrev Jean-Samuel Reynaud 
:

> Dear All,
> 
> PPA for KiCad 5.1 is now ready.
> When it's possible (for example on Ubuntu Bionic) GTK 3 is used, python3
> is enabled and WX4.0 too...
> 
> Don't hesitate to report any issues on ppa.
> 
> To use it:
> sudo add-apt-repository ppa:js-reynaud/kicad-5.1
> sudo apt-get update
> sudo apt install kicad
> 
> For the moment, as I see, no doc/templates/lib/footprint repo were tag
> 5.1.0-rc1 yet...
> 
> Note that for python plugins some refactoring can be needed when
> migrating to python3. According to <https://pythonclock.org/> perhaps it's
> time to switch any plugins to python 3 ;)
> 
> 
> 
> 
> 
> Le 08/02/2019 à 21:53, Marcos Chaparro a écrit :
> 
> > You are using GTK2 in this build. Are you building yourself? If so,
> > you need to delete the existing build directory, create a new one and
> > specify -DwxWidgets_CONFIG_OPTIONS="--toolkit=gtk3" in the cmake
> > options.
> > 
> > 
> > Its a nightly build
> > from http://ppa.launchpad.net/js-reynaud/kicad-dev-nightly/ubuntu bionic
> > main
> > 
> > Will start a build now and see if it fixes it. Shouldn't the packaged
> > deb for ubuntu bionic beaver (18.04) come with that cmake option set?
> > 
> > Thanks
> > 
> > ___
> > Mailing list: <https://launchpad.net/~kicad-developers>
> > Post to : 
> > Unsubscribe : <https://launchpad.net/~kicad-developers>
> > More help : <https://help.launchpad.net/ListHelp>
> > 
> 
> ___
> Mailing list: <https://launchpad.net/~kicad-developers>
> Post to : 
> Unsubscribe : <https://launchpad.net/~kicad-developers>
> More help : <https://help.launchpad.net/ListHelp>
> 

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

Re: [Kicad-developers] FOSDEM KiCad dinner.

[Frank Severinsen]

Hi Wayne

Added you to the group


Den 26. januar 2019 kl. 01.31.46 +01.00, skrev Wayne Stambaugh 
:

> Frank,
> 
> My phone number is 1-757-880-5981.
> 
> Cheers,
> 
> Wayne
> 
> On 1/25/19 7:15 PM, Frank Severinsen wrote:
> 
> > To the ones coming to Fosdem in a week.
> > I made a whatsapp group for all the Kicad people going.
> > It can be used for dinner planning, barcrawl, hangout, hackerspace meetups, 
> > or just finding each other at Fosdem (I was quite surprised how crowded it 
> > was last year).
> > Drop me an email with your phonenumber if you would like to be added to the 
> > group.
> > Kindest regards
> > Frank Severinsen
> > Den 7. januar 2019 kl. 18.40.00 +01.00, skrev Wayne Stambaugh 
> > <>:
> > 
> > > For those of you who don't know, the last few years at FOSDEM we have
> > > had a KiCad dinner on Saturday evening which was open to all. Last year
> > > we had well over 30 attendees which was very not manageable. This year
> > > we have decided to limit the size to 15. So far we have 4 confirmed
> > > attendees from the lead development team. I am now opening up requests
> > > to the developers on the development mailing list. This includes our
> > > library, documentation, and translation developers. Please RSVP me as
> > > soon as possible if you are interested. Resevations will be on a first
> > > come first serve basis until all 15 spots are reserved. Any remaining
> > > spots will be open to sponsors and then to the general public.
> > > 
> > > Cheers,
> > > 
> > > Wayne
> > > 
> > > ___
> > > Mailing list: <https://launchpad.net/~kicad-developers>
> > > Post to :  
> > > >
> > > Unsubscribe : <https://launchpad.net/~kicad-developers>
> > > More help : <https://help.launchpad.net/ListHelp>
> > > 

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

Re: [Kicad-developers] FOSDEM KiCad dinner.

[Frank Severinsen]

Hi WayneI would like to attend again this year. ___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Cost of different courtyard elements for the closed outline and DRC algorithms

[Frank Severinsen]

Hi JohnThat would be great! Ill be happy to help on the library side. Do you know what would be needed in the pcb file to make the test valid? Would 5000-1 0402 caps (or a more complicated part) lined up neatly be fine? Should they intersect to trigger the fault? Should it be different components?Im guessing the 5000-1 0402 should be fine, but im too familiar with the algorithm___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Cost of different courtyard elements for the closed outline and DRC algorithms

[Frank Severinsen]

@JohnRegarding the basic parts, René has scripted most of them including the most common packages. Adding the rounded courtyard to all resistors, caps, QFN's etc could be done quite easily and have the same amount of maintenance. That's why we wanted some dev input before going crazy with it.Any complex projects which could be Recommended for testing this? And is there a good way to only measure time of courtyard checks? ___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Cost of different courtyard elements for the closed outline and DRC algorithms

[Frank Severinsen]

Hi JohnRené added 2 links in the bottom. One of them is a complex shape for a mosfet, with roundings. Which ends up in a lot of 90 deg arcs. The other discussion is mainly when the courtyard is a spline, which has been discretized into arcs. Hence also the question if weird angles are slower. ___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] Cost of different courtyard elements for the closed outline and DRC algorithms

[Frank Severinsen]

JP it seems your email only went to Seth and not the mail list___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help   : https://help.launchpad.net/ListHelp

Re: [Kicad-developers] [RFC] wxPhoenix support

[Frank Severinsen]

Hi guys

If I understand it correctly, Python support should now be working again in 
nightly on newer linux distros.
at least in 18.10 it's doesnt seem like python or phoenix is enabled. Is this 
on purpose? If it should be ready to go it would be nice to have more testers.

Den 23. oktober 2018 kl. 16.22.18 +02.00, skrev Maciej Sumiński 
:

> I have briefly tested the branch with Phoenix/Python3/GTK3 and
> wxPython/Python2/GTK3 on Linux - no problems observed so far. Well done,
> thank you Thomas!
> 
> Cheers,
> Orson
> 
> On 10/23/18 3:56 PM, Thomas Pointhuber wrote:
> 
> > Hi Wayne,
> >
> > The console crash is already fixed in the merge request:
> > 
> > 
> > Regards,
> > Thomas
> > 
> > Am 22.10.18 um 18:36 schrieb Wayne Stambaugh:
> > 
> > > Hey Thomas,
> > >
> > > I looked over you merge request and it changes seem fine. I still need
> > > to test it but until the console crash issue is resolved, I will not
> > > approve the patch. Hopefully someone can help you out with the mutex
> > > locking issue.
> > > 
> > > Cheers,
> > > 
> > > Wayne
> > > 
> ___
> Mailing list: 
> Post to : 
> Unsubscribe : 
> More help : 
>

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

Re: [Kicad-developers] Filling Zones with the Kicad 5 python API

[Frank Severinsen]

And now I remember you use KiCad files instead of gerbers Sendt fra min Samsung Galaxy-smartphone. Oprindelig besked Fra: James Neal  Dato: 08/08/2018  20.29  (GMT+01:00) Til: kicad-developers@lists.launchpad.net Emne: [Kicad-developers] Filling Zones with the Kicad 5 python API Hey!We use the kicad python library to CAM boards for manufacturing.   One of the big issues we see in customer uploads is they fail to fill zones before saving the file, so we use this function:  def __Fill_All_Zones(self):    # Kicad doesn't refresh ground pours automatically during plotting    # This can lead to unusual errors if minor adjustments were made,    # and the designer didn't manually refresh.    # This glorious function added thanks to Adam Wolf    for zone_index in xrange(0, self.board.GetAreaCount()):      zone = self.board.GetArea(zone_index)      if not zone.GetIsKeepout():        #__Fill_Zone(self.board, zone)        zone.ClearFilledPolysList();        zone.UnFill();        if zone.GetIsKeepout():            return        zone.BuildFilledSolidAreasPolygons(self.board);        zone.SetIsFilled(True)It looks like zone.BuildFilledSolidAreasPolygons has been removed in the KiCAD 5 python API.  Was it replaced with something else, or is there a new way to do this?Thanks!-LaenOSH Park

___Mailing list: https://launchpad.net/~kicad-developersPost to : kicad-developers@lists.launchpad.netUnsubscribe : https://launchpad.net/~kicad-developersMore help   : https://help.launchpad.net/ListHelp



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

Re: [Kicad-developers] Filling Zones with the Kicad 5 python API

[Frank Severinsen]

Hi James V5 checks the zones by default when plotting, so this issue should hopefully be reduced by itself :) Sendt fra min Samsung Galaxy-smartphone. Oprindelig besked Fra: James Neal  Dato: 08/08/2018  20.29  (GMT+01:00) Til: kicad-developers@lists.launchpad.net Emne: [Kicad-developers] Filling Zones with the Kicad 5 python API Hey!We use the kicad python library to CAM boards for manufacturing.   One of the big issues we see in customer uploads is they fail to fill zones before saving the file, so we use this function:  def __Fill_All_Zones(self):    # Kicad doesn't refresh ground pours automatically during plotting    # This can lead to unusual errors if minor adjustments were made,    # and the designer didn't manually refresh.    # This glorious function added thanks to Adam Wolf    for zone_index in xrange(0, self.board.GetAreaCount()):      zone = self.board.GetArea(zone_index)      if not zone.GetIsKeepout():        #__Fill_Zone(self.board, zone)        zone.ClearFilledPolysList();        zone.UnFill();        if zone.GetIsKeepout():            return        zone.BuildFilledSolidAreasPolygons(self.board);        zone.SetIsFilled(True)It looks like zone.BuildFilledSolidAreasPolygons has been removed in the KiCAD 5 python API.  Was it replaced with something else, or is there a new way to do this?Thanks!-LaenOSH Park

___Mailing list: https://launchpad.net/~kicad-developersPost to : kicad-developers@lists.launchpad.netUnsubscribe : https://launchpad.net/~kicad-developersMore help   : https://help.launchpad.net/ListHelp



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