Re: [Kicad-developers] [PATCH] Refactor COMMON_ACTIONS into a base and derived class

rdcoding) for this stuff? Anything I can do to encourage? > > > Best, > > hauptmech > > > > > > > On 17/02/17 16:56, Jon Evans wrote: > > Hi all, > > More preparation for GerbView GAL port: this patch pulls a virtual ACTIONS > class out of

Re: [Kicad-developers] Hard-coded hotkeys in pcbnew/tools/selection_tool.cpp

t;> >> I agree this has to be fixed, yet I doubt it is located on someone's >> list. If noone steps in, then most likely I will do it at one point in >> the future. >> >> Regards, >> Orson >> >> On 06/27/2017 01:29 PM, hauptmech wrote: >>

Re: [Kicad-developers] Color scheme import/export

It was on my list and unfortunately I haven't had time to work on it in a while. I expect to have time for coding again starting in a week or so, but if you'd like to take this on, go for it. I was thinking about first focusing on getting GerbView GAL to a point where it can be merged. Thanks, J

Re: [Kicad-developers] Color scheme import/export

I think a palette is a good idea, I was thinking the same thing. Jon On Aug 19, 2017 12:28, "Chris Pavlina" wrote: > There are one or two more usability features I'd like to have for color > schemes - in particular, I'd like the ability to move around color > settings between layers easily. I t

Re: [Kicad-developers] wire connections

I'm assuming you're referring to schematic wires? I'm not sure if there is active work going on in this area, but I briefly looked into adding this functionality and decided it would be better to wait until eeschema is using GAL canvas and the new tools system instead of spending time adding lots o

Re: [Kicad-developers] New feature: support for Gerber job file.

Hi JP, This is a nice feature and it seems to work well! I did have to make one change in gerber_jobfile_writer.cpp:154 to get it to compile on MacOS / LLVM: adding c_str() fputs( header[ii].c_str(), jobFile ); Best, Jon On Wed, Aug 30, 2017 at 11:26 AM, jp charras wrote: > Le 30/08/2017 à 13

[Kicad-developers] GAL grid style setting inconsistency

Hi all, I was looking into why my Gerbview GAL branch was defaulting to line grid when I thought it should be dots grid, and I found an inconsistency in the GAL display options code. In gal_display_options.cpp, the grid options map (gridStyleConfigValues) go in this order: DOTS, LINES, SMALL_CROS

[Kicad-developers] [PATCH] Move ZOOM_TOOL to common; add RMB-drag to zoom out

