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

Re: [Kicad-developers] DRC changes

gt; > <https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html#creating-a-fork> > > -Ian > > On Sun, Apr 26, 2020 at 2:48 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > I don’t have a personal repo. Is it (reasonably) obvious how to create

Re: [Kicad-developers] DRC changes

Do I fork the project and put it in my “namespace”? > On 26 Apr 2020, at 14:47, Jeff Young wrote: > > I don’t have a personal repo. Is it (reasonably) obvious how to create one? > >> On 26 Apr 2020, at 14:32, Wayne Stambaugh wrote: >> >> Hi Jeff, >> &

Re: [Kicad-developers] DRC changes

ake it much easier > to test and avoid poluting the main repo with developers personal > working branches. > > Thanks, > > Wayne > > On 4/26/20 8:27 AM, Jeff Young wrote: >> I have added code to many DRC errors which shows the minimum clearance, >> its source, and th

[Kicad-developers] DRC changes

I have added code to many DRC errors which shows the minimum clearance, its source, and the actual clearance. The old DRC code was pretty heavily optimised around the idea of only needing to know if the clearance was violated (and not by how much), so a lot of it has been re-written. For this

Re: [Kicad-developers] What is a global variable, and why we don't need them.

This is indeed my particular problem. But copy/paste only recently started using the system clipboard, so that would have been an issue too. I can’t remember if the fixes for that are in 5.1 or 6.0…. > On 13 Apr 2020, at 04:23, Andy Peters wrote: > > > >> On Apr 12, 2020, at 6:50 AM,

Re: [Kicad-developers] What is a global variable, and why we don't need them.

Yeah, I can’t believe g_RootSheet hasn’t gotten us into more trouble. I guess most of the issues I’ve seen to-date with the globals have been between edit frames, and since only SCH_EDIT_FRAME uses sheets we’ve been OK. (That being said, the last one was SCH_EDIT_FRAME and PLOTTER getting in

[Kicad-developers] Removal of some globals

I had to remove some globals from Eeschema that were causing problems (default line width, text size, wire thickness, bus thickness etc.). It was a large change (as these things always are), so let me know if you see anything odd. Cheers, Jeff. ___

Re: [Kicad-developers] component or symbol?

Hi Marco, In the netlist, no, because the elements it refers to are called “component” in the netlist file. But everywhere else, yes. Cheers, Jeff. > On 5 Apr 2020, at 11:02, Marco Ciampa wrote: > > > #: pcbnew/dialogs/dialog_netlist.cpp:279 > msgid "Using reference designators to match

Re: [Kicad-developers] Inconsistency within l10n strings

Single quotes are much easier to read in the code (because they don’t require escaping). But, yeah, it would be nice to standardise on a single approach. Cheers, Jeff. > On 4 Apr 2020, at 19:10, Carsten Schoenert wrote: > > Hello Marco > > Am 04.04.20 um 20:05 schrieb Marco Ciampa: >> I do

Re: [Kicad-developers] Saving the pin-to-pin map

es will be in JSON format, at which point all the > wxConfig helper code will be deprecated/removed. > > On Thu, Mar 12, 2020 at 10:13 AM Jeff Young <mailto:j...@rokeby.ie>> wrote: > Hi Jon, > > Speaking of which, I note that we’re still using the PARAM_CFG stuff to

Re: [Kicad-developers] Saving the pin-to-pin map

ote: > > Project (it will be moved into a separate ERC settings file) > > On Thu, Mar 12, 2020 at 9:59 AM Jeff Young <mailto:j...@rokeby.ie>> wrote: > We don’t currently save the ERC pin-to-pin map (which I would think makes it > nearly useless). > > Shou

[Kicad-developers] Saving the pin-to-pin map

We don’t currently save the ERC pin-to-pin map (which I would think makes it nearly useless). Should it be project-relative, or global? Cheers, Jeff. ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

[Kicad-developers] Stroke font changes

I brought the time to open Eeschema for the first time from ~ 5 seconds to 1 by changing the stroke font from a 3-dimensional vector (character x stroke x points) to 3 vectors (the top two of pointers and the bottom of wxPoints). If you see anything fishy, it’s probably due to this….

Re: [Kicad-developers] DRC marker persistence

long list >>> of errors -- for that I just use clearing by type or by >>> multi-selection. Clearing (unlike ignoring) is not persisted in >>Altium. >>> >>> @Wayne - If we do decide to put them in project storage rather >>than the >>

Re: [Kicad-developers] DRC marker persistence

The current implementation has checkboxes below the list: [ ] All, [ ] Errors, [ ] Warnings, [ ] Exclusions. If you check Exclusions you’ll see them in the main list, but greyed out. (Strikethrough would have been better, but alas there’s wxWidgets in the way again.) > On 3 Mar 2020, at

Re: [Kicad-developers] DRC marker persistence

it will still ignore it. (The risk is that I might have moved them even closer together, and that while the first clearance violation was deemed acceptable, the second wouldn’t be. Then again, if you want to check again you can delete your ignore list.) Cheers, Jeff. > > Best regards

[Kicad-developers] DRC marker persistence

Part of the 6.0 DRC architecture is marker persistence. This will allow you to work your way through a large set of DRC violations, flagging those that have already been checked as exceptions or some-such. Two questions: 1) Store markers in board file or project file? Board file is much

