Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

Just the other day a user on IRC showed us this image of a hexagonal fill he hacked into his board by using bitmap2componet. Sort of a hack^3. 1) export gerbers and convert to PNG with gerbV 2) custom Python Imaging Library (PIL) script 3) bitmap2component https://i.imgur.com/ThqIz5Y.png Having

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

OK, Makes sense. On Tue, Mar 13, 2018 at 4:25 PM, jp charras wrote: > Le 13/03/2018 à 20:47, Jon Evans a écrit : > > I wonder if it might be a faster algorithm to calculate the perimeter > (and holes) of zones, offset > > it in by the zone thickness as a polygon, and then

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

Le 13/03/2018 à 20:47, Jon Evans a écrit : > I wonder if it might be a faster algorithm to calculate the perimeter (and > holes) of zones, offset > it in by the zone thickness as a polygon, and then draw in the grid as line > segments rather than as > more holes in the polygon? This is the

Re: [Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

I would not change anything. As long as your version increments as documented, there is no problem. But if you change that by jumping backwards, you create an exception that has the opportunity to bite people. So what if you skipped RC1 in your version string (and therefore in your

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

I wonder if it might be a faster algorithm to calculate the perimeter (and holes) of zones, offset it in by the zone thickness as a polygon, and then draw in the grid as line segments rather than as more holes in the polygon? On Tue, Mar 13, 2018 at 3:44 PM, jp charras

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

Le 13/03/2018 à 20:38, Jon Evans a écrit : > For the last point, you could use the approach I put in GerbView of start > measuring the time, and > then throw up a progress window if the time exceeds N seconds (with a button > to cancel the operation) > That way you don't even see the window on

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

For the last point, you could use the approach I put in GerbView of start measuring the time, and then throw up a progress window if the time exceeds N seconds (with a button to cancel the operation) That way you don't even see the window on small boards, but you get the feedback and can cancel

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

Le 13/03/2018 à 18:24, Seth Hillbrand a écrit : > Hi JP- > > I gave it a spin and definitely like it!  I have been using custom footprints > for capacitive > sensors, but this is much better.  A couple thoughts: > > 1) I'd prefer to have the angle saved as a parameter in the file rather than >

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

Hi JP- I gave it a spin and definitely like it! I have been using custom footprints for capacitive sensors, but this is much better. A couple thoughts: 1) I'd prefer to have the angle saved as a parameter in the file rather than a fixed list of options. 2) We'll definitely need to address the