21d6d116c4157f0cec132e2c9f64b9c4c1895de7 Mon Sep 17 00:00:00 2001 From: Jon Evans Date: Wed, 30 Aug 2017 22:35:30 -0400 Subject: [PATCH] Move ZOOM_TOOL to common; add RMB-drag to zoom out --- common/CMakeLists.txt | 1 + common/tool/actions.cpp | 4 {pcbnew

Re: [Kicad-developers] application for svg to png

Could we merge the PNG files into a tilemap like is commonly done for mobile/web applications? On Thu, Aug 31, 2017 at 3:04 PM, jp charras wrote: > Le 31/08/2017 à 20:27, Wayne Stambaugh a écrit : > > Is it possible to create image libraries with different size images > > using the method you de

Re: [Kicad-developers] [Patch] Add ability to reset Pcbnew layer colors to default

Yes, there is V6 work planned for this, I was planning on doing it, but there are several steps in between (first changing how settings in general are stored, and then a general refresh of the layers/color settings GUI) On Wed, Aug 21, 2019 at 5:06 PM Ian McInerney wrote: > I noticed today that

Re: [Kicad-developers] [Patch] Add ability to reset Pcbnew layer colors to default

committed your Doxygen error log file. I don't think > we would want to merge that into the KiCad source. If Jon is OK with > merging this, you please resubmit the patch without your Doxygen error > log file. > > Cheers, > > Wayne > > On 8/21/19 5:21 PM, Jon Evans wrote:

Re: [Kicad-developers] [Patch] Make pl_editor runnable from build directory

It does work in Linux in my experience. Haven't made it work on Win or Mac. On Thu, Oct 3, 2019 at 1:56 PM Nick Østergaard wrote: > It is quite some time since I tried to run anything of kicad in the > build dir. Does it even work for other pats of kicad? > > I switched my workflow to make inst

Re: [Kicad-developers] GitLab migration

Also some interesting discussion on Hacker News[1] Keep in mind that GitLab as a company is quite unique in that they are 100% remote and employ people distributed globally in many different cultures. Whether or how GitLab employees discuss politics at work (necessarily, via electronic communicatio

Re: [Kicad-developers] Minimum Boost version

On Mon, Oct 21, 2019 at 5:53 PM Diego Herranz wrote: > > It looks like by the time 6.0 is out, Ubuntu 16.04 may still be officially > supported. Just something to have in mind. > I love your optimism :) ___ Mailing list: https://launchpad.net/~kicad-de

Re: [Kicad-developers] Benchmarking kicad compilation on CPUs released 6 years apart

Thanks for this data! I also have a Haswell system right now and have been eyeing the new Ryzens... I too feel the pain of long kicad compilation time. -Jon On Tue, Oct 29, 2019, 01:51 Henner Zeller wrote: > > > On Mon, 28 Oct 2019 at 22:21, Andrew Lutsenko > wrote: > >> Hi all, >> >> This inf

Re: [Kicad-developers] Benchmarking kicad compilation on CPUs released 6 years apart

Ha, I also keep around my Thinkpad T61 for occasional testing for this purpose, although usually I avoid building on it as that takes a lonng time. On Tue, Oct 29, 2019 at 10:57 AM Drew Van Zandt wrote: > Let me encourage some of y'all to stick with an older machine, or keep it > around for

Re: [Kicad-developers] Benchmarking kicad compilation on CPUsreleased 6 years apart

I don't own either, but am planning a Ryzen build. The Threadrippers built on the third-gen Zen are not out yet, but presumably they will be even better as workstation/server CPUs than third-gen Ryzen. On the other hand, if buying parts today, the 3900X / 3700X seem like way better bang for the b

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

Eeschema now keeps its internal net state up to date continuously, but I didn't work on any continuous syncing to PcbNew. The way it works in Eeschema, the graphical schematic is still the driving source of truth; the netlist does not drive the schematic. -Jon On Wed, Nov 6, 2019 at 9:08 AM Ian

Re: [Kicad-developers] macos dev environment

I also use CLion. It's okay but not perfect. It's been a while since I've been compiling on my Mac but from what I recall, the most frustrating part is the need to re-generate all of the application packages whenever anything is touched (which is a slow and non-parallel process). It's possible t

Re: [Kicad-developers] New lead developer announcement

Congrats and welcome, Ian! On Thu, Nov 7, 2019 at 3:17 PM Jeff Young wrote: > 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 Mc

Re: [Kicad-developers] Project save as

FWIW, we are considering moving to the "create a folder for the project" to be a requirement rather than an option, in case that impacts this feature. Or rather, it would be a requirement that there be one KiCad project per folder, not necessarily that automatically creating a folder would be a req

Re: [Kicad-developers] Project save as

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 wrote: > On 2019-11-11 11:42, Jeff Young wrote: > > > A... I didn't notice that. We are indeed failing to look for the > > Protel extensions.

Re: [Kicad-developers] Project save as

I guess ultimately this is up to Jeff since he's implementing it, but I think this is going way above and beyond what any user should expect of an application. I have never used any software that tried this hard to handle the "save as" feature without any chance of the user needing to take some fo

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

I can add the simulator to the scope of effort to do the whole settings files upgrade for 6.0 On Thu, Nov 21, 2019 at 5:06 PM Wayne Stambaugh wrote: > > On 11/21/19 1:15 PM, Kymatica wrote: > > Sure, I can make it configurable. Where should this setting be > available? In the main preferences? (

[Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build

2001 From: Jon Evans Date: Sun, 24 Nov 2019 12:30:29 -0500 Subject: [PATCH 1/3] Use wxArrayString instead of vector in BUS_ALIAS Fixes linker errors on Windows/VC See: https://trac.wxwidgets.org/ticket/10884 --- eeschema/bus_alias.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

Re: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build

> extension support. Did someone recently add ngspice and wxPhoneix to > vcpkg? The Python code is also somewhat different as I assume that you > would use the default python install to build the Python extensions. > > Cheers, > > Wayne > > On 11/24/19 12:40 PM, Jon Evans w

Re: [Kicad-developers] GitLab migration

While there are many forms of 2FA in the world, GitLab does not support all of them. Currently, TOTP and U2F are the only supported methods [1] This means that if we enabled it, everyone with commit access would need either a device running a TOTP-compliant program, or a U2F device such as a YubiK

Re: [Kicad-developers] GitLab migration

As far as I know, there is not fine-grained access control on Wiki pages. The only way to do something like this to create a separate project just for a public wiki. Then a limited set of people would have permissions to copy things from the public wiki to the main KiCad project wiki. To be hones

Re: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build

py to experiment with whatever you’ve got, > especially if you can provide some guidance. > > > > Brian > > > > *From: *Jon Evans > *Sent: *November 24, 2019 12:41 PM > *To: *KiCad Developers > *Subject: *[Kicad-developers] [PATCH] Fixes for Visual S

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

That error was fixed by Seth this morning, you may need to rebase on latest On Sat, Nov 30, 2019 at 2:02 PM Eeli Kaikkonen wrote: > > > la 30. marrask. 2019 klo 9.54 Alexander Shuklin (jasura...@gmail.com) > kirjoitti: > >> >> Many thanks, I hope my patch is not very bad. >> You can find that pa

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

>From another professional user, I have to disagree. There are at least two cases I can think of where changing the footprint during layout is important: 1) In my experience, it's common to keep multiple variants of IPC standard SMD footprints, especially for passives. By default, we specify the "

Re: [Kicad-developers] [PATCH] Fixes for Visual Studio / vcpkg build

What environment does that build use? My patches were necessary for VS2019 using default compiler settings On Sun, Dec 1, 2019, 17:32 Nick Østergaard wrote: > Oh, ok. Then I wonder why Jon needed to patch it. > > On Sun, 1 Dec 2019 at 20:14, Simon Richter > wrote: > > > > Hi Nick, > > > > On 01

[Kicad-developers] Altium 20 new interactive routing features

https://www.altium.com/altium-designer/whats-new Check out the first two videos "Any Angle Routing" and "Sliding" - some interesting concepts. I haven't played with them in real life yet. -Jon ___ Mailing list: https://launchpad.net/~kicad-developers Po

Re: [Kicad-developers] Altium 20 new interactive routing features

I installed AD20 to play around a bit. The new any-angle mode so far works as advertised, it is quite smooth and responsive. The video may be pre-planned but I don't think it's heavily edited. The router seems to update the proposed path at every grid step, so if you set a small grid the updates

Re: [Kicad-developers] suggestion: git branching model

We already have used temporary branches for major features in the past. I'm sure we'll continue to do this (through gitlab merge requests) where it makes sense - it's a lot of work to keep a feature branch in mergeable state. -Jon On Wed, Dec 11, 2019, 10:16 Jonatan Liljedahl wrote: > Good poin

Re: [Kicad-developers] Connection graph question

Hi Wayne, I can't look at the code this minute, but I think you basically have it right. This call is quite expensive so if we can not trust the pin map to be valid, we'll probably want to come up with some way to make a targeted update so that we don't incur the computation time of a full recalcu

Re: [Kicad-developers] SCH_BUS_BUS_ENTRY

IIRC we agreed it could be deleted, but someone would need to make a migration code to replace it in schematics to actually do so. It currently has no special behavior at all-its just a 45-degree piece of bus wire. -Jon On Sat, Dec 14, 2019, 16:00 Seth Hillbrand wrote: > Hi Devs- > > I recall

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

Hi all, The Gerber job file specification[1] says that the format follows the JSON standard, and doesn't say much else about numeric value storage. But, in the examples in that spec, decimal (floating-point) values are all truncated with only a few digits after the decimal point. The manual JSON

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

omething 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 doesn't say much else

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

me. Maybe > someone has some huge hack that uses fixed-length regular expressions to > parse them or something. > > In the absence of a spec, the examples are what people use. > > I’m not convinced this is the best plan either — but I am convinced it’s > the safest. > > Cheers

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

t's considered a JSON "number". > Otherwise we should be storing the float as string and applying the > custom formatting in the conversion to string. > > On Sat, Dec 28, 2019 at 8:01 AM jp charras wrote: > > > > Le 24/12/2019 à 21:43, Jon Evans a écrit : &g

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

1.600 is readable. > 1.600088817841970012523233890533447265625 is just ridiculous > (for any value in a config file). > > > > > On Sat, Dec 28, 2019 at 8:01 AM jp charras > wrote: > >> > >> Le 24/12/2019 à 21:43, Jon Evans a écrit : > >

Re: [Kicad-developers] Better handling of bugs which affect two versions

This is a good point, Eeli. Lead devs, what do you think about adding a bright-colored label "needs cherry pick" that can be removed when the commits are picked to the required branch? That way, we can run searches for this label and inspect issues that have it (even if the issue is closed) I gue

[Kicad-developers] Printing size_t on MSW (%zu)

Hi all, Context: https://gitlab.com/kicad/code/kicad/merge_requests/28#note_264910682 I have heard there are issues using "%zu" format specifier on Windows/mingw, because mingw links against a very old Windows library that does not support the C99 standard. I have also heard that this isn't an i

Re: [Kicad-developers] Printing size_t on MSW (%zu)

I found it defined in C:\msys64\mingw64\include\c++\8.3.0\x86_64-w64-mingw32\bits\os_defines.h on my machine. @JP -- what platform did you use (Windows version / MSYS version / etc) where you saw the issue? On Fri, Jan 3, 2020 at 9:02 AM Seth Hillbrand wrote: > On 2020-01-02 17:19, Jon Ev

Re: [Kicad-developers] Printing size_t on MSW (%zu)

So maybe it's a 32-bits vs 64-bits thing. If you add a line like #define __USE_MINGW_ANSI_STDIO 1 at the top of that source file, does it work? On Fri, Jan 3, 2020 at 9:32 AM jp charras wrote: > Le 03/01/2020 à 15:10, Jon Evans a écrit : > > I found it defined in > > C:\msys

Re: [Kicad-developers] Printing size_t on MSW (%zu)

Widgets/blob/cc931612eec2e3ea49200ebff45042135f3c3f9c/include/wx/wxcrtvararg.h#L84 > > > > > > On Fri, Jan 3, 2020 at 10:05 AM jp charras > wrote: > >> > >> Le 03/01/2020 à 15:58, Jon Evans a écrit : > >>> So maybe it's a 32-bits vs 64-bits t

Re: [Kicad-developers] Advice on merge request

Hi Brian, For the first question, you could cherry-pick all the commits from Alexander's merge request onto your own feature branch (rebasing your own commits on top of his). Once his MR is merged, you can just rebase your branch on top of latest master, dropping the cherry-picked commits and just

Re: [Kicad-developers] How do I refresh PCB or Schematic window

Are you doing something like getView()->Update( item ); for the items that you are touching? That plus GetCanvas()->Refresh() should be enough. Is your code somewhere we can look at? On Wed, Jan 8, 2020 at 11:02 PM Brian Piccioni wrote: > Hello & thanks for the help. > > I open a dialog in PCBNe

Re: [Kicad-developers] Coverity heads-up

It's worth mentioning that I'm getting rid of PARAM_CFG_ARRAY in my new settings branch (should be done before FOSDEM) On Sun, Jan 12, 2020 at 10:31 AM Jeff Young wrote: > Hi Wayne, > > The main one that permeates the code is CONFIG_PARAM_ARRAY. It doesn't > use any of the boost::ptr_array fanc

Re: [Kicad-developers] Rebase the tree?

Personally, I think "history is inviolate" doesn't need to apply to things that were checked in accidentally, and thus will never need to be merged against, diffed, etc. On Fri, Jan 17, 2020 at 10:48 AM Simon Richter wrote: > Hi Seth, > > On Fri, Jan 17, 2020 at 06:53:46AM -0800, Seth Hillbrand

Re: [Kicad-developers] How to show pad in pcbnew by clicking pin in eeschema

This does appear to have broken at some point. Filed an issue for it: https://gitlab.com/kicad/code/kicad/issues/3791 -Jon On Mon, Jan 20, 2020 at 11:10 AM Dick Hollenbeck wrote: > Quick help, > > When I click on a pin in eeschema I get the disambiguating menu and then I > say "pin" choice. >

Re: [Kicad-developers] GitHub Mirror not updating?

I can say from experience that enabling LFS would be a lot more hassle than rebasing. On Mon, Jan 20, 2020 at 12:09 PM Wayne Stambaugh wrote: > Is that what is causing the mirror issue? If so, we should probably > rebase to get rid of the blobs. I was really hoping we wouldn't have to > do tha

Re: [Kicad-developers] Using Master branch / Nightly builds for work on new projects - Is it safe?

I think the following scenarios are entirely possible if you use the Master branch from ~now until it reaches feature completeness for V6 release: 1) Files may be corrupted permanently (so you would need to restore them from a backup or earlier version if you use a version control system) 2) File