Re: [Kicad-developers] DRC reports

of a tangent from the specific matter of > DRC settings -- they could always live in the Board Setup for now, and move > later if we decide to go in the direction I describe. > I do think that there should be no settings in the control dialog (other than > controlling reporting), but where

Re: [Kicad-developers] DRC reports

Oops, probably didn’t read your email carefully enough. You also mentioned project-level, so I assume you also mean Board Setup, not Preferences. > On 28 Feb 2020, at 11:26, Jeff Young wrote: > > I was thinking Board Settings. Some of them might be project-specific, no? > >&

Re: [Kicad-developers] DRC reports

M4i8ATsQVoWgNTytc0Ctw/edit# > > <https://docs.google.com/document/d/1r6tveX475pcCU-Gmv1rKIWM4i8ATsQVoWgNTytc0Ctw/edit#> > > -Jon > > On Wed, Feb 26, 2020 at 6:22 AM Jeff Young <mailto:j...@rokeby.ie>> wrote: > OK, I’m coming around to the idea of a hybrid system (tabs

Re: [Kicad-developers] DRC reports

OK, I’m coming around to the idea of a hybrid system (tabs + outline + severity filtering). Jon, could you post your violation taxonomy here? On the settings front, I do actually think they belong in a different dialog (a la Allegro). But we could have a right-button menu though that takes

Re: [Kicad-developers] wx asserts in macOS

I’d be inclined to leave them on for nightlies. That being said, the signal-to-noise ratio on the reports we get is pretty low, so I don’t feel strongly. > On 26 Feb 2020, at 05:21, Adam Wolf wrote: > > Hi folks! > > Right now, wx debug/asserts are turned on for macOS nightly builds, > but

Re: [Kicad-developers] DRC reports

hat exist (i.e. > empty top level sections would be suppressed) so it would not be too > cluttered. > > -Jon > > On Tue, Feb 25, 2020 at 5:27 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > Now that it’s a tree we could do the 3 level hierarchy pretty easily.

Re: [Kicad-developers] DRC reports

