Re: [Kicad-developers] Introduction of sentry application monitoring and error tracking

>> Thanks for putting in the work to get this integrated, Mark! +1 ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help :

Re: [Kicad-developers] Perplexing issue with Drawing sheet editor

They’re clipped to the page size. Any chance that got set to something really small (or in the wrong units) or something? Cheers, Jeff. > On 22 Feb 2022, at 17:57, Ruth Ivimey-Cook wrote: > > Folks, > > I've just been creating my first custom drawing sheet, and having

Re: [Kicad-developers] QA build failure

~~ > make[2]: *** [qa/pns/CMakeFiles/test_pns.dir/build.make:398: > qa/pns/CMakeFiles/test_pns.dir/pns_log_viewer.cpp.o] Error 1 > > > On 12/26/21 10:13 AM, jeff wrote: >> I’ve attempted to fix these, although they don’t appear to be part of the >> build target on m

Re: [Kicad-developers] QA build failure

I’ve attempted to fix these, although they don’t appear to be part of the build target on my machine so I can’t confirm. > On 26 Dec 2021, at 14:26, Wayne Stambaugh wrote: > > I'm seeing the following build failure this morning: > > /home/foo/src/kicad-trunk/qa/qa_utils/mocks.cpp:622:28:

Re: [Kicad-developers] New lead developer announcement

Awesome! Welcome aboard Mikolaj. > On 19 Nov 2021, at 14:28, Jon Evans wrote: > > Welcome Mikolaj! Happy to have you in this role :) > > -Jon > > On Fri, Nov 19, 2021 at 9:15 AM Wayne Stambaugh > wrote: > I am happy to announce that Mikolaj Wielgus has accepted

Re: [Kicad-developers] [OT-ish] Rotate while moving?

It works on my build (5.99). What version are you running? > On 15 Nov 2021, at 16:58, Brian wrote: > > Hi, > > I would swear that at one time in the past, while moving / grabbing a symbol > or footprint (M or G), I could rotate it in the midst of the move/grab > operation by pressing R.

Re: [Kicad-developers] Fwd: Crash invoking pcbnew Board settings

for them? (It= > does not for me on OSX. Speaking of which, can someone refresh my memory = > on the cmake instruction to turn on something like ASAN on OSX?) > > Cheers, > Jeff. > > On Sat, Nov 6, 2021 at 5:56 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: &

[Kicad-developers] Fwd: Crash invoking pcbnew Board settings

___ 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] Crash invoking pcbnew Board settings

a bad file, it’d still be nice to not crash on it.) Cheers, Jeff. > On 6 Nov 2021, at 01:59, Ruth Ivimey-Cook wrote: > > Hi > > I've been using the nightly build of kicad via flatpak (because of the > WxWidgets issues on Linux) for a while, and have encountered a fairly >

Re: [Kicad-developers] Problem compiling 5.1, maybe from commit 2975e859500

This normally happens when you’re building both 5.1 and 5.99 in a single tree. I have to delete them a lot as I do that. But I haven’t a clue how it’s supposed to be. When I have a working build (even if it’s clunky), I tend to be very hesitant to change anything. ;) > On 14 Sep 2021, at

Re: [Kicad-developers] Modifier Key Modification

Umm… how do you do a long-click on a track-pad set up for tapping? > On 5 Sep 2021, at 21:53, Seth Hillbrand wrote: > > Hi Folks- > > A final update to the 5.99 modifier key situation has been pushed. This > resolves a number of conflicting modifier keys for different actions. > > Part of

Re: [Kicad-developers] Experience compiling latest HEAD

> I presume KiCad 6 will be released after wx 3.2 is released (stated by their > releases page as 'hopefully in September 2021’). No, we won’t be waiting on wxWidgets to release. (I suspect their date is optimistic.) Cheers, Jeff. > On 29 Jun 2021, at 14:14, Ruth Ivimey-Co

Re: [Kicad-developers] Experience compiling latest HEAD

worse to use the actually broken "stable" version of it He he… yeah, that about sums up the state of wxWidgets. ;) Cheers, Jeff. > On 29 Jun 2021, at 11:44, Ruth Ivimey-Cook wrote: > > >> wxwidget 3.1 is the development version for the upcoming stable version >&