Re: [Kicad-developers] What happened to buses in eeschema?

Hi Brian, Since your build version doesn't include a git commit, I have no idea how recent a build you are running, but I think you are hitting one of the eeschema internal units change bugs that was present for a day or two but then resolved. Bus entries were briefly very very small. The rules

Re: [Kicad-developers] Proper way to report bugs on branches

Can you reproduce these same issues on the master branch? Either the latest master, or the point on master at which your custom branch splits (i.e. the most recent rebase point) Doing so will absolutely rule out that there is anything about your branch related, and also make it easier to figure out

Re: [Kicad-developers] Proper way to report bugs on branches

list > { SCL SCK ~CS RD} all items after and including CS have an over bar. > > Brian > On 2020-01-27 7:14 p.m., Jon Evans wrote: > > Can you reproduce these same issues on the master branch? Either the > latest master, or the point on master at which your custom branch splits &

Re: [Kicad-developers] Broken Linux build

LIB_ID::Test is hidden behind a DEBUG ifdef check. So, it seems like in your configuration the CMake change is not setting DEBUG anymore. Are you able to inspect your CMakeCache.txt to shed some light on this? On Fri, Feb 7, 2020 at 11:46 AM Wayne Stambaugh wrote: > I'm running into this build

Re: [Kicad-developers] Broken Linux build