ons. > It seems like a better ultimate state would be: > (a) being able to turn on/off all types of violations (and set their severity) > (b) being able to clear or ignore certain violations or certain classes of > violations in one go (I was thinking via a context menu on each

[Kicad-developers] DRC reports

I’m looking at adding filtering to the DRC window. I’d like to use something similar to the HTML report panel where we’d have some checkboxes under the listbox: [ ] Show All [ ] Clearances [ ] Constraints [ ] Courtyards It would be nice and consistent to then have a Save button after

Re: [Kicad-developers] Proposal to update eeSchema annotation?

“Real” sheet numbering would be nice (ie: instead of page number times X, have a way to prefix by sheet start ref, and have a way to define that in the sheet). > On 22 Feb 2020, at 14:47, Brian Piccioni wrote: > > Hello > Now that Geographic Reannotation is a WIP I was thinking it might make

Re: [Kicad-developers] What does /path do in PCBNew files?

Pasting creates new timestamps. So copy/paste works fine, there’s just no way to do a unified copy/paste between eeschema *and* pcbnew. The timestamps are moving to UUIDs as we speak. The links are reset/updated when you do an Update PCB from Schematic and chose the “re-associate by

Re: [Kicad-developers] Broken Linux build

Yes, I also see the issue (on OSX). > On 7 Feb 2020, at 17:40, Jon Evans wrote: > > Wayne, can you revert the changes on lines 343-347 and add back -DDEBUG to > those four locations, keeping the added part around line 173 of the > CMakeLists.txt? > > If that fixes it, it tells us that for

Re: [Kicad-developers] What should I base my work on? 5.5 or 6?

I’ve been using 6.0 for boards. Just completed 5 of them. I’m not even using git with them. (But that’s because I’m an idiot. I’m also currently in the middle of re-ripping 500 CDs because I didn’t back up my music server either.) Cheers, Jeff. > On 5 Feb 2020, at 16:36, Seth Hillbrand

Re: [Kicad-developers] macos notarization status

Awesome! Great job, Adam. > On 4 Feb 2020, at 22:03, Adam Wolf wrote: > > Hi folks! > > Good news. > > On my dev machine, I've got the DMG, the apps, all the frameworks, > everything, all notarized. The apps are all signed even! > > We don't need to change the symlinks! (I'm a little

Re: [Kicad-developers] Welcome New Bug Squad members

Welcome, guys! > On 4 Feb 2020, at 14:15, Dino Ghilardi wrote: > > Congratulations Eeli and Simon! > > Dino. > > On 04/02/20 10:40, Seth Hillbrand wrote: >> Welcome to our newest Bug Squad members Eeli Kaikkonen and Simon Richter. >> As members of the Bug Squad, they help to verify, triage

Re: [Kicad-developers] [Kicad source code]

Hi Andrea, Have a look at SCH_DRAWING_TOOLS::PlaceComponent(). Cheers, Jeff. > On 3 Feb 2020, at 18:08, Andrea Martí wrote: > > Hi, > I posted this question on the kicad forums website and someone directed me to > the developer's mailing list instead of that forum. I have been looking into

Re: [Kicad-developers] Gitlab issue tracker

Never mind. It did close it, just with a time lag from the other changes. Cheers, Jeff. > On 3 Feb 2020, at 15:45, Ian McInerney wrote: > > It should automatically close them when you do that. > > -Ian > > On Mon, Feb 3, 2020 at 3:29 PM Jeff Young <mailto:j...@rok

[Kicad-developers] Gitlab issue tracker

I just used: /duplicate #2402 to mark a bug as a duplicate. Cool. But it didn’t close it. Do we want duplicates closed, or was that just how Launchpad did it? Cheers, Jeff. ___ Mailing list: https://launchpad.net/~kicad-developers Post to

[Kicad-developers] FOSDEM

Hi guys, Unfortunately I’ve had to cancel my FOSDEM plans due to an illness in the family. (While my daughter’s college roommate is actually from Wuhan, she didn’t go back to China for the term break so thankfully it’s not that at least.) Cheers, Jeff.

Re: [Kicad-developers] Rebase the tree?

check to make sure I didn’t bungle it again that would be great. Cheers, Jeff. > On 20 Jan 2020, at 23:43, Wayne Stambaugh wrote: > > No problem. Hopefully it wont cause too many issues for other devs who > have to rebase any local changes. > > Cheers, > > Wayne >

Re: [Kicad-developers] Rebase the tree?

Thanks, Wayne! Sorry for causing such a mess. Cheers, Jeff. > On 20 Jan 2020, at 22:32, Wayne Stambaugh wrote: > > I found it. I had to create a new protection for the master branch. I > pushed the changes and enabled the GitLab protection for the master > branch so we should be good to

[Kicad-developers] Bug in the new RTREE stuff

Hi Seth, I found an odd bug in the new RTREE stuff: Open a schematic. Click on a symbol’s reference. It gets highlighted. Now nudge it my pressing M and then one of the arrow keys. Click on something else and then try to select the reference again. You’ll get the disambiguation menu

Re: [Kicad-developers] Coverity heads-up

rs which I believe is the only exception that boost pointer > containers throw? Ignoring out of memory errors is not an acceptable > option. These issues will need to be address in order to convert over > to the standard c++ containers. > > Cheers, > > Wayne > > On 1/12/20

[Kicad-developers] Coverity heads-up

I’ve given up chasing down all the places where we fail to catch boost exceptions. I’m removing boost::ptr_vector in favour of std::vector (which boost uses under the hood anyway). ___ Mailing list: https://launchpad.net/~kicad-developers Post to

Re: [Kicad-developers] Coverity finds an ugly bug in wxWidgets

pers > On > Behalf Of Ian McInerney > Sent: 12 January 2020 12:24 > To: Jeff Young > Cc: KiCad Developers > Subject: Re: [Kicad-developers] Coverity finds an ugly bug in wxWidgets > > I thought that Wayne was agreeing with requiring them on all lengths of > stateme

Re: [Kicad-developers] Coverity finds an ugly bug in wxWidgets

We could also just require them on if/then/else statements…. > On 12 Jan 2020, at 00:35, Jeff Young wrote: > > Sure, but unless we go with Seth’s option, then it’s just going to happen > again…. > >> On 11 Jan 2020, at 23:28, Wayne Stambaugh > <mailto:stambau...@

Re: [Kicad-developers] Coverity finds an ugly bug in wxWidgets

ilto:s...@kipro-pcb.com <mailto:s...@kipro-pcb.com>>> wrote: >> >>I suppose that we could update our coding policy to require braces >>even for single line statements. >> >>-Seth >> >>On Jan 11, 2020 1:28 PM, Jeff Youn

[Kicad-developers] Coverity finds an ugly bug in wxWidgets

This looks safe enough: if( n_changed ) wxLogTrace( "CN", "Cluster %p : net : %d %s\n", cluster.get(), cluster->OriginNet(), (const char*) cluster->OriginNetName().c_str() ); else wxLogTrace( "CN", "Cluster %p : nothing to propagate\n", cluster.get() ); Sadly, the macro

Re: [Kicad-developers] Markdown issue

There’s also this one in Markdown: https://scan8.coverity.com/reports.htm#v33181/p10844/fileInstanceId=29813788=10144552=125666 > On 11 Jan 2020, at 20:32, Jeff Young wrote: > > Could someone familiar with Clipper have a look at this one: > > https://scan8.coverity.com/rep

[Kicad-developers] Clipper issue

Could someone familiar with Clipper have a look at this one: https://scan8.coverity.com/reports.htm#v33181/p10844/fileInstanceId=29818824=10144638=102371 Thanks,

Re: [Kicad-developers] unreleased wxFormBuilder

I think OSX was one of the laggards, but I’m now on 3.9.0. Cheers, Jeff. > On 5 Jan 2020, at 12:57, Simon Richter wrote: > > Hi, > > we've been asked on IRC about a dire warning "you WILL lose data if you > save" from wxFormBuilder when opening some of the files. Apparently > there are new

Re: [Kicad-developers] Question about gerber job file numeric format

st plan. > > -Jon > > On Tue, Dec 24, 2019, 13:54 Jeff Young <mailto:j...@rokeby.ie>> wrote: > Safest would be (b). > > We could probably do something pretty dumb (ie: set a single value in the > JSON printer which it uses for precision). > >>

Re: [Kicad-developers] Question about gerber job file numeric format

Safest would be (b). We could probably do something pretty dumb (ie: set a single value in the JSON printer which it uses for precision). > On 24 Dec 2019, at 15:22, Jon Evans wrote: > > Hi all, > > The Gerber job file specification[1] says that the format follows the JSON > standard, and

Re: [Kicad-developers] Folks doing their own Mac builds will want to fetch from our local wxWidgets branch...

\ > --with-regex=builtin \ > --with-libtiff=builtin \ > --with-zlib=builtin \ > --with-expat=builtin \ > --without-liblzma \ > --with-macosx-version-min=10.14 \ > CC=clang \ > CXX=clang++ > > Thanks, > -Ian > > On Sun, De

Re: [Kicad-developers] Folks doing their own Mac builds will want to fetch from our local wxWidgets branch...

ince that typdefs wxChar into char, and we get an > error). Is there another configure flag you pass to still use Unicode by not > UTF8? > > Thanks, > -Ian > > On Sat, Aug 10, 2019 at 11:18 AM Jeff Young <mailto:j...@rokeby.ie>>

Re: [Kicad-developers] Connection graph question

I was going to say that if they’re now a copy we could simplify the draw code a bit. But I see Wayne has already done that. :) Cheers, Jeff. > On 12 Dec 2019, at 08:57, Jonatan Liljedahl wrote: > > On Thu, Dec 12, 2019 at 12:01 AM Wayne Stambaugh wrote: > >> Now that the LIB_PART of the

