Re: [Kicad-developers] Missing zone segments

Am Mo., 15. Okt. 2018 um 17:29 Uhr schrieb Jeff Young : > Hmmm... I note looking at the code that we do read the old segment count > and if it’s <= 24 we use a 0.02mm acceptable error and if it’s greater than > 24 we use a 0.005mm. We could put a high/low resolution setting back in > the dialog

Re: [Kicad-developers] Missing zone segments

Hmmm... I note looking at the code that we do read the old segment count and if it’s <= 24 we use a 0.02mm acceptable error and if it’s greater than 24 we use a 0.005mm. We could put a high/low resolution setting back in the dialog (and write out 16 or 32 to keep from having to change the file

Re: [Kicad-developers] Missing zone segments

Hi Seth, The old method consisted of two hard-coded values, regardless of radius. It was replaced with a geometric algorithm which calculates the number of segments to use given a particular radius and acceptable error. We may need to adjust the error parameter a bit. (But the change

Re: [Kicad-developers] 5.0.1 release status.

Hi Wayne, There was a commit on master made for this purpose: 9a3cfb857. The function is to remove a failing test and thereby avoid having to exclude it from the CTest harness, which doesn't work on old Boosts. I thought it was in v5, but it is evidently not (and git branch --contains concurs).

Re: [Kicad-developers] 5.0.1 release status.

@JS: I figured that commit https://git.launchpad.net/kicad/commit/?id=9a3cfb8 does the trick when cherry picked on to the 5.0 branch... But that's all I can say. Cheers Ronnie Am Mo., 15. Okt. 2018 um 20:03 Uhr schrieb Wayne Stambaugh < stambau...@gmail.com>: > JS is on the mailing list. I

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

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

[Kicad-developers] Jenkins build is back to normal : linux-kicad-full-gcc-head #4150

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

Re: [Kicad-developers] Build error

Jeff fixed it with d62145fba9c35916631b3d. ma 15. lokak. 2018 klo 23.11 Eeli Kaikkonen (eeli.kaikko...@gmail.com) kirjoitti: > > > ma 15. lokak. 2018 klo 22.59 Wayne Stambaugh (stambau...@gmail.com) > kirjoitti: > >> The latest round of commits causes the following build error (at least >> on

[Kicad-developers] Build failed in Jenkins: linux-kicad-full-gcc-head #4149

See Changes: [jeff] Allow editing of library footprint from board reference. [jeff] Simplify exchange footprints dialog and support wildcards. [jeff] Place object borders in front of background fills.

Re: [Kicad-developers] Build error

ma 15. lokak. 2018 klo 22.59 Wayne Stambaugh (stambau...@gmail.com) kirjoitti: > The latest round of commits causes the following build error (at least > on windows). > > error: 'else' without a previous 'if' > In Linux, too. -Eeli Kaikkonen ___

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

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 error

The latest round of commits causes the following build error (at least on windows). C:/msys64/home/wstambaugh/src/kicad-trunk/pcbnew/pcb_edit_frame.cpp: In member function 'void PCB_EDIT_FRAME::InstallFootprintPropertiesDialog(MODULE*, wxDC*)':

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

See Changes: [jean-pierre charras] Try to fix the Jenkins link error -- Started by an SCM change Building remotely on debian8 (clang gcc linux) in workspace

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

See Changes: [jeff] Allow editing of library footprint from board reference. [jeff] Simplify exchange footprints dialog and support wildcards. [jeff] Place object borders in front of background fills. [jeff] Back out

Re: [Kicad-developers] Something odd with Eeschema GAL

BTW, I fixed the AdvanceDepth/Borders issue. The same strategy was *not* effective at fixing the dragged-objects-drawn-behind issue. Cheers, Jeff. > On 15 Oct 2018, at 19:11, jp charras wrote: > > Le 15/10/2018 à 18:58, Seth Hillbrand a écrit : >> Hi Jeff/JP- >> >> I pushed a small patch

Re: [Kicad-developers] Something odd with Eeschema GAL

Yep, fixes the OSX preferences issue too. (I’m backing out the patch to avoid it.) Well done, Seth! Cheers, Jeff. > On 15 Oct 2018, at 19:11, jp charras wrote: > > Le 15/10/2018 à 18:58, Seth Hillbrand a écrit : >> Hi Jeff/JP- >> >> I pushed a small patch to address this (bf164f7c4) >>

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

See -- Started by upstream project "linux-kicad-full-gcc-head" build number 4148 originally caused by: Started by upstream project "any-kicad-mirror-head" build number 3163

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

See Changes: [jean-pierre charras] Pcbnew, CMakeLists.txt: remove duplicate lines. For some reason, a few [jean-pierre charras] Cross probing: ensure highlighted net in Eeschema is shown when cross

Re: [Kicad-developers] Something odd with Eeschema GAL

Le 15/10/2018 à 18:58, Seth Hillbrand a écrit : > Hi Jeff/JP- > > I pushed a small patch to address this (bf164f7c4) > > The resize event triggered the compositor to change sizes.  This needed > to be locked to avoid the context writing into a bad size. > > Let me know if it still causes issues

Re: [Kicad-developers] 5.0.1 release status.

JS is on the mailing list. I suspect he will reply soon. On 10/15/2018 1:59 PM, Ronnie Gaensli wrote: > Hi all! > > I've been awaiting the 5.0.1 release to be officially available via the > ppa of js-reynaud. Though unfortunatley there's an issue with the > build:  >

Re: [Kicad-developers] 5.0.1 release status.

Hi all! I've been awaiting the 5.0.1 release to be officially available via the ppa of js-reynaud. Though unfortunatley there's an issue with the build: https://launchpad.net/~js-reynaud/+archive/ubuntu/kicad-5/+build/15533528 Actually it's the tests that cause the issue:

Re: [Kicad-developers] Something odd with Eeschema GAL

Hi Jeff/JP- I pushed a small patch to address this (bf164f7c4) The resize event triggered the compositor to change sizes. This needed to be locked to avoid the context writing into a bad size. Let me know if it still causes issues under W7 32. -Seth Am Mo., 15. Okt. 2018 um 08:39 Uhr schrieb

Re: [Kicad-developers] Something odd with Eeschema GAL

That’s the same bug that was being triggered on OSX with grid settings (and originally resulted in a deadlock before I switched GAL to RAII context locking). I spent a couple of days on it but came up blank (other than that I suspected it was a result of drawing into a wrongly-sized buffer,