r the compile commands somewhere? Does anyone else see this issue? On Fri, Feb 7, 2020 at 12:26 PM Wayne Stambaugh wrote: > Neither `make rebuild_cache` or a clean build fixed the issue. Attached > is the CMakeCache.txt file. > > On 2/7/20 11:50 AM, Jon Evans wrote: > > LIB_ID::

Re: [Kicad-developers] Broken Linux build

your system. (see: https://gitlab.com/kicad/code/kicad/commit/b824051adf246c6d5d30a1a5806dd7a194f23700#9a2aa4db38d3115ed60da621e012c0efc0172aae_339_343 ) -Jon On Fri, Feb 7, 2020 at 12:29 PM Jon Evans wrote: > At the moment I only have access to my Mac, and can confirm that -DDEBUG > do

Re: [Kicad-developers] Broken Linux build

L -DWX_COMPATIBILITY -D_FILE_OFFSET_BITS=64 -D__WXMAC__ -D__WXOSX_COCOA__ -D__WXOSX__ On Fri, Feb 7, 2020 at 12:45 PM Jeff Young wrote: > 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 bac

Re: [Kicad-developers] Broken Linux build

Feb 7, 2020 at 1:20 PM Wayne Stambaugh wrote: > No luck. Adding those lines didn't resolve the issue for me. > > On 2/7/20 12:40 PM, Jon Evans wrote: > > Wayne, can you revert the changes on lines 343-347 and add back -DDEBUG > > to those four locations, keeping the ad

Re: [Kicad-developers] Broken Linux build

Good find! I think we should remove that line (pcbnew/CMakeLists.txt:403) since it's not used. I guess we have just been clobbering KICAD_CONFIG_DIR for swig and it just didn't matter. On Fri, Feb 7, 2020 at 1:29 PM Simon Richter wrote: > Hi, > > On 07.02.20 19:19, Simon Richter wrote: > > > Th

Re: [Kicad-developers] Broken Linux build

-I${WXPYTHON_SWIG_DIR} > > but that didn't help either. > > On 2/7/20 1:42 PM, Simon Richter wrote: > > Hi, > > > > On 07.02.20 19:31, Jon Evans wrote: > > > >> Good find! I think we should remove that line > >> (pcbnew/CMakeLists.

[Kicad-developers] GCC 7.4 crash somehow related to backannotate

Hi all, I am running into a weird problem on GCC 7.4 / Ubuntu 18.04.1 Master compiles just fine. However, after rebasing onto latest master, my branch in MR90 causes an internal compiler segfault on eeschema/tools/backannotate.cpp:185 I

Re: [Kicad-developers] GCC 7.4 crash somehow related to backannotate

ualifier will change much there. > > If somebody knows better about that, please let me know, because I don't > know :( > > > > On Sat, 8 Feb 2020 at 19:33, Jon Evans wrote: > > > > > > Hi all, > > > > > > I am running into a weird probl

Re: [Kicad-developers] Fedora build failures

JP already fixed in fb19d83b On Mon, Feb 17, 2020 at 10:12 AM Steven A. Falco wrote: > The Fedora Copr builds are failing with the following error. Is anyone > else seeing this? > > Steve > > cd /builddir/build/BUILD/kicad-r17610-2ca16c0b/qa/eeschema && > /usr/bin/c++ -DBOOST_TEST_DYN_

[Kicad-developers] New settings framework merged

Hi everyone who uses nightly builds of KiCad! For those who don’t follow GitLab that closely, the new settings system got merged today. This brings a few user-facing changes that you should be aware of: First, user settings are now stored in versioned subfolders of the KiCad config path. The ma

Re: [Kicad-developers] New settings framework merged

; I think we need to restore previous behavior. In terms of json > representation probably ordered array of {path : visibility} tuples will > work best. > > Regards, > Andrew > > On Wed, Feb 19, 2020 at 8:57 PM Jon Evans wrote: > >> Hi everyone who uses nightly builds of KiCad! >

Re: [Kicad-developers] unable to compile masrer HEAD

Oops, that's my fault, I inadvertently introduced a dependency on BUILD_GITHUB_PLUGIN=ON Dev team -- is there any reason we can't include kicad_curl always? I used it for URL escaping as it's the only library we currently use that has a good facility for that. -Jon On Sun, Feb 23, 2020 at 10:05

Re: [Kicad-developers] unable to compile masrer HEAD

https://gitlab.com/kicad/code/kicad/-/merge_requests/113 @Sergey -- are you able to build with BUILD_GITHUB_PLUGIN=ON for now? On Sun, Feb 23, 2020 at 11:27 AM Wayne Stambaugh wrote: > On 2/23/20 11:08 AM, Seth Hillbrand wrote: > > On 2020-02-23 07:11, Jon Evans wrote: > > >

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

Without looking at the code, those two *may* be linked (creating a new undo step should cause the save button to be enabled) On Sun, Feb 23, 2020 at 11:35 AM Eeli Kaikkonen wrote: > > > On Sat, Feb 22, 2020 at 4:48 PM Brian Piccioni < > br...@documenteddesigns.com> wrote: > >> Hello >> >> Now th

[Kicad-developers] MacOS nightlies gone

MacOS nightly builds are no longer showing up on the CERN S3 bucket. Anyone know what's up? -Jon ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-devel

Re: [Kicad-developers] DRC reports

The idea I was kicking around was to build a 2-level tree, with the parents being these categories (in new drc branch): https://gitlab.com/kicad/code/kicad/-/blob/drc/pcbnew/drc/drc_violation.h#L31 I think there are much fewer than 64 error types that actually need to be displayed to the user in gr

Re: [Kicad-developers] DRC reports

s right. > > I do like the right-click clear and ignore actions. And I think those are > fine to do at the 64-types granularity. But I don’t really want to do that > just to not show courtyard violations. > > On 25 Feb 2020, at 20:53, Jon Evans wrote: > > Some mockup to g

Re: [Kicad-developers] DRC reports

On Tue, Feb 25, 2020 at 6:04 PM Eeli Kaikkonen wrote: > The problem with all tree structure UI's is that they are difficult to > navigate. The locations of the top level items change based on what is > opened. There's constant need or at least temptation to open and close > items. Tabs are always

Re: [Kicad-developers] DRC reports

thing I haven't seen mentioned are the handling of groups of elements, > such as multiple traces which need their lengths matched or a net class > that contains multiple nets. How that is shown in the UI might require > another level since each of those groups must break out the ele

Re: [Kicad-developers] DRC reports

hinking Board Settings. Some of them might be project-specific, no? > > On 28 Feb 2020, at 02:34, Jon Evans wrote: > > I agree settings should be in a different dialog. I kind of think they > should go in the main preferences window as another entry (there will be > multiple "

Re: [Kicad-developers] DRC reports

Yes, that's what I am proposing. On Fri, Feb 28, 2020 at 11:30 AM Jeff Young wrote: > At present Preferences holds only app-wide settings. So if we went in > this direction we’d want to do it en-masse. > > On 28 Feb 2020, at 14:48, Jon Evans wrote: > > I did mean Pref

Re: [Kicad-developers] Annotation Epic/Geographic reannotation

Hi Brian, I haven't looked at your MR yet since it seemed like a lot of other people were already engaged and I think "too many cooks in the kitchen" can be a detriment to code review. I just opened it up today and noticed that it needs to be rebased on master (can't be done automatically, which p

Re: [Kicad-developers] Annotation Epic/Geographic reannotation

rt of the > process so I always assume radio silence means I screwed something up. > > I think !108 is pretty up to date with master. I will have to push a new > version with consistent handling of references with eeSchema. > > Brian > > > On 2020-03-01 7:31 p.m., Jon Evan

Re: [Kicad-developers] DRC marker persistence

Hi Jeff, There are several ways to do persistence. It sounds like you are planning to implement it as "save the state of all DRC markers", which is one way. Another way would be to just save the exceptions (aka waived violations), so closing and opening a board would not return the markers to vie

Re: [Kicad-developers] DRC marker persistence

My original UX proposal was to have them in an "ignored" group at the bottom of the list, collapsed by default but still visible so that things can be "unignored" without too much trouble. On Tue, Mar 3, 2020 at 10:20 AM Nhat Khai wrote: > Instead of persisted: > 1) Can it has a expiration day,

Re: [Kicad-developers] DRC marker persistence

h, people won't be impacted unless they use the ignore feature. -Jon On Tue, Mar 3, 2020 at 3:56 PM Wayne Stambaugh wrote: > On 3/3/20 8:59 AM, Jon Evans wrote: > > Hi Jeff, > > > > There are several ways to do persistence. It sounds like you are > > plannin

Re: [Kicad-developers] DRC marker persistence

This will be the end state (more or less) when V6 is ready. On Wed, Mar 4, 2020, 04:12 yann jautard wrote: > > Le 03/03/2020 à 21:55, Wayne Stambaugh a écrit : > > > > I'm just wondering about the impact to CVS users of adding them to the > > project file. I'm not sure if it's an issue or not.

[Kicad-developers] Project file churn

I've started work on the new project system for V6. One question that I wanted to cast a wide net on: Are there any real-world uses for the "update" and "last_client" lines that are stored in the current project format? KiCad internally doesn't make any use of these, and they just cause file chu

Re: [Kicad-developers] Project file churn

We don't currently use the update timestamp for anything that I can see. But even if we did, couldn't we just use the file modification time from the OS? On Sat, Mar 7, 2020 at 2:02 PM Wayne Stambaugh wrote: > Hi Jon, > > On 3/7/20 1:25 PM, Jon Evans wrote: > > I&#

Re: [Kicad-developers] Project file churn

the > other. > > On 3/7/20 2:05 PM, Jon Evans wrote: > > We don't currently use the update timestamp for anything that I can > > see. But even if we did, couldn't we just use the file modification > > time from the OS? > > > > On Sat, Mar 7, 2020 at 2:0

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

Project (it will be moved into a separate ERC settings file) On Thu, Mar 12, 2020 at 9:59 AM Jeff Young wrote: > 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. > > > ___

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

h, I note that we’re still using the PARAM_CFG stuff to > read/write the stuff in the new preferences structs. I assume that’s a > temporary measure and we’ll just be writing the structs to JSON at some > point? > > Thanks, > Jeff. > > > On 12 Mar 2020, at 14:10, Jon Evans

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

tings just write to the JSON object directly. If you think that would be better for some situations, feel free to play around with that approach. On Thu, Mar 12, 2020 at 10:15 AM Jon Evans wrote: > Yes, that's right. As part of splitting the project settings into > different files, those

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

etc. Is > the JSON stuff all in so I could play around with that now, or do I need to > wait a bit? > > On 12 Mar 2020, at 14:17, Jon Evans wrote: > > Or, maybe I didn't understand you right -- there are similar PARAM helpers > for JSON as well, so that code doesn't n

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

e should also be a user configurable default setting template that > can be loaded when creating new projects. > > On 3/12/20 10:10 AM, Jon Evans wrote: > > Project (it will be moved into a separate ERC settings file) > > > > On Thu, Mar 12, 2020 at 9:59 AM Jeff Youn

Re: [Kicad-developers] Project-Local Settings (was: Saving the pin-to-pin map)

ir own settings - such as > DRC/ERC rules, etc). > > -Ian > > On Thu, Mar 12, 2020 at 2:54 PM Jon Evans wrote: > >> That's a good point -- all project-local settings should essentially have >> a second copy in the global settings which are the defaults. >> &g