[Kicad-developers] Editing stroke font

Is there a tutorial anywhere on editing the stroke font? We seem to be missing the Ω symbol…. ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe :

Re: [Kicad-developers] GitLab bug workflow

> > Speaking of which @Maciej Suminski <mailto:maciej.sumin...@cern.ch> can you > modify the current janitor "nudger" that emails people if they close an issue > with no milestone to work with GitLab? > > -Ian > > On Wed, Dec 4, 2019 at 11:10 AM Jeff Young <

Re: [Kicad-developers] GitLab bug workflow

Hmm… just noticed that some of the non-released bugs are coming in a Closed, so we appear to be going from Open to Closed at Fix-Committed. So do we still want to add the Fix-Committed tag to new bugs, or just Close them? > On 4 Dec 2019, at 11:09, Jeff Young wrote: > > F

[Kicad-developers] GitLab bug workflow

Forgive me if this was communicated and I missed it, but when do we transition a GitLab bug from Open to Closed? At Fix-Committed or Fix-Released? And are those two tags just for migrated bugs, or will we continue to use them for new bugs? Thanks, Jeff.

Re: [Kicad-developers] Strokefont change from std::deque to std::vector

OK, my stuff is pushed > On 3 Dec 2019, at 17:44, Jeff Young wrote: > > He he… I had sort of the same idea, only I’m building it lazily at runtime. > But I think your idea would be even better. > > Since I’ve already made the changes to have STROKE_FONT use const point