Re: [Kicad-developers] Experiences/feedback with 'nightly'

sided board (well, odd layer boards actually) is tracked in https://gitlab.com/kicad/code/kicad/-/issues/2425 <https://gitlab.com/kicad/code/kicad/-/issues/2425>. Cheers, Jeff. > On 28 Jun 2021, at 17:28, Ruth Ivimey-Cook wrote: > > I've been using the nightly build for the last

Re: [Kicad-developers] Default netlist

Can you look in your project file and see if it’s getting set? > On 11 May 2021, at 11:09, BERTRAND Joël wrote: > > Holger Vogt a écrit : >> In 5.99: Eeschema -> File -> Export -> Netlist > > Yes, I know. But dialog is always opened on default KiCAD netlist. > >

Re: [Kicad-developers] Default netlist

Hi Joël, Does it not remember the last setting? (It’s supposed to.) Cheers, Jeff. > On 11 May 2021, at 09:32, BERTRAND Joël wrote: > > Hello, > > In KiCAD 5.x, if I remember, there was a button to select default > netlist (and of course a button in main menu t

Re: [Kicad-developers] Updating Paths

Woot! > On 21 Mar 2021, at 14:41, Seth Hillbrand wrote: > > Hi All- > > I've submitted a series of merge requests to coordinate renaming the default > paths from "library" to "symbols" and from "modules" to "footprints" > > https://gitlab.com/kicad/code/kicad/-/merge_requests/741 >

Re: [Kicad-developers] Build error.

Ditto! > On 27 Feb 2021, at 13:55, Wayne Stambaugh wrote: > > Thanks! > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help :

Re: [Kicad-developers] PCB Calculator text problem

Huh. I thought wxWidgets auto-column-widths were only broken on GTK? > On 19 Feb 2021, at 18:04, David wrote: > > Done. Thanks. > > On 19/02/2021 17:52, Seth Hillbrand wrote: >> You can click Help->Report Bug >> >> Thanks- >> Seth >> >> On Fri, Feb 19, 2021 at 9:43 AM David >

Re: [Kicad-developers] question about XML BOM output

The elements are used by Pcbnew. We should probably suppress writing them in “BOM mode”. > On 19 Feb 2021, at 14:50, Jonatan Liljedahl wrote: > > Hi, > > When using jlcpcb-kicad-tools, it's tedious and error prone to fill in > the LCSC_Part for all components, so I'm thinking how to

Re: [Kicad-developers] some property field names are translated in kicad_pcb file

Hi Johann, That looks like a bug. Can you log it in GitLab? (Mostly so you can test it after I attempt to fix it.) Cheers, Jeff. > On 27 Jan 2021, at 10:45, Johann Wilhelm > wrote: > > Hi! > > I'm currently doing some parsing of PCB files and stumbled over thi

Re: [Kicad-developers] Odp: Re: Questions to the QA code

Good point. I have only used the Java one (which I guess is the original?). Cheers, Jeff. > On 20 Jan 2021, at 21:18, Sylwester Kocjan wrote: > > Hi Jeff, > > Did you use https://github.com/tpounds/mockitopp > <https://github.com/tpounds/mockitopp> or th

Re: [Kicad-developers] Questions to the QA code

I’ve used Mockito. Can’t say I remember a thing about it, though (which could be good?). Cheers, Jeff. > On 17 Jan 2021, at 14:49, Sylwester Kocjan wrote: > > Hello, > > On 17/01/2021 09:47, Alex wrote: > > ...GTest, Doctest and Catch2, (...) they'll all get the job d

Re: [Kicad-developers] Build problem of current master tree

I’m a 3rd-grader (at best) when it comes to cmake/build systems, so I’ll leave that one for others…. > On 2 Jan 2021, at 15:06, Carsten Schoenert wrote: > > Hello Jeff, > > Am 02.01.21 um 15:45 schrieb Jeff Young: >> Hi Carsten, >> >> Known problem when

Re: [Kicad-developers] Build problem of current master tree

Hi Carsten, Known problem when building 5.99 in a tree that used to hold 5.1. Try: cd include rm *_lexer.h Cheers, Jeff. > On 2 Jan 2021, at 14:00, Carsten Schoenert wrote: > > Hi, > > since a long time I'm trying to build a current version of 5.99 again. > But my

Re: [Kicad-developers] Odp: broken pipe and a simple commit

No worries. Everyone runs into it. > On 22 Oct 2020, at 12:22, Marco Ciampa wrote: > > On Thu, Oct 22, 2020 at 11:01:48AM +0100, Jeff Young wrote: >> I can’t see the pipeline reports (they’re all 404), >> but did you increase the CI timeout for your repo to 4 hours? >

Re: [Kicad-developers] Odp: broken pipe and a simple commit

I can’t see the pipeline reports (they’re all 404), but did you increase the CI timeout for your repo to 4 hours? (Our CI system is really slow.) > On 22 Oct 2020, at 10:42, Marco Ciampa wrote: > > On Thu, Oct 22, 2020 at 10:52:08AM +0200, Sylwester Kocjan wrote: >> Hi Marco, Did you

Re: [Kicad-developers] V6 Usability suggestion

Hi Brian, While it doesn’t directly address your suggestion, did you discover that you can also edit the severities by right-clicking on an actual DRC error (in the DRC dialog)? Cheers, Jeff. > On 21 Oct 2020, at 17:44, Brian Piccioni wrote: > > Hello > > The power new

Re: [Kicad-developers] New lead developer announcement.

Welcome Mark & Thomas! > On 7 Oct 2020, at 14:28, Chris Gammell wrote: > > Congrats, that's awesome! Wayne, can you post on the main site (blog) or the > forum as well so we can spread the word? > > On Wed, Oct 7, 2020 at 8:23 AM Wayne Stambaugh > wrote: > I am

Re: [Kicad-developers] Back Annotate - Ignore Other Projects

I think this is no longer used. If memory serves, it was used in multi-part warnings. (Now that we can independently back-annotate parts it no longer applies.) But someone should probably do a cursory poke around to see if that memory matches reality…. > On 28 Sep 2020, at 19:58,

Re: [Kicad-developers] Pad SHAPE, SH_RECT vs SH_SIMPLE

Check the value of m_orient. It sounds like it’s not exactly 0. (Or 900, 1800 or 2700.) > On 7 Sep 2020, at 08:41, Mário Luzeiro wrote: > > Here are the debug of some cases that has 4 points SH_SIMPLE > (51849001, 1150) (51849000, 1239) (52798999, 1240) (52799000, > 1151) >

Re: [Kicad-developers] D_PAD contributing to solder mask

IsOnLayer( F_Mask ) || IsOnLayer( B_Mask ) > On 6 Sep 2020, at 18:43, Mário Luzeiro wrote: > > Hi all, > what is the correct way to check that a D_PAD is contributing to solder mask? > eg: on the Pad Properties editor, the F.Mask or B.Mask is ticked.. > > Mario >

Re: [Kicad-developers] request for comment about perhaps clearer strings

I was thinking that but decided I must just be too much of a MOSFET-head. (Well, at least when I can’t find a suitable JFET.) > On 31 Aug 2020, at 17:37, Seth Hillbrand wrote: > > > > On Mon, Aug 31, 2020 at 9:30 AM Marco Ciampa > wrote: > On Mon, Aug 31, 2020 at

Re: [Kicad-developers] Placing real components out of a database instead of: "Automatic assignment of footprint with a database"

Awesome. You guys might lose me so I can go work on that…. > On 29 Aug 2020, at 16:07, Seth Hillbrand wrote: > > Calcite is a classic open source application. No ODBC driver but they > support queries in pig latin. > ___ Mailing list:

Re: [Kicad-developers] Placing real components out of a database instead of: "Automatic assignment of footprint with a database"

My point about MySQL wasn’t that *we* should bundle it, but rather why some of the contributors to this thread wanted to avoid it (or other things that support ODBC) and instead use CSV. ___ Mailing list: https://launchpad.net/~kicad-developers Post

Re: [Kicad-developers] Placing real components out of a database instead of: "Automatic assignment of footprint with a database"

Surely there must be an open source impl of an ODBC interface on a CSV file? Although I’m not sure of the desire to avoid MySQL. It’s remarkably easy to set up an instance (or auto-deploy one with an app). Apologies if we’ve already talked about that; I’ll confess to not having followed

Re: [Kicad-developers] running gerbview from local build on macOS

It’s a “thing” on OSX.  I run the attached script which fixes things up.  Sadly it has to be run after each build.I know Jon has the same issue, but I haven’t heard about it from Ian.  Perhaps he has a better solution….Cheers,Jeff. link_apps.sh Description: Binary data On 19 Aug 2020, at 10:32

Re: [Kicad-developers] Pcbnew - wxWidgets Debug Alerts on startup

I don’t see them. Can you drop into a debugger and give us the stack trace for each one of them? Thanks, Jeff. > On 18 Aug 2020, at 19:56, pjmo...@csi.com wrote: > > Is it just me or does anyone else get these "wxWidgets Debug Alert" > messages w

Re: [Kicad-developers] ERC Rules Options missing?

Schematic Setup. It got much bigger because you can now set the severities of all the errors. Cheers, Jeff. > On 8 Aug 2020, at 17:47, Brian Piccioni wrote: > > Hello > > I'm running my built Version: (5.99.0-2620-g2af4bd02a), release build. > > ERC Rules options seem

Re: [Kicad-developers] kicad | pcbnew: dragging leaves behind the courtyard (#5037)

My numeric dyslexia hath produced another great bug. Check out this video. ;) > On 2 Aug 2020, at 03:43, evils wrote: > > evils commented: > > @jeffyoung is this related? > > > 2020-08-02T04_41_10+02_00 >

Re: [Kicad-developers] DRC rules panel

To do syntax highlighting and code completion. > On 20 Jul 2020, at 14:41, Ben Ellis wrote: > > Why are the DRC rules parsed w/ s-exprs as they're being typed instead of > after? I just fixed a bug where typing ) without ( crashed the entire program >

Re: [Kicad-developers] Display origin transforms for DRC reports?

and the frame; I’d hate to see it lost. On the topic Jon and Ian were discussing (one parameter or two) I don’t have strong feelings. Cheers, Jeff. > On 10 Jul 2020, at 21:30, Jon Evans wrote: > > The way I see it, there is one package of information that we should > be delivering:

Re: [Kicad-developers] Display origin transforms for DRC reports?

I agree on both points: units and transform should be saved in the project file, and they should be passed to GetSelectMenuText as parameters. Cheers, Jeff. > On 10 Jul 2020, at 19:35, Jon Evans wrote: > > OK, I see. > > I have mostly stayed out of this conversat

Re: [Kicad-developers] Display origin transforms for DRC reports?

to GetSelectMenuText(). However, if the origin affects how to interpret the data in the file, then it should be in the BOARD/SCHEMATIC like Jon said (which is easy to access from the BOARD_ITEM or SCH_ITEM). Cheers, Jeff. > On 10 Jul 2020, at 18:25, Jon Evans wrote: > > Shouldn't t

Re: [Kicad-developers] Display origin transforms for DRC reports?

No, the DRC re-write won’t affect GetSelectMenuText(). It originated for describing items in the Clarify Selection menu, but it’s now used whenever we want to describe an item to the user. > On 10 Jul 2020, at 00:51, Reece R. Pollack wrote: > > On 7/9/20 7:09 PM, Tomasz Wlostowski wrote: >>

Re: [Kicad-developers] 3d-viewer: via diameter calculation off?

Our usage of “drill” in the terminology is pretty misleading. As far as I’m aware the vast majority of board houses treat it as “finish hole” diameter. Cheers, Jeff. > On 8 Jul 2020, at 23:00, Seth Hillbrand wrote: > > That really depends on the manufacturer. Many manu

Re: [Kicad-developers] Critical path item / request for help

I love this part: > wxPython4.0 (needed for Python3) And I thought our versioning was challenged. ;)___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] Assumptions about EDA_DRAW_FRAME in pcbnew