Re: [Kicad-developers] Starting kicad_pcb triggers assertion under FreeBSD

Hi, It's easier to track these things if you report on the GitLab issue tracker: https://gitlab.com/kicad/code/kicad/-/issues Could you attach the contents of your ~/.config/kicad directory in a ZIP archive? (or wherever you store your KiCad config, if you are using a custom location) Thanks, Jon

Re: [Kicad-developers] MR Test Failure Help

I just rebased 170 on top of latest master, let's see if that fixes it. On Tue, Apr 21, 2020 at 6:07 PM Emery B wrote: > Hello Team, > > My merge requests (170&171) have failed in the test step. Test passes if > merged to the latest development branch. Should I push a merge-commit to my > MR? Pl

Re: [Kicad-developers] Coverity for the 5.1 branch

Thanks! Speaking of Coverity, should we change the config to skip the auto-generated swig files? They seem to generate lots of noise. -Jon On Thu, Apr 23, 2020 at 8:01 AM Wayne Stambaugh wrote: > Nice work! Thank you Mark and Nick. > > On 4/23/20 4:03 AM, Nick Østergaard wrote: > > Hello > >

Re: [Kicad-developers] Help debug pcbnew

This actually recently started happening to me if I had KICAD_SCRIPTING turned on, the only way I could find to fix it was by disabling scripting. I was going to dig in to what was going on, but then I upgraded to Ubuntu 20.04 today and the problem went away, so it was probably some kind of depende

Re: [Kicad-developers] Is it really the case that installing KiCad on a Mac requires manually copying files around?

I believe these users are talking about the normal MacOS method of installing software, which does typically involve copying files. Normally MacOS software is packaged as a disk image that is mounted when you double click it. The mounted image then normally contains the software to be installed,

Re: [Kicad-developers] Consider changing .pro extension in the future

It's on my TODO list, it will happen as part of a new project format https://gitlab.com/kicad/code/kicad/-/issues/2169 -Jon On Thu, May 7, 2020 at 12:18 PM Wayne Stambaugh wrote: > I'm pretty sure this has been discussed to death but but until a new > project file format is created, the file ex

<    1   2   3   4   5   6   7   8   9   >