Re: [Kicad-developers] Strokefont change from std::deque to std::vector

, Jeff. > On 3 Dec 2019, at 17:40, Seth Hillbrand wrote: > > On 12/3/19 7:27 AM, Jeff Young wrote: >> Hi Seth, >> >> Trying to keep track of lengths is going to be ugly. I did re-write the >> bounding-box calc (which saves a bunch), and re-mapped the initialisati

Re: [Kicad-developers] Strokefont change from std::deque to std::vector

t; > On Tue, Dec 03, 2019 at 03:27:26PM +0000, Jeff Young wrote: > >> Changing the glyph back to a deque (and leaving the strokes vectors) would >> probably alleviate much of the performance hit — but I’m not sure if it >> would bring back the memory issues or not. >

Re: [Kicad-developers] Strokefont change from std::deque to std::vector

bring back the memory issues or not. Cheers, Jeff. > On 3 Dec 2019, at 00:57, Seth Hillbrand wrote: > > On 12/2/19 3:45 PM, Jeff Young wrote: >> Hi Seth, >> >> What was the reason for the change from std::deque to std::vector? Building >> the stroke font is n

Re: [Kicad-developers] Project leader announcement

Excellent news! > On 3 Dec 2019, at 14:39, Seth Hillbrand wrote: > > On 2019-12-03 06:28, Wayne Stambaugh wrote: >> I wanted keep everyone up to date with my employment situation since my >> termination from WIT. I am excited to announce that I have joined the >> KiCad Services Corporation[1]