Re: [Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

To prevent version issues for packagers, I will remove the -rc2 tag from the source repo and change the default (when git is not found) version string to 5.0.0-rc1-unknown to indicate that the version is somewhere between rc1 and rc2. I don't know that this makes things any clearer or not but I'm

Re: [Kicad-developers] who's responsible for translations?

The source translations are managed here: https://github.com/KiCad/kicad-i18n On 3/13/2018 12:43 PM, Tomasz Wlostowski wrote: > Hi all, > > Sorry for a possibly dumb question - I've been recently contacted by a > Polish translator who localized the V5 RC and submitted his > contributions to me.

[Kicad-developers] who's responsible for translations?

Hi all, Sorry for a possibly dumb question - I've been recently contacted by a Polish translator who localized the V5 RC and submitted his contributions to me. Who is officially responsible for managing translations of KiCad so that I could forward this stuff to appropriate person? Cheers, Tom

Re: [Kicad-developers] Making typed-in unit support more obvious

Thanks! Chris, your example link is dead but I'll use my imagination here. 1) I like the idea of making it more obvious. For 5, could we just add a tooltip? 2) I think that the extra step of only selecting the number is extraneous. Since we default to the document units, it doesn't matter if

Re: [Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

Am 13.03.2018 um 17:05 schrieb Eeli Kaikkonen: > 2018-03-13 17:44 GMT+02:00 Jon Evans : > >> I know what the G means, just wish git describe had an option to disable >> it, since it makes copy/paste more tedious. >> >> I think if we had left the tag at rc1, then we'd just have

Re: [Kicad-developers] Making typed-in unit support more obvious

Hi Seth, https://bugs.launchpad.net/kicad/+bug/1660156 Cheers, Jeff. > On 13 Mar 2018, at 15:39, Seth Hillbrand wrote: > > Hi Jeff- > > I can't find which bug report this can you send the link? I'm not sure that >

Re: [Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

2018-03-13 17:44 GMT+02:00 Jon Evans : > I know what the G means, just wish git describe had an option to disable > it, since it makes copy/paste more tedious. > > I think if we had left the tag at rc1, then we'd just have users thinking > they had rc1 when they really have a

Re: [Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

I know what the G means, just wish git describe had an option to disable it, since it makes copy/paste more tedious. I think if we had left the tag at rc1, then we'd just have users thinking they had rc1 when they really have a newer nightly. Better to make a new tag that doesn't include rcN in

Re: [Kicad-developers] Making typed-in unit support more obvious

Hi Jeff- I can't find which bug report this can you send the link? I'm not sure that I follow what the issue is and I'd like to understand the problem it's addressing. Thanks! -S 2018-03-13 2:58 GMT-07:00 Jeff Young : > There’s a wishlish item to make support for typed-in

Re: [Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

I think it would have been better if the commit after 5.0.0-rc1 was not tagged 5.0.0-rc2-dev. Then the git describe would make more sense. It would indicate that it was based on the 5.0.0-rc1 with additional commits and its hash. The g stands for git according to the man page.

Re: [Kicad-developers] [RFC] Experimental grid pattern in zone fill

Nice work! It may just be experimental, but it seems pretty close to a feature for 6.0 to me :-) I gave it a try on various boards I have worked on recently and it seems to work as advertised and is not noticeably slower than a solid fill on my computer. Assuming we work out any issues related

Re: [Kicad-developers] bug in numeric_evaluator?

Ah, right, I misread it. In the while condition isdigit() and isDecSep() will both return false for \0 and thereby exit the loop. It’s just a typo introduced when the new isDecSep() was implemented. That’s pretty funny that it works. Thanks for the clarification, Michael. Cheers, Jeff. >

Re: [Kicad-developers] Action python plugin: access to sch/net user fields

Hi guys. I wrote pcbnew action plugin for generating pos files. This is applicable for Russia now (uses russian transliteration). It is can easy changed for generating custom report files from pcb and sch. This plugin reads user fields from sch. https://github.com/KiCad-RU/kicad_plugins В

Re: [Kicad-developers] bug in numeric_evaluator?

It is a bug/typo that just happens to work. There is no need to check for \0. There used to be a comparison like "ch == clDecSep". Ugly but it should be safe for now. if( isDecSep( ch ) && sepCount ) break; should do the trick. - Michael On Tue, Mar 13, 2018 at 11:10 AM, Jeff Young

Re: [Kicad-developers] KiCad 5 RC1 fails to build on armel (mips, powerpc and ppc64el due undeclared initializer LIBCONTEXT_CALL_CONVENTION)

Hi up there, a small update for the issue on armel (armvt4, armvt5t). Am 09.03.2018 um 07:45 schrieb Carsten Schoenert: > PS: The build issue on armel is probably related to a missing '-mfpu=vfp > -msoft-float' option or similar, I will try to reproduce this on one of > my cubieboards. If

Re: [Kicad-developers] Need guidance/hints on accessing list of available pcbnew footprints from python

Hi Miles, Have you seen FOOTPRINT_VIEWER_FRAME::ReCreateFootprintList() (pcbnew/footprint_viewer_frame.cpp)? It might be the easiest way to go. Perhaps it could be wrapped in a function provided by the scripting interface. I could not find 'includefallback' option you have mentioned, would you

Re: [Kicad-developers] bug in numeric_evaluator?

Yuck. It’s clever code all right. The “correct” version would be: if( !ch || ( isDecSep( ch ) && sepCount ) ) break; but it’s a whole 3 characters longer. ;) I’ll fix this in my 6.0 tree (which already has libeval re-formatted to Kicad standards), but I suggest we leave it sleeping for

[Kicad-developers] Making typed-in unit support more obvious

There’s a wishlish item to make support for typed-in units more discoverable. I think the easiest way to do this is to adopt a policy of removing unit static-texts following a value textCtrl in favour of displaying the current units in the text. If the user clicks into the control and types

[Kicad-developers] Need guidance/hints on accessing list of available pcbnew footprints from python

In one of my python plugins, I want to know the list of available footprints (mounting holes, in this case) Digging through the code, I can't make heads or tails of how to get this information. There are a bunch of abstract class involved. impls There are a couple possibilities, none of

Re: [Kicad-developers] Deletion in plugins causing trouble

Thank you Miles, I have just pushed your patch. I agree with Wayne, one day we will need to revise the Python scripting interface. Regards, Orson On 03/06/2018 10:02 AM, miles mccoo wrote: > Thanks all for your replies. > > I like the plugin mechanism. It does some nice things for python folks.