> On 4 Jul 2020, at 00:31, Reece R. Pollack wrote: > > On 7/3/20 5:42 PM, Jeff Young wrote: >> Hi Reece, >> >>> On 3 Jul 2020, at 21:32, Reece R. Pollack >> <mailto:re...@his.com>> wrote: >>> >>> Noting that the PCB

Re: [Kicad-developers] Assumptions about EDA_DRAW_FRAME in pcbnew

d push the origin (along with its getters and setters) down in to EDA_DRAW_FRAME. If this really is PCB-specific, then you can either push just the origin getters/setters down into EDA_DRAW_FRAME and override them in PCB_BASE_FRAME, or do a dynamic_cast to PCB_BASE_FRAME and if non-null call t

Re: [Kicad-developers] Derived class naming questions

PCB_UNIT_BINDER. No rule, so go with the prevailing practice. Cheers, Jeff. > On 3 Jul 2020, at 21:49, Reece R. Pollack wrote: > > Here's a coding standards question: > > Let's say I create a PCB-specific class derived from UNIT_BINDER. Should it > be call

Re: [Kicad-developers] Auto-generated backup files: are they useful?

to actually get done for 6.0. If it’s going to result in the can getting kicked further down the road, them I’d rather remove the feature. Cheers, Jeff. > On 30 Jun 2020, at 12:57, Nick Østergaard wrote: > > Last time I looked, there was rescue feature in the file menu of pcbnew, I &

Re: [Kicad-developers] Auto-generated backup files: are they useful?

How does the current backup file strategy interact with the autosave feature? If autosave works without it, that might address a lot of these concerns. > On 29 Jun 2020, at 23:13, hauptmech wrote: > > > While I agree that it is not KiCad's job to do archival backups or version > control,

Re: [Kicad-developers] WYSISYG pad editor

… if someone is using a polygon to do a neck-down to a pad, and we allow recombine to run in Pcbnew, then we’re going to suck that polygon into the pad definition. Maybe we do need to keep it Footprint Editor only.) Cheers, Jeff. > On 26 Jun 2020, at 17:05, Roberto Fernández Bautista > wrote: &

Re: [Kicad-developers] GitLab milestone cleanup

eers, Jeff. > On 26 Jun 2020, at 11:11, Ian McInerney wrote: > > In general, wishlist items should only be given a milestone if they are > either: > 1) Actively being worked on by a developer > 2) Currently on the plan for the release they are milestoned against (this > one

[Kicad-developers] WYSISYG pad editor

I implemented a prototype of a WYSIWYG custom-pad shape editor. You can ctrl-E on a pad and it explodes it and puts you into high-contrast mode with the shapes. After editing the shapes a second ctrl-E re-combines everything and exits high-contrast mode. While it’s pretty neat if you do

Re: [Kicad-developers] Compile issue

A clean build sorted it…. > On 23 Jun 2020, at 15:33, Ian McInerney wrote: > > The pcb calculator is a kiface (the bitmap 2 component is not though). The > Kiface() symbol is defined in `pcb_calculator.cpp`, and that hasn't changed. > > -Ian > > On Tue, Jun 23, 20

[Kicad-developers] Compile issue

CMakeFiles/pcb_calculator.dir/build.make:113: pcb_calculator/pcb_calculator.app/Contents/MacOS/pcb_calculator] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:2954: pcb_calculator/CMakeFiles/pcb_calculator.dir/all] Error 2 I don’t think pcb_calculator is supposed to have a Kiface()? Th