[Kicad-developers] Strokefont change from std::deque to std::vector

Hi Seth, What was the reason for the change from std::deque to std::vector? Building the stroke font is now accounting for 50% of document load time (I think because we’re using a 2D vector so that any resize of any constituent vector has to reallocate the whole shebang). We also load the

Re: [Kicad-developers] Git fixes migration

ng the launchpad janitor tag >> will close the bug now that the launchpad repo is a mirror. You can >> push it to the gitlab repo an see what happens. If it doesn't work, you >> will have to manually change the bug status in Launchpad.it s >> On 12/2/19 8:32 AM, Jeff Young w

Re: [Kicad-developers] v6 roadmap and schedule (was Re: 5.1.5 released.)

There’s some great stuff in here though on some of the topics we are doing. I’m not sure how best to work in to the email discussions that are bound to come up, but I’ve flagged it in my email inbox. Cheers, Jeff. Oh, and for what it’s worth, our main UI guy spent 25 years at Adobe, and uses

[Kicad-developers] Git fixes migration

So I just fixed a bug. Can I still use the Launchpad ID in a “git fixes” statement, or do I need to wait until it has a git number? ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe

Re: [Kicad-developers] Which GitLab issues tracker are we going to use?

t. The other lists (KiCad and KiCad/code) just show > all issues for all the projects underneath that folder. > > -Ian > > On Sun, Dec 1, 2019 at 8:51 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > Kicad, Kicad/code or Kicad/code/kicad? > >

[Kicad-developers] Which GitLab issues tracker are we going to use?

Kicad, Kicad/code or Kicad/code/kicad? ___ 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] Fix lp:1849376

Didn’t someone do a couple of icons recently that looked nice? Ian or Michael maybe? (I was hoping to get a new icon for something or another too, although I can’t remember what now….) > On 27 Nov 2019, at 08:00, Franck Jullien wrote: > >> I took a look at the intersheet reference patch and

Re: [Kicad-developers] New Official Bug Tracker Tags

n. > > -Ian > > On Tue, 26 Nov 2019, 8:07 p.m. Jeff Young, <mailto:j...@rokeby.ie>> wrote: > I would go with either historic (modedit and libedit) or current (fp_editor > and symbol_editor). > > Mixing the two would be particularly obscure. > > Cheers, >

Re: [Kicad-developers] GitLab migration

mediately > so we can resolve it. > > Cheers, > > Wayne > > On 11/26/19 8:13 AM, Jeff Young wrote: >> Was there a resolution on the 2FA question? (I used to have to use it for >> Adobe’s VPN and hated it, but it is what it is.) >> >> I assume g

Re: [Kicad-developers] New Official Bug Tracker Tags

I would go with either historic (modedit and libedit) or current (fp_editor and symbol_editor). Mixing the two would be particularly obscure. Cheers, Jeff. > On 26 Nov 2019, at 19:40, Wayne Stambaugh wrote: > > > > On 11/26/19 2:20 PM, Ian McInerney wrote: >> I would like to introduce two

Re: [Kicad-developers] GitLab migration

Was there a resolution on the 2FA question? (I used to have to use it for Adobe’s VPN and hated it, but it is what it is.) I assume git merges will still go through SSH and not require 2FA either way? Cheers, Jeff. ___ Mailing list:

Re: [Kicad-developers] Using OPT types

Personally I hate OPT (because it’s somewhat harder to read and more-than-somewhat harder to debug). I also dislike auto, except in the case of stl::’s overly-verbose iterators. Again, they make the code harder to read more often than not. Maybe I’m just showing my age…. > On 24 Nov 2019, at

