Re: [kicad] Multiple Track Dragging development investigations

> that key press '0' then dumps the logs to pns.log He he… you’re already father along than me then. ;) -- You received this message because you are subscribed to the Google Groups "KiCad Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [kicad] Multiple Track Dragging development investigations

At least some of the debug decorator can be turned on by putting “ShowRouterDebugGraphics=1” in your kicad_advanced file (a text file in your kicad preferences directory). I’m not sure if that turns on all of it or not…. I’ve only used the logging stuff once. I broke in the debugger and

Re: [kicad] Multiple Track Dragging development investigations

I use CLion rather than MS Visual Studio, but if I run KiCad from CLion then there’s a “Run” window where it dumps the stdout to. Did you find the debug decorator in the PNS Router code? It draws a bunch of graphical stuff on the canvas showing the start and end items, attempted paths, etc.

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

He he… yeah, this is one of the reasons our coding style discourages the use of “auto” — it tends to obfuscate the code. However, a lot of C++ programmers are used to using it, so it tends to creep in from time to time. The case given should read: for( const std::pair>& netclass :

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

ok wrote: > > > On 29/06/2021 12:39, Jeff Young wrote: >> Windows and Mac are single platforms, so the KiCad team builds those. We >> also build the Linux flatpak, which is statically linked (to 3.1). > > Except that the flatpak I installed yesterday is of version 5.1.10 and

Re: [Kicad-developers] Experience compiling latest HEAD

Windows and Mac are single platforms, so the KiCad team builds those. We also build the Linux flatpak, which is statically linked (to 3.1). It’s all the Linux distros that we can’t do much about. > I'm not saying it's ideal to use the possibly broken -dev version of wx, but > IMO it is worse

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

Hi Ruth, Are your 3D issues in raytracing or normal (OpenGL) rendering? Could you screenshot your Preferences > 3D Viewer > Display Options panel? (I’m unable to reproduce any of the issues you’re mentioning.) For unlock all you can do a Select All and then a right-mouse-button Unlock. You

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 to generate

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 this: > > (footprint

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

/projects/mockpp/ > <https://sourceforge.net/projects/mockpp/> > > BR, > SK > Dnia 17 stycznia 2021 16:45 Jeff Young napisał(a): > > I’ve used Mockito. Can’t say I remember a thing about it, though (which > could be good?). > > Cheers, > Jeff. > &g

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 done > > They are all

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 attempt is failing with

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 DRC is great. I

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 when starting up Pcbnew: > >

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 seems to have disappeared.

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?

xt( EDA_UNITS::MILLIMETRES ); >>>> >>>> It seems to me that if we're going to change the parameters to this >>>> function, we should pass a pointer to an EDA_DRAW_FRAME as a single >>>> parameter. If this parameter is nullptr, then we assume >>>

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

gt;> >>>> I'm finding some of the GetSelectMenuText() implementations format >>>> coordinate addresses for display. That means they need to use display >>>> origin transforms so the displayed coordinate matches what the user sees >>>> on t

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

>> transforms are currently available. >> >> Might someone more familiar with the data structures and calling >> sequences could suggest how this can best be accomplished? >> >> Seth, I'd appreciate it if you could bring your knowledge and expertise >>

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 manufacturers will

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

Hi Reece, > On 3 Jul 2020, at 21:32, Reece R. Pollack wrote: > > Noting that the PCB_BASE_FRAME class is derived from the EDA_DRAW_FRAME > class, is it acceptable to assume that the EDA_DRAW_FRAME pointer parameters > passed to functions in Pcbnew classes are actually pointers to a >

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 called PCB_UNIT_BINDER or

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

I find the backup files in the directory pretty annoying. While it’s not ideal I’m willing to completely lose the backup functionality to fix that. I’m also fine with building a more sophisticated system to folder them (ie: one that can handle the external files), but only if it’s going to

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

t to run the "recombine" command? Also I can see that > you'd end up joining up several pads together accidentally... I'd suggest the > "editing" mode should restrict editing to a single pad > > Roberto (Qbort) > > On Thu, 25 Jun 2020 at 21:53, Jeff Young <

Re: [Kicad-developers] GitLab milestone cleanup

Hi Jon, et al, So I’m still playing with WYSIWYG pad editing, but there’s no requirement for it in 6.0. If I find something that works well then I’ll merge it, but otherwise it will probably get pushed to the back-burner (ie: 7.0 & padstacks). So should it be in the milestone or not? Cheers,

[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

Did something change regarding how much of common is getting pulled into pcb_calculator? I’m getting the following link errors: Undefined symbols for architecture x86_64: "Kiface()", referenced from: EDA_BASE_FRAME::config() const in libcommon.a(eda_base_frame.cpp.o)

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

Some answers below: > On 20 Jun 2020, at 06:39, wrote: > > I wanted to add a feature to GerbView that relates to exporting a KiCad PCB > file from loaded Gerbers. I often use "Export to PCBNew..." to recreate > boards from Gerbers, and many of them involve Gerbers generated by Protel, >

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

: >>>> Rule 1) If mismatch > x, flag the "Trace length mismatch" as an error >>>> Rule 2) If mismatch > y, flag the "Trace length mismatch" as a warning >>>> >>>> When x > y and rule 1 is a higher priority, th

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

t; Min via diameter: generates DRCE_VIA_SIZE > Copper edge clearance: generates DRCE_CLEARANCE > Min through hole: generates DRCE_HOLE_SIZE > Hole to hole: generates DRCE_HOLE_CLEARANCE > uVia diameter: generates DRCE_VIA_SIZE > uVia drill: generates DRCE_HOLE_SIZE > > > > On Thu,

[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

The “Inside Keepout” issue might be a bad example. I’d definitely be in favour of folding all of those into a single violation because a keepout already specifies which types of things are excluded. But other things I’d be less in favour of. I want a warning about NPTHs in courtyards; I

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

onstraint is also correct. > > regards, > > Mark > > Jeff Young wrote: > > Hi Mark, > > That???s 6 change-lists too early for the fix. You need at least > d2cd4de280353b02ab66dab8e22e8da88415dc13. > > Cheers, >

Re: [Kicad-developers] DRC rules

an > do this, but it has consequences for the number of drc-rules I need. For > the big design I can constrain with 451 lines when I can use a default, > if that's not possible I need 7437 lines. > > There is also an overflow at some point. Two pads, one at (364, 218.5) > and the ot

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. > I still have

Re: [Kicad-developers] DRC rules

me in that case the last selector is applied and not the last > rule, correct? > > To be honest I prefer the selector/rule seperation, is that going to stay? > > regards, > > Mark. > > Jeff Young wrote: > > Hi Mark, > > The condition

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. > On 2 Jun 2020, at 11:05,

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 wrote: >

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

only matching items and removing others. > > Eeli Kaikkonen > > > On Sat, May 30, 2020 at 5:50 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > One strategy is to highlight the first match as you type, but leave the menu > entries unchanged. > > Another st

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

One strategy is to highlight the first match as you type, but leave the menu entries unchanged. Another strategy is to remove the un-matched entries (so the selected on is always at the top). I’m used to CLion, which removes, but the Scintilla Editor’s default is to just highlight. Which is

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, Andrea

Re: [Kicad-developers] DRC rules

do a DRC check if fails on the > pads of C1 and C2. I'm using cec857c0f49d4fd984a4095896306ff5d3a5930e, > not sure if you changed anything after that. > > To me the syntax is just fine, as long as these things can be specified > correcly. > > regards, > > Mark. >

Re: [Kicad-developers] DRC rules

Hi Mark, That’s expected. The effective clearance is the largest specified in all rules that match. Since both selectors match in the same-net case, the effective clearance is 1.3mm. There is a “relaxed” token to address this, which allows a higher-priority rule to relax a constraint. So

Re: [Kicad-developers] DRC rules

all permutations > and combinations of nets, but that would become a combinatorial nightmare! > > Yours, > James. > > > On Thu, May 21, 2020 at 11:29 AM Jeff Young <mailto:j...@rokeby.ie>> wrote: > Hi James, > > It sounds like you’re looking for hole-to-h

Re: [Kicad-developers] DRC rules

s achieved with what is currently there, but is the latter possible? > It's essentially a question of where via-to-via measurements are made. > > Thanks, > James. > > > > On Sat, May 16, 2020 at 4:44 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > I’ve just merged

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

Congrats on the first bug! Actually 4 separate ones: the caching mechanism was causing the rules to not be loaded when the board was read, the zone cutout stuff wasn’t fully hooked up to the new rules engine, there’s no "Net-(C1-Pad2)" netclass in the document (only "Net-(C1-Pad1)”), and the

Re: [Kicad-developers] DRC rules

Hi Mark, Clearances are in mm, so your clearances are *really* big. At a guess I’d say all the clearances are overflow when we multiply them by mm-to-nm, but I’d think that would give random results not no results. You shouldn’t need to set a priority unless you’re authoring a “relaxed”

Re: [Kicad-developers] DRC rules

(selector (match_type board_edge) (rule "Small Edge")) > (selector (match_layer "In1.Cu") (match_type board_edge) (rule "Big Edge") > (priority 2)) > > >> On 16 May 2020, at 16:43, Jeff Young > <mailto:j...@rokeby.ie>> wrote: >> >> I’ve

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

Hi James, You might first want to download one of the nightlies (5.99) and play with it. Block selections are gone: eeschema now has a “normal” selection model where you click on things and/or drag-select and they get highlighted. So from the GUI perspective you’d just need to add the options

Re: [Kicad-developers] DRC changes

l subject to the round-off errors > (https://gitlab.com/kicad/code/kicad/-/issues/4139 > <https://gitlab.com/kicad/code/kicad/-/issues/4139>)? > > -Ian > > On Sun, Apr 26, 2020 at 4:30 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > New bits up here: https://git

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

.kipro-pcb.com/>i...@kipro-pcb.com > <mailto:i...@kipro-pcb.com> ><https://twitter.com/KiProEDA> > <https://www.linkedin.com/company/kicad> > > On 2020-04-26 07:14, Jeff Young wrote: > >> So I set jeffyoung/kicad as a remote named "pub

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

ning is that your fork has the main branches marked as > protected still - since they are marked as protected in the main repo the > fork copies that setting over. > > -Ian > > On Sun, Apr 26, 2020 at 3:14 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > So I set jeffyoung/kica

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

jected] drc (pre-receive hook declined) This is all greek to me. Any ideas? Thanks, Jeff. > On 26 Apr 2020, at 14:58, Jeff Young wrote: > > Never mind. That page explains how to do the later. > > >> On 26 Apr 2020, at 14:56, Jeff Young > <mailto:j...@rokeby.ie&g

Re: [Kicad-developers] DRC changes

Never mind. That page explains how to do the later. > On 26 Apr 2020, at 14:56, Jeff Young wrote: > > And then the merge request, is that from jeff/kicad:jeffDRC to > jeff/kicad:master, or is there some way to do a merge request from > jeff/kicad:jeffDRC to kicad/co

  1   2   3   4   5   6   7   8   9   10   >