Re: [Kicad-developers] [Proposed Feature] GerbView - Mapping Gerbers w Altium extensions to KiCad PCB layers

aditional "i". Is this a KiCad thing, or > something specific to whatever developer(s) worked in the code I've looked at? It’s pretty random over a larger sample of code. Use either. > > 4 - The source files I've looked at only use the generic "int

Re: [Kicad-developers] Granularity of DRC error code

020 22:27, Jeff Young wrote: >> I had also originally planned on “compiling” the classic system into >> behind-the-scenes rules, but I don’t think that’s going to work out. It’s >> pretty easy to agree on priority of all the edge case (pad override, >> footprint overrides, n

Re: [Kicad-developers] Granularity of DRC error code

uniform about them. > On 11 Jun 2020, at 19:35, Jon Evans wrote: > > That has yet to be determined, IIRC. Jeff expressed a preference for > keeping around the current "basic rules" GUI we have, but that doesn't > answer whether those rules are internally represented

Re: [Kicad-developers] Granularity of DRC error code

nything that is a cost difference. I would only use > errors to mean "this can't be built at any cost from my preferred > manufacturer" or "this design won't work if I try to build it" > > On Thu, Jun 11, 2020 at 1:13 PM Jeff Young wrote: >> >> Ima

Re: [Kicad-developers] Granularity of DRC error code

e from via diameter is fine. > > Can you explain a situation where it makes sense to have e.g. > through-via drill be a warning but uVia drill be an error or > vice-versa? This is what I don't understand. > > On Thu, Jun 11, 2020 at 11:24 AM Jeff Young wrote: >> >

Re: [Kicad-developers] How do we envision Pad Stacks?

> On 11 Jun 2020, at 16:16, Wayne Stambaugh wrote: > > If not, we > need to create one to make sure we have it well defined before any > implementation can be done. Just to be clear: I’m not looking at implementing it. But I’d need to know what direction we were moving in *if* I were to

Re: [Kicad-developers] Granularity of DRC error code

(a production constraint) and via size (possibly just a current/heat constraint). I’m still on the fence with throughVia drill vs. uVia drill. The rest I can agree with. Cheers, Jeff. > On 11 Jun 2020, at 15:56, Jon Evans wrote: > > I think having fewer codes is something

[Kicad-developers] How do we envision Pad Stacks?

I had been assuming that you could define a separate shape for each layer. Full flexibility, but time-consuming to edit (even with commands such as “push current layer to other layers”). Most users are looking to route traces on inner layers between tight pads. This is commonly done with the

Re: [Kicad-developers] Granularity of DRC error code

and I still don't think you > need separate severities for those. > > On Thu, Jun 11, 2020 at 10:24 AM Jeff Young wrote: >> >> (But I do like being able to assign a severity to a rule.) >> >> On 11 Jun 2020, at 15:22, Jeff Young wrote: >> >> I think

Re: [Kicad-developers] Granularity of DRC error code

(But I do like being able to assign a severity to a rule.) > On 11 Jun 2020, at 15:22, Jeff Young wrote: > > I think we’d still need some sort of taxonomy to put the severities on for > the “classic” system. > >> On 11 Jun 2020, at 15:01, Ian McInerney > <mail

Re: [Kicad-developers] Granularity of DRC error code

(not separate > > > *rules* but separate violations) I still don't get the use case. > > > > > > As mentioned in the last taxonomy discussion, I still think we could > > > get rid of the tons of different "X close to Y" errors and just call > > &g

Re: [Kicad-developers] Granularity of DRC error code

in the nightlies. Cheers, Jeff > On 11 Jun 2020, at 06:19, Greg Smith wrote: > > I think more grouping in general categories is good. I also think that it > would be nice to exclude *specific* DRCs that once a designer checks the > error, they can flag it to ignore in the future. The

Re: [Kicad-developers] Build error: Now compiles for me.

Thanks, Dino! > On 10 Jun 2020, at 14:18, Dino Ghilardi wrote: > > No more build error on my machine (gcc 6.3.0) > > > Cheers, > Dino. > > On 10/06/20 14:52, Jeff Young wrote: >> I’ve merged an attempted fix. (Of course the previous one compiled fine

Re: [Kicad-developers] Build error

I’ve merged an attempted fix. (Of course the previous one compiled fine on CLang too, so I’m not 100% confident in it -- but it seem to fit the error GCC was generating.) > On 10 Jun 2020, at 12:59, Wayne Stambaugh wrote: > > I forgot to mention, lead devs please do not commit any new code

Re: [Kicad-developers] DRC rules

Hi Mark, We’ve seen something like that DRC error before. I think it was because the two items (the reported item and the correct item) had the same UUID. Can you check to see if that’s the case here? Thanks, Jeff. > On 4 Jun 2020, at 13:59, mdoes...@xs4all.nl wrote: > > Hello Jef

Re: [Kicad-developers] DRC rules

Hi Mark, That’s 6 change-lists too early for the fix. You need at least d2cd4de280353b02ab66dab8e22e8da88415dc13. Cheers, Jeff. > On 4 Jun 2020, at 10:13, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > I just tried version 9ff09aa784551264e89350368f61ed6b35266f7a, but >

Re: [Kicad-developers] DRC rules

Hi Mark, The hole clearance logic never got updated to pass both items (the track and the hole). It should work now. Cheers, Jeff. > On 2 Jun 2020, at 22:27, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > I've tried my big board and the clearances seem to work OK for planes.

Re: [Kicad-developers] DRC rules

Mark, Yes, last selector. Order of rules (at present) doesn’t matter. No, we were not planning on keeping the separation, although we did discuss supporting named conditions. Cheers, Jeff. > On 2 Jun 2020, at 13:00, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > I assu

Re: [Kicad-developers] DRC rules

Hi Mark, The condition syntax was just a preview. It’s not implemented yet. You’ll need to use the selector syntax for now. So, for instance: (selector (match_netclass "Net-(C1-Pad1)") (match_netclass "Net-(C1-Pad1)”) (rule “Min_Net-(C1-Pad1)") Cheers, Jeff. >

Re: [Kicad-developers] DRC rules

Hi Mark, Rules are now evaluated in order: last one which matches wins. Most of the time you won’t need priority, but if you do have two rules that match the same things, put the higher priority one later in the rules file. Cheers, Jeff. > On 2 Jun 2020, at 09:41, mdoes...@xs4all.nl wr

Re: [Kicad-developers] Poll: how does autocomplete filter?

Huh, appears things are pretty uniform. I wonder where the Scintilla folks came up with their model? Anyway, thanks. I’ll bend the Scintilla engine to our wishes. ;) Cheers, Jeff. > On 30 May 2020, at 17:11, Ian McInerney wrote: > > I am used to autocomplete tools only show

[Kicad-developers] Poll: how does autocomplete filter?

is more common? Which are you used to? Which do you like better? Cheers, Jeff. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help

Re: [Kicad-developers] Configure dialog shim in eeschema to be modeless instead of modal.

No. The dialogs would all have to be beefed up to listen to changes in the document and update their values, pointers, etc. We do have some work in progress for an Inspector, which would be modeless and show the selected items’ properties. Cheers, Jeff. > On 29 May 2020, at 19:31, And

Re: [Kicad-developers] DRC rules

Hi Mark, There are 4 or 5 bug fixes after the hash you’re using. The one I just pushed is most likely to address your pad-to-pad DRC issue. Cheers, Jeff. > On 21 May 2020, at 20:53, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > That works fine on the plane, but when I

Re: [Kicad-developers] DRC rules

uot;0.2mm" (clearance relaxed 0.2)) It’s worth noting that we’re not very happy with this syntax and are working on some other ways to address it. Cheers, Jeff. > On 21 May 2020, at 19:55, mdoes...@xs4all.nl wrote: > > Hello Jeff, > > I've tried to get the big board worki

Re: [Kicad-developers] DRC rules

While the prototype is selector-based the “real” implementation is likely to be expression-based, so you’ll be able to say something like: (rule “my special rule” … (condition “A.net <http://a.net/> == B.net <http://b.net/>”)) Cheers, Jeff. > On 21 May 2020, at 12:19, James

Re: [Kicad-developers] DRC rules

.) Cheers, Jeff > On 21 May 2020, at 10:54, James Jackson wrote: > > Hi Jeff, > > Many thanks for this - looks very powerful, and when it gets hooked in to the > PNS router will be killer. An issue I'm currently grappling with a variety of > rules considering placements ar

Re: [Kicad-developers] Requesting maintainership for KiCad manifest on flathub.org

Awesome! Welcome on board, Johannes. > On 18 May 2020, at 21:42, Jon Evans wrote: > > Hi Johannes, > > Thank you for offering to take on maintenance of the flathub package. > We are happy to have your help with this, and as far as I know none of > the other lead developers was planning on

Re: [Kicad-developers] DRC rules

ot;Net-(C1-Pad1)”), and the code responded poorly to failing to find a net (putting subsequent nets off-by-one). The third one is yours. ;) Fixes for the other three are now in master (if you build your own); otherwise you can get them from tonight’s nightly. Cheers, Jeff. > On 18 May 2020, at 12:01,

Re: [Kicad-developers] DRC rules

c net? (The later isn’t implemented, although maybe it needs to be.) Let me know how it goes with smaller clearances. If it still doesn’t work I may need a copy of your project to debug. Cheers, Jeff. > On 18 May 2020, at 10:18, mdoes...@xs4all.nl wrote: > > I've just tested this on a desi

Re: [Kicad-developers] DRC rules

I got tired of my text editor not highlighting matching parens so there’s now a basic rule editor in Board Setup > Design Rules > Rules. > On 16 May 2020, at 17:02, Jon Evans wrote: > > Thanks Jeff, this is awesome. I look forward to trying it out. > > On Sat, May 16,

Re: [Kicad-developers] DRC rules

_via) (rule "Big Hole")) (rule "Big Hole" (hole 2)) (rule "Small Edge" (clearance 2)) (rule "Big Edge" (clearance 3)) (selector (match_type board_edge) (rule "Small Edge")) (selector (match_layer "In1.Cu") (match_type board_edge) (ru

[Kicad-developers] DRC rules

I’ve just merged a possible implementation of the DRC rules. I’d like to get some feedback on it, and also some testing. (Because the rules support such a wide range of possibilities it’s going to need a good deal of testing.) For now, it picks up DRC rules from a file named “drc-rules” in

Re: [Kicad-developers] Eeschema annotate block / specific component types proposal

to the Scope section of the Annotate dialog. I believe there’s already a Wishlist item for this in the issue database. I suck at git, so you don’t want to know what I do for branching, etc. ;) Cheers, Jeff. > On 7 May 2020, at 14:19, James Jackson wrote: > > Hi all, > > First

Re: [Kicad-developers] DRC changes

In my simple test, the round-off errors are no longer an issue. But I don’t have that exact footprint. Could someone make the testcase (which fails on master) and send me the project + board? Thanks, Jeff. > On 26 Apr 2020, at 16:58, Ian McInerney wrote: > > Is it stil

Re: [Kicad-developers] DRC changes

New bits up here: https://gitlab.com/kicad/code/kicad/-/merge_requests/193 <https://gitlab.com/kicad/code/kicad/-/merge_requests/193> I claim this fixes the rotation problems and should markedly improve performance. Cheers, Jeff. > On 26 Apr 2020, at 15:48, Jeff Young wrote:

Re: [Kicad-developers] DRC changes

Yeah, rotated rectangles report negative clearances too…. > On 26 Apr 2020, at 15:40, Jeff Young wrote: > > Cool, I’ll look into that. > > I’ve also got some performance improvements to upload. > > Cheers, > Jeff. > >> On 26 Apr 2020, at 15:35, jp charras wr

Re: [Kicad-developers] DRC changes

—force does the trick. > On 26 Apr 2020, at 15:43, Jeff Young wrote: > > OK, I’ve turned mirroring off. Anyone know how to delete all the other > branches? (I tried through git, but of course run into the same “protected” > issue.) > >> On 26 Apr 2020, at 15:35, Se

Re: [Kicad-developers] DRC changes

OK, I’ve turned mirroring off. Anyone know how to delete all the other branches? (I tried through git, but of course run into the same “protected” issue.) > On 26 Apr 2020, at 15:35, Seth Hillbrand wrote: > > Hi Jeff- > > You do not want your fork to mirror KiCad. You don't

Re: [Kicad-developers] DRC changes

Cool, I’ll look into that. I’ve also got some performance improvements to upload. Cheers, Jeff. > On 26 Apr 2020, at 15:35, jp charras wrote: > > Le 26/04/2020 à 16:15, Jeff Young a écrit : >> Hi JP, >> >> Did they report the same number of err

Re: [Kicad-developers] DRC changes

Hi Ian, Yeah, I tried just pushing the branch first, but it does the same thing. I think I need to either delete all the other branches by hand, or turn off the “mirror” property (as that might force pushing of all branches). Cheers, Jeff. > On 26 Apr 2020, at 15:21, Ian McInerney wr

Re: [Kicad-developers] DRC changes

Hi JP, Did they report the same number of errors? Thanks, Jeff. > On 26 Apr 2020, at 15:03, jp charras wrote: > > Le 26/04/2020 à 14:27, Jeff Young a écrit : >> I have added code to many DRC errors which shows the minimum clearance, its >> source, and the actual clea

Re: [Kicad-developers] DRC changes

So I set jeffyoung/kicad as a remote named “public” and set as a mirror. But when I push to it I get a bunch of errors: Jeffs-MBP:kicad jeff$ git push public Enter passphrase for key '/Users/jeff/.ssh/id_rsa': Enumerating objects: 3601, done. Counting objects: 100% (2535/2535), done. Delta

  1   2   3   4   5   6   7   8   9   10   >