Re: [Kicad-developers] KiCad joins the Linux Foundation

Addition. Folks are free to continue to use CERN if they want. > On 22 Nov 2019, at 19:39, Mark Roszko wrote: > > > I need to add a "Donate via Linux Foundation" button to the KiCad > website main page. > > But is it in addition to or to replace CERN? > > > > On Fri, Nov 22, 2019 at

Re: [Kicad-developers] Back annotate references from PCB

learn it. I have a couple > projects in the pipeline where I might find this feature useful; in the past, > I've manually copy/pasted sections of a schematic to repeat subcircuits. > > Thanks, > -Brian > > On 11/22/19 2:37 PM, Jeff Young wrote: >> Hi Brian, >

Re: [Kicad-developers] Back annotate references from PCB

Hi Brian, Imagine you’re doing an audio amplifier. Your main schematic sheet has 4 subsheets: PSU, control logic, left channel and right channel. Both left channel and right channel point to the same sub-page. So there’s a single schematic symbol for each part in the left & right channel,

Re: [Kicad-developers] [PATCH] Eeschema: simulator: use dotted traces for current and phase.

I think phase is always dotted in LTSpice, but current is solid. You can chose the colour of any trace. > On 21 Nov 2019, at 17:33, Ian McInerney wrote: > > This is probably introducing major feature creep, but it would be nice to > develop a dialog that allows setting the per-trace

Re: [Kicad-developers] Building current master fails

This will do it in one step: find . -name *_lexer.h -delete > On 20 Nov 2019, at 15:57, Adam Wolf wrote: > > Thanks for this! I have just been cleaning a lot.. :) > > On Wed, Nov 20, 2019 at 9:16 AM Jeff Young wrote: >> >> I switch between 5.1 and master and back

Re: [Kicad-developers] Building current master fails

I switch between 5.1 and master and back in the same tree. You have to run the clean each time you go from 5.1 to master. > On 20 Nov 2019, at 14:34, Ian McInerney wrote: > > Thats correct, all those lexer files should now be in the build folder. I > think that only the board file has had

Re: [Kicad-developers] [PATCH] Kicad: project manager: Do not reconstruct entire project tree when renaming file to different dir

ey behave that would be good. If they work for > both of you I will push them. > > -Ian > > On Sat, Nov 16, 2019 at 1:00 AM Mikołaj Wielgus <mailto:wielgusmiko...@gmail.com>> wrote: > Jeff, > > your new version appears to be working well on my computer on Windows.

Re: [Kicad-developers] [PATCH] Kicad: project manager: Do not reconstruct entire project tree when renaming file to different dir

>> wrote: > I'll give it a test on GTK once my build here finishes, but I don't think I > have seen any issues with file watcher on GTK in the past. > > -Ian > > On Fri, Nov 15, 2019 at 10:03 PM Jeff Young <mailto:j...@rokeby.ie>> wrote: > Hi Mikolaj, > &

Re: [Kicad-developers] Project save as

FWIW, the old generated files are not outdated — the paths in them are updated. > On 11 Nov 2019, at 23:06, Eeli Kaikkonen wrote: > > > > ti 12. marrask. 2019 klo 0.02 Jon Evans (j...@craftyjon.com > ) kirjoitti: > I question the value of creating this amount of

Re: [Kicad-developers] Tab handling in text rendering and bbox calculation

D’oh. I was thinking our stroke font was mono-spaced, but then why would we have to look up widths in the width-table. I think my brain worked better years ago, but perhaps it’s just nostalgia…. ;) > On 12 Nov 2019, at 12:35, Johannes Sprigode wrote: > > If that is so then I rest my case. >

Re: [Kicad-developers] Tab handling in text rendering and bbox calculation

The artificial fattening of the middle of the character strokes suggests that Johannes has one of the subpixel anti-aliasing methods turned on. While it doesn’t seem like that would have a cumulative effect of more than a single pixel, maybe it's somehow involved. Johannes, does it change any

Re: [Kicad-developers] GitLab migration

I’d definitely keep Fix Committed. For Fix Released someone’s either going to try and find them from a plain-text search (which never worked for shit with Launchpad), or from a commit-message. The commit-message will just have the Launchpad number in it anyway, so they’re going to go to

Re: [Kicad-developers] Project save as

ote: > > > > ma 11. marrask. 2019 klo 22.41 Jeff Young (j...@rokeby.ie > <mailto:j...@rokeby.ie>) kirjoitti: > Yes, the current algorithm renames files that either match the project name > (with any extension), or start with the project name followed by a dash

Re: [Kicad-developers] Project save as

e any generated files. This matches my > experience with other tools. > > On Mon, Nov 11, 2019 at 3:28 PM Seth Hillbrand <mailto:s...@kipro-pcb.com>> wrote: > On 2019-11-11 11:42, Jeff Young wrote: > > > A... I didn't notice that. We are indeed failing to look

Re: [Kicad-developers] Project save as

20:29, Jon Evans wrote: > > In my opinion we should not rename any generated files. This matches my > experience with other tools. > > On Mon, Nov 11, 2019 at 3:28 PM Seth Hillbrand <mailto:s...@kipro-pcb.com>> wrote: > On 2019-11-11 11:42, Jeff Young wrote: &

Re: [Kicad-developers] Project save as

A… I didn’t notice that. We are indeed failing to look for the Protel extensions. > On 11 Nov 2019, at 19:35, Eeli Kaikkonen wrote: > > ma 11. marrask. 2019 klo 20.39 Jeff Young (j...@rokeby.ie > <mailto:j...@rokeby.ie>) kirjoitti: > I want to address t

Re: [Kicad-developers] Project save as

Next for the folder or file question. New project does indeed ask for the name of the project file and also asks if you want a directory auto-created. I hate that, but I’ll admit it’s clearer than the Save As… case where you’re not sure which it’s asking for. We have our own dialog for

Re: [Kicad-developers] Project save as

I want to address the Gerber issue first. In this case Eeli was expecting the old name to get updated if it occurred anywhere in the filename. My expectation was that it would only get updated if the file name started with the old name. Either is easy to implement, but I’d rather not have a

Re: [Kicad-developers] Test failures

Hi Simon, I’ve pushed changed which I hope will fix the spacing problem (but I never got the test environment working on my Mac so I’m not 100% sure). Cheers, Jeff. > On 10 Nov 2019, at 09:28, Simon Richter wrote: > > Hi, > > we seem to have picked up two test failure reports[1]: > >

Re: [Kicad-developers] Project save as

He he… I know our users. I can be sure of a bug report even if I get it right. ;) > This is exactly why I never tackled this one. Anytime your are trying > to deal with complex relative path changes, the code gets rather messy. > I doubt this will affect many users but you can be rest assured

Re: [Kicad-developers] Project save as

Hi Wayne, > On 9 Nov 2019, at 19:05, Wayne Stambaugh wrote: > > Hey Jeff, > > On 11/9/2019 12:06 PM, Jeff Young wrote: >> I’m working through the project Save As feature. >> >> I currently have it renaming the top-level files, updating the symbol and >&g

[Kicad-developers] Project save as

I’m working through the project Save As feature. I currently have it renaming the top-level files, updating the symbol and footprint lib tables, updating paths in Gerber job files, and updating paths and filenames in the netlist. A couple of questions: 1) The netlist I’m handling is a .net

Re: [Kicad-developers] New lead developer announcement

Woot! Congrats, Ian! Cheers, Jeff. > On 7 Nov 2019, at 20:14, Wayne Stambaugh wrote: > > I am happy to announce that the KiCad project now has a new member of > the lead development team. Ian McInerney has accepted an invitation to > become a member of the lead development team. Ian's

<    1   2   3   4   5   6   7   8   9   10   >