Re: [Kicad-developers] CVE-2022-23803, CVE-2022-23804, CVE-2022-23946, CVE-2022-23947

Le 16/02/2022 à 19:38, Steven A. Falco a écrit : I found "Fix overflow vulnerability in Gerbview" and possibly "Fix relative return with nullptr condition".  Are there other patches in the series, or are those two the only ones that are needed? I tried grepping the log for CVE, but didn't

Re: [Kicad-developers] strange, probably trivial, message formatting error

Le 29/11/2021 à 15:48, Ian McInerney a écrit : I ask because it is working in the non-translated English dialog I have: image.png -Ian On Mon, Nov 29, 2021 at 2:31 PM Marco Ciampa wrote: On Mon, Nov 29, 2021 at 12:58:15PM +, Ian McInerney wrote: > Did you include the newlines

Re: [Kicad-developers] Tools for editing/creating UI elements in KiCad?

Le 02/09/2021 à 16:35, Brian a écrit : Hi Folks, Reviving some conversation that's happened over the years...what are the favored tools for editing and/or creating the wxWidgets UI elements for KiCad?  Hopefully not "vi"... On the one hand, I suppose I could always just go my own way with

Re: [Kicad-developers] Can't compile latest kicad

Le 16/07/2021 à 13:15, Mark Roszko a écrit : has_value was added in boost 1.68. There is an argument we should be supporting boost 1.65 due to Ubuntu 18 Commit 25e9d177 should fix this issue.  Please test. -- Jean-Pierre CHARRAS ___ Mailing

Re: [Kicad-developers] Any pointers to speed up the build

Le 11/07/2021 à 14:59, Andrew Lutsenko a écrit : Few things that can help 1. Disable qa tests build if you don't need them 2. Disable python scripting if you don't need it 3. Use MSVC if you are on windows. Their linker is a LOT faster than gcc. 4. Use more powerful hardware. Those steps take

Re: [Kicad-developers] Problem opening a PCB file

Le 06/07/2021 à 17:55, Steven A. Falco a écrit : On 7/6/21 11:30 AM, jp charras wrote: Le 06/07/2021 à 17:17, Steven A. Falco a écrit : I've found a project on github [1] that I am interested in, but I have not been able to open the PCB file correctly.  It seems that 5.1 is too old

Re: [Kicad-developers] Problem opening a PCB file

Le 06/07/2021 à 17:17, Steven A. Falco a écrit : I've found a project on github [1] that I am interested in, but I have not been able to open the PCB file correctly.  It seems that 5.1 is too old to handle this file, but 5.99 has several issues, as described in [2]. It looks like the ground

Re: [Kicad-developers] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

Le 28/06/2021 à 16:14, Brian Piccioni a écrit : JP Thanks for the quick reply bjpic@LAPTOP-70Q5CT1Q MSYS ~/kicad-source/build/release~ $ find /mingw64/ -name *glew* /mingw64/bin/glew32.dll /mingw64/bin/glewinfo.exe /mingw64/bin/libvtkglew-8.2.dll /mingw64/include/GL/glew.h

Re: [Kicad-developers] MSYS2 Could NOT find GLEW (missing: GLEW_LIBRARY)

Le 28/06/2021 à 15:51, Brian Piccioni a écrit : Hello I have observed that Geographical Reannotation (my contribution) no longer seems to update the schematic. Manual "Update Schematic from PCB" seems to work so I assume there has been a modification to the Kiway commands. In order to track

Re: [Kicad-developers] *** SPAM *** Re: ngspice-34

Le 03/02/2021 à 11:38, Carsten Schoenert a écrit : Hello Holger, Am 03.02.21 um 11:20 schrieb Holger Vogt: I remember some time ago I tried to address the libtool versioning, but I did not understand it, so abandoned it again. libtool isn't really easy, yes, but the more complicated thing is

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

Le 02/01/2021 à 18:11, Carsten Schoenert a écrit : Am 02.01.21 um 18:07 schrieb jp charras: What is the problem with these files? They are build in tree in case you do a configure out of tree? They are already the final header files built from the corresponding .md files. In my eyes it's

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

Le 02/01/2021 à 17:45, Carsten Schoenert a écrit : Hi, Am 02.01.21 um 17:17 schrieb jp charras: Le 02/01/2021 à 17:09, Nick Østergaard a écrit : FYI, there are still generated files in the source which are also checked in to the source tree: After a make clean: deleted:    ../eeschema

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

Le 02/01/2021 à 17:09, Nick Østergaard a écrit : FYI, there are still generated files in the source which are also checked in to the source tree: After a make clean: deleted:    ../eeschema/dialogs/dialog_bom_help_md.h deleted:    ../pcb_calculator/attenuators/bridget_tee_formula.h deleted:  

Re: [Kicad-developers] MSVC compile: missing s3d_plugin_oce.dll

Le 02/12/2020 à 08:15, deve...@worldinone.at a écrit : I copied over ALL of the dlls, just in case, and it did not help. If it is about dependencies, maybe I missed to install something in vcpkg. I installed the recommended libraries as per the web documentation: boost cairo curl glew

Re: [Kicad-developers] V6 Usability suggestion

Le 21/10/2020 à 18:44, Brian Piccioni a écrit : Hello The power new DRC is great. I believe it would be more usable if the Board Setup -> Design Rules -> Violation Severity table would be in alphabetical order. Until the table has been configured there are a profligacy of DRC errors, many

[Kicad-developers] Fwd: mingw64 build issue.

Message transféré Sujet : mingw64 build issue. Date : Sat, 26 Sep 2020 07:35:20 - De :Frank Zeeman Répondre à :Frank Zeeman Pour : jean-pierre charras I had to downgrade using pacman -U

Re: [Kicad-developers] mingw64 build issue.

Le 25/09/2020 à 19:11, Wayne Stambaugh a écrit : Is anyone else seeing the following error when building with MinGW64/msys2? ../common/libcommon.a(libcontext.cpp.obj):libcontext.cpp:(.text+0x19e): relocation truncated to fit: R_X86_64_PC32 against `*ABS*' I did some digging around and it

Re: [Kicad-developers] Help needed

Le 25/09/2020 à 16:32, Jon Evans a écrit : Can you run with ASAN on (KICAD_SANITIZE in CMake) and see if you get some info about why you get a segfault? On Fri, Sep 25, 2020 at 10:28 AM Franck Jullien mailto:franck.jull...@gmail.com>> wrote: Hi, I'm working on the intersheets

Re: [Kicad-developers] Call for bitmap help

Le 01/09/2020 à 19:37, Wayne Stambaugh a écrit : I just committed[1] the support to edit symbols in place using the symbol library editor. I used the export symbol icon as a temporary place holder but it's not ideal. If someone has the time, I would appreciate if you would make a bitmap that

Re: [Kicad-developers] Build broken?

Le 10/08/2020 à 11:18, Roberto Fernández Bautista a écrit : > Hi Jon, > > Thanks for that commit - it does appear that it fixed one compile issue, > however it appears there is > a second one. Just to make sure it was nothing related to my branch, I pulled > latest from master > (commit 

Re: [Kicad-developers] Master won't build

Le 07/08/2020 à 05:41, Brian Piccioni a écrit : > FYI I pulled master origin a few hours ago and it fails with > > [ 98%] Linking CXX shared module _pcbnew.kiface > C:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/10.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe: > >

Re: [Kicad-developers] Net Tie specification?

Currently, the best doc about net ties ( and microwave components that create similar problems) is: https://lists.launchpad.net/kicad-developers/msg24455.html ([RFC] On net ties, microwave tools & custom pad shapes, altogether.) Le 30/07/2020 à 01:59, Jon Evans a écrit : > From this comment,

Re: [Kicad-developers] Castellated edge support in v5.99

Le 23/07/2020 à 14:19, Jon Evans a écrit : > Local rules will be done with zones: you can give a name to a copper or > keepout zone and use it to define a rule. If you want a zone that is > only used to define a rule and has no other effect, use a keepout that > has no restrictions set. > >

Re: [Kicad-developers] Profligacy of messages/ link errors building 5.99 on Windows 10/Msys

Le 23/07/2020 à 00:39, Jon Evans a écrit : > If it is the commit I made that Ian points out, I won't be able to debug > it very effectively.  I don't have a msys2 build environment, and it > seems to work on all the platforms I do have. > > On Wed, Jul 22, 2020 at 6:38 PM Wayne Stambaugh

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

Le 30/06/2020 à 00:13, hauptmech a écrit : > > While I agree that it is not KiCad's job to do archival backups or version > control, I do think that KiCad should preserve the integrity of users data > through a crash. Even better if the work between the last save and the crash > is also

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

Le 20/06/2020 à 22:40, Jeff Young a écrit : > Some answers below: > >> On 20 Jun 2020, at 06:39, mailto:pjmo...@csi.com>> >> mailto:pjmo...@csi.com>> 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

Re: [Kicad-developers] Build on msys2 fails : libngspice-x.dll not found in any executable path

Le 25/05/2020 à 15:33, Brian Piccioni a écrit : > Unfortunately, while we seem to get past the libngspice-0.dll problem with > the fix, the old workaround  for the python problem no longer works. > > cmake -DCMAKE_BUILD_TYPE=Debug \ > -DKICAD_SCRIPTING=OFF\ I believe this

Re: [Kicad-developers] Build on msys2 fails : libngspice-x.dll not found in any executable path

Le 23/05/2020 à 17:55, jp charras a écrit : > Le 23/05/2020 à 17:35, Wayne Stambaugh a écrit : >> There is definitely something wrong but I'm not sure where the issue is. >> I downgraded both cmake a couple of versions but cmake started >> complaining about missing librar

Re: [Kicad-developers] Build on msys2 fails : libngspice-x.dll not found in any executable path

Le 23/05/2020 à 17:35, Wayne Stambaugh a écrit : > There is definitely something wrong but I'm not sure where the issue is. > I downgraded both cmake a couple of versions but cmake started > complaining about missing libraries. I even modified Findngspice.cmake > with the absolute path to

Re: [Kicad-developers] KiCad website

Le 23/05/2020 à 15:26, Wayne Stambaugh a écrit : > I don't know if it was intentional (I'm guessing not) but the KiCad > website looks completely different today on Firefox and Chrome (see > attached screen shot). Clicking on the topic links doesn't even take me > to the correct page. > >

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

Le 07/05/2020 à 20:15, Jeff Young a écrit : > 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

Re: [Kicad-developers] 5.1 branch freeze

Le 06/05/2020 à 00:09, Nick Østergaard a écrit : > Mmm, when you mean branch freeze, I assume you really mean that we > have a string freeze for the branch. > > I am sorta wondering why we can't enable the CI, for example. [1] > > Also as a heads up, there a couple of critical issues for the

Re: [Kicad-developers] DRC changes

Le 26/04/2020 à 16:15, Jeff Young a écrit : > Hi JP, > > Did they report the same number of errors? > > Thanks, > Jeff. > No: The old algo reports 0 error. The new reports a lot. I am thinking there is an issue with rectangular or round/rect pads rotated by +- 90 deg. -- Jean-Pierre

Re: [Kicad-developers] DRC changes

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

Re: [Kicad-developers] Removal of some globals

Le 05/04/2020 à 17:20, Jeff Young a écrit : > 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. > >

Re: [Kicad-developers] Please be kind towards translators

Le 05/04/2020 à 10:55, jp charras a écrit : > Le 05/04/2020 à 10:49, Marco Ciampa a écrit : >> Hello devs, >> I often see many messages like those of the newly merged Altinium importer: >> >> stream has no properties >> stream was not parsed correc

Re: [Kicad-developers] Please be kind towards translators

Le 05/04/2020 à 10:49, Marco Ciampa a écrit : > Hello devs, > I often see many messages like those of the newly merged Altinium importer: > > stream has no properties > stream was not parsed correctly > > etc. > > for the sake of reducing traslation strings, could you please add a %s

Re: [Kicad-developers] [commit 85c2e0d2] pcbnew/drc/drc_tree_model.cpp

Le 04/03/2020 à 10:44, BERTRAND Joël a écrit : > Hello, > > With gcc version 9.2.1 20200224, current master compilation fails with : > > /home/bertrand/git/kicad/pcbnew/drc/drc_tree_model.cpp:201:54: error: > operands to ?: have different types ‘const wxString’ and ‘const wxChar*’ >

Re: [Kicad-developers] Who has access to confidential issues?

Le 28/02/2020 à 14:03, Seth Hillbrand a écrit : > On 2020-02-28 04:59, Eeli Kaikkonen wrote: > >> On Fri, Feb 28, 2020 at 1:55 PM jp charras > <mailto:jp.char...@wanadoo.fr>> wrote: >> >> Unfortunately, issue 3955 does not exist on Gitlab: latest is 3954.

Re: [Kicad-developers] pcbnew extremly slow

Le 28/02/2020 à 12:46, BERTRAND Joël a écrit : > BERTRAND Joël a écrit : >> Seth Hillbrand a écrit : >> >>> Hi Joël- >>> >>> Please open an issue report at >>> https://gitlab.com/kicad/code/kicad/issues and attach the project. >>> >> >> Done. >> https://gitlab.com/kicad/code/kicad/issues/3955 > >

Re: [Kicad-developers] Fedora build failures

Le 17/02/2020 à 16:12, Steven A. Falco a écrit : > 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_LINK -DDEBUG -DEESCHEMA

Re: [Kicad-developers] Internal units in the KiCAD source code

Le 13/02/2020 à 20:08, jp charras a écrit : > Le 13/02/2020 à 15:46, Wayne Stambaugh a écrit : >> Hi Johannes, >> >> Thank you for your suggestion but the internal units for each format >> were chosen for a specific reason. There really is no justifiable >> reason

Re: [Kicad-developers] Internal units in the KiCAD source code

Le 13/02/2020 à 15:46, Wayne Stambaugh a écrit : > Hi Johannes, > > Thank you for your suggestion but the internal units for each format > were chosen for a specific reason. There really is no justifiable > reason to change them as they have been carefully selected based on the > requirements of

Re: [Kicad-developers] Two patches to submit (eeschema)

Le 10/02/2020 à 19:37, Ian McInerney a écrit : > Sylwester, > > Would it be possible for you to submit these are two merge requests to the > KiCad GitLab repository: https://gitlab.com/kicad/code/kicad/-/tree/master. > We have started to use the merge requests to better track and review the >

Re: [Kicad-developers] Repeat request for help from icon maintainer.

cluded file. the first useful line of my script running cmake is: export PATH=$WXMSW:$PATH:/d/inkscape:/d/pngcrush You will have to remove inkscape from msys2. Attached, my msys2 script to run cmake. Good luck... > > On 2020-02-04 9:34 a.m., jp charras wrote: >> Le 04/02/2020

Re: [Kicad-developers] Repeat request for help from icon maintainer.

Le 04/02/2020 à 15:06, Brian Piccioni a écrit : > Hello > > I emailed earlier because when I follow the directions to create a new > icon under MSYS2 it fails. > > This means that either > > 1) the directions are wrong or > 2) I am following them incorrectly. > > Perhaps an icon maintainer can

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

Le 28/01/2020 à 17:15, jp charras a écrit : > Le 28/01/2020 à 15:32, Seth Hillbrand a écrit : >> No need.  It has already been reported with reproduction steps here >> https://gitlab.com/kicad/code/kicad/issues/3811 >> >> If you find a bug, use the standard bug r

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

is schematic has only had one sheet ever. >> >> I shall recompile the master branch and try and boil down the >> schematic to something simple to test. >> >> Brian >> >> >> >> On 2020-01-28 3:36 a.m., jp charras wrote: >>> Le 28/0

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

Le 28/01/2020 à 01:10, Brian Piccioni a écrit : > Hello > > I have been using Kicad while working on re-annotation (hopefully > Alexander's merge request will soon be accepted and I can dust off mine). > > I have been using branches of the current master. I have noticed a few > issues which I

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

Le 20/01/2020 à 17:19, Jon Evans a écrit : > This does appear to have broken at some point.  Filed an issue for it: > https://gitlab.com/kicad/code/kicad/issues/3791 > > -Jon Fixed. > > On Mon, Jan 20, 2020 at 11:10 AM Dick Hollenbeck > wrote: > > Quick help, >

[Kicad-developers] New Feature: Pad property.

Hi All, FYI, I just added a new feature, only used in Gerber files: Pad property. This is a pad property for fabrication, used in latest Gerber file specification (copper layers plots and drill files) Property is a pad info used mainly for fabrication or test. Currently, supported properties

Re: [Kicad-developers] QA broken for arcs

Le 03/01/2020 à 20:57, Seth Hillbrand a écrit : > Hi Folks- > > It looks like a recent commit broke the QA tests for Arc bbox checks. Commit 5707e6eac should fix this issue. > > > ../../qa/common/geometry/test_shape_arc.cpp(91): error: in > "ShapeArc/BasicCPAGeom": check

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

aze of macros to determine how to do > printf on Windows. I wonder what it ends up doing. There is a special > case just for MINGW32 but not MINGW64. > > https://github.com/wxWidgets/wxWidgets/blob/cc931612eec2e3ea49200ebff45042135f3c3f9c/include/wx/wxcrtvararg.h#L84 > > > On Fri,

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

ussion about this on the mingw users mailing > list:  > https://osdn.net/projects/mingw/lists/archive/users/2019-January/000202.html). > > -Ian I am using mingw32 only. The tools installed by pacman are something like mingw-w64-i686-xxx > > On Fri, Jan 3, 2020 at 2:32 PM jp charras

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

z' in format [-Wformat=] > > On Fri, Jan 3, 2020 at 9:32 AM jp charras <mailto:jp.char...@wanadoo.fr>> wrote: > > Le 03/01/2020 à 15:10, Jon Evans a écrit : > > I found it defined in > > > C:\msys64\mingw64\include\c++\8.3.0\x86_64-w64-mingw32\bits

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

Le 03/01/2020 à 15:10, Jon Evans a écrit : > 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? I confirm the %zu is not working on

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

ersion to string. OK. I am thinking we have to use a reasonable and readable notation (like in all our kicad files). To encode a board thickness, 1.600 is readable. 1.600088817841970012523233890533447265625 is just ridiculous (for any value in a config file). > > On Sat

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

Le 24/12/2019 à 21:43, Jon Evans a écrit : > OK, so both the JSON format itself and the Ucamco gerber format (which > is not necessarily the same as the job file format, but hey) specify > storing doubles. > But, the examples in the Ucamco doc, and KiCad itself, do not store doubles. > > I have

Re: [Kicad-developers] [PATCH] Drop "const" that breaks Windows-specific code

Le 06/12/2019 à 11:28, Simon Richter a écrit : > --- > common/gestfich.cpp | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > I already fixed this issue. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post

Re: [Kicad-developers] What does "when in doubt do it opposite than certain other pcb tool" stand for?

Le 26/11/2019 à 18:45, Seth Hillbrand a écrit : > On 2019-11-26 09:43, Andy Peters wrote: > >> On Nov 26, 2019, at 10:41 AM, Seth Hillbrand wrote: >> >> On 2019-11-26 09:05, Tomasz Wlostowski wrote: >> On 22/11/2019 17:42, Rene Pöschl wrote: >> I would assume this is referencing version 6 of

Re: [Kicad-developers] GitLab migration

Le 25/11/2019 à 17:53, Kevin Cozens a écrit : > On 2019-11-25 11:03 a.m., Seth Hillbrand wrote: >> 2FA would be using something like Google Authenticator on your phone, >> a YubiKey or SMS message code to verify your login on a computer in >> addition to the password. > > It may not affect me as

Re: [Kicad-developers] Using OPT types

Le 24/11/2019 à 18:09, Wayne Stambaugh a écrit : > On 11/24/19 7:12 AM, Jeff Young wrote: >> Personally I hate OPT (because it’s somewhat harder to read and >> more-than-somewhat harder to debug). > > I tend to agree with Jeff. The older I get, the less I like having to > dig around the code

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

Le 24/11/2019 à 07:58, Alexander Shuklin a écrit : > Hi Eeli and Brian, > Sorry for delay, unfortunately I cannot answer too often. > >> It has occurred to me (Alexander please chime in) that once back annotation >> has been solved subject to all the issues raised by Wayne and others that it >>

[Kicad-developers] INFO: added a enhancement: schematic pin function stored in pads.

I just added a enhancement in Pcbnew: After updating the PCB from schematic, the pin names (pin functions) are now stored in Pads. When not empty, they are shown in the message panel (bottom of the pcb editor frame) among other pad settings (like netname). This enhancement is due to the fact

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

Le 23/11/2019 à 00:05, ja...@veith.net a écrit : >> On 22.11.19 21:12, Wayne Stambaugh wrote: >> What Jeff described is the simplest case.  Where things really get >> interesting is when you start sharing schematic files between projects. > > Imho multiple use of a schematic requires separate

Re: [Kicad-developers] [PATCH] Pcbnew drill sizes statistics & Project manager multiple selection options

ets 3.1.3 currently. (I sometimes rebuild Kicad with wxPython on wxWidgets 3.0.4, for tests) > On Thu, 7 Nov 2019, 14:37 jp charras, <mailto:jp.char...@wanadoo.fr>> wrote: > > Le 06/11/2019 à 23:18, Mikołaj Wielgus a écrit : > > Hello, > > > > I ha

Re: [Kicad-developers] [PATCH] Pcbnew drill sizes statistics & Project manager multiple selection options

pending on the platform and wxWidgets version) In this case, this sizing problem is a minor issue. > > On Thu, Nov 7, 2019 at 3:37 PM jp charras <mailto:jp.char...@wanadoo.fr>> wrote: > > Le 06/11/2019 à 23:18, Mikołaj Wielgus a écrit : > > Hello, > &g

Re: [Kicad-developers] [PATCH v3] [NEW] eeschema: Allow hierarchy navigator to stay open

Le 10/11/2019 à 17:33, Franck Jullien a écrit : > Le jeu. 7 nov. 2019 à 21:51, a écrit : >> >> From: Franck Jullien >> >> User can now decide to keep the hierarchy navigator open while working >> on a schematic. This behavior can be configured in >> eeschema->preferences->eeschema->Editing

Re: [Kicad-developers] Symbol library code changes

Le 06/11/2019 à 21:34, Wayne Stambaugh a écrit : > I finally finish up the initial attempt at simple inheritance for the > symbol library code. The change is non-trivial and will likely have > some unexpected side affects that I missed. I pushed the branch to my > personal repo[1] and I would

Re: [Kicad-developers] LOCALE_IO thread-local

Le 21/06/2019 à 23:25, Seth Hillbrand a écrit : > Hi Devs- > > We currently have an RAII locale switch (LOCALE_IO) that swaps the > global locale to allow floating point handling with decimal points > instead of a commas.  Because it changes the global locale, we need to > be very careful about

Re: [Kicad-developers] New lead developer announcement

> On 11/7/19 12:14 PM, 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 contributions have >> earned him this privilege

Re: [Kicad-developers] [PATCH] Pcbnew drill sizes statistics & Project manager multiple selection options

Le 06/11/2019 à 23:18, Mikołaj Wielgus a écrit : > Hello, > > I have submitted two patches on Launchpad some time ago. I would like to > ask for feedback. > > Links: > https://bugs.launchpad.net/kicad/+bug/1841144 > https://bugs.launchpad.net/kicad/+bug/1016464 > > Best Regards, > Mikołaj

Re: [Kicad-developers] KICAD_USE_FONT_REDUCED_SET question

Le 19/10/2019 à 07:03, Seth Hillbrand a écrit : > On 2019-10-09 02:26, jp charras wrote: >> >> Hi Seth, >> >> Here is a test showing the memory used by pcbnew, with and without CJK >> font (I used the Windows monitor resources): >> >> Initial

Re: [Kicad-developers] Should gerber files in protel format use same name? (PATCH?)

Le 16/10/2019 à 09:36, Nick Østergaard a écrit : > A related issue was brought up on > https://forum.kicad.info/t/gerber-filenames-with-protel-extensions/14177 > > I think the manufacturer should only make it a warning not an error. I > assume their reasoning is that they want to make sure only

Re: [Kicad-developers] Footprint keepout zone merge review

Le 09/10/2019 à 00:00, Wayne Stambaugh a écrit : > Seth, > > Please let me finish testing and reviewing the latest changes before you > merge it. Sorry about the delay in responding. I have been busy > putting the finishing touches on the LIB_PART refactor for the upcoming > symbol library file

Re: [Kicad-developers] KICAD_USE_FONT_REDUCED_SET question

Le 07/10/2019 à 20:07, Seth Hillbrand a écrit : > Hi JP- > > > I noticed that you added an option to disable the CJK ideographs > in 34b26a0ac because you were seeing out of memory issues under OpenGL.  > The stroke fonts should only be loading on the system heap (4.5MB for > the current CJK

Re: [Kicad-developers] [Patch] Update build documentation with debugging options

Le 05/10/2019 à 19:11, Ian McInerney a écrit : > This is purely a documentation update for the dev docs. It adds the new > debugging options that enable GLib assertions, the Address Sanitizer and > Valgrind support into the documentation so they are accessible and > documented. > > -Ian > I

Re: [Kicad-developers] Commit 0a829c328e90f550994a7660b310630a5aa02361 not compiling ("undefined reference to `PgmOrNull()'")

Le 05/10/2019 à 12:20, Dino Ghilardi a écrit : > Hello, > > Latest commit (master branch) is not compiling giving an > "undefined reference to `PgmOrNull()'" error during make Should be fixed now. > > I tried also using: > git clean-fx > make clean > cmake ../ > make -j7 > > may be something

Re: [Kicad-developers] Commit 0a829c328e90f550994a7660b310630a5aa02361 not compiling ("undefined reference to `PgmOrNull()'")

Le 05/10/2019 à 13:07, Ian McInerney a écrit : > I am somewhat confused by the reason for needing to introduce the new > function in that commit. Does this crash happen when running the Python > from inside Pcbnew or when trying to run Pcbnew python bindings from the > system Python prompt? The

Re: [Kicad-developers] [Patch] Pcb Calculator: Convert tracks width versus current formula

Le 04/10/2019 à 17:15, Jakub Kozdon a écrit : > Hi Jean-Pierre, > > This came from discussion on bug 1818998. I hope that this patch will > work correctly. > > I will also look at eeschema/dialogs/dialog_bom_help.html > > Jakub > Hi Jakub, Your patch works fine, and I committed it. Thanks

Re: [Kicad-developers] [Patch] Handle Cvpcb save actions immediately

Le 18/09/2019 à 10:13, Ian McInerney a écrit : > Ping. > > On Mon, Sep 9, 2019 at 7:05 AM Ian McInerney > wrote: > > This patch updates Cvpcb to run the save actions immediately when > the buttons are pressed. If they are not run immediately, then the >

Re: [Kicad-developers] [Patch] Overbright view in 3D legacy render

Le 08/09/2019 à 12:44, Michal Jahelka a écrit : > This patch adds missing material parameter m_Emissive set to (0,0,0) in > kicad/3d-viewer/3d_rendering/3d_render_ogl_legacy/c3d_render_ogl_legacy.cpp. > Before this was PCB overbrighted (especially solder mask) and sometimes > with bad colors. With

Re: [Kicad-developers] [RFC] Comments for a Layer Stack Manager in Pcbnew

Le 06/09/2019 à 12:04, Michael Kavanagh a écrit : > Hi JP, > > This will be a great addition to KiCad, and I'm excited to see this > progress. Now it's merged into master, would you prefer feedback on > the mailing list or bug reports? > > In any case, the panel display seems to be broken on

Re: [Kicad-developers] [RFC] Comments for a Layer Stack Manager in Pcbnew

I just committed the Layer Stack Manager feature. Some comments below: Le 03/09/2019 à 20:47, Evan Shultz a écrit : > A few comments from the peanut gallery using Simon's "497" build... > > Some things Seth suggested that I support and don't see: > - Units could be shown once at the top of the

[Kicad-developers] Commit c8a6878 breaks compilation on msys2

common.h does not compile with msys2/gcc 9.1.0 Here is the error message: In file included from D:/wxWidgets-3.1.1/include/wx/defs.h:851, from D:/wxWidgets-3.1.1/include/wx/wx.h:14, from E:/kicad-launchpad/gerber_dev/include/common.h:37, from

Re: [Kicad-developers] [RFC] Comments for a Layer Stack Manager in Pcbnew

Le 02/09/2019 à 14:06, Simon Richter a écrit : > Hi, > >> Please test and comment. >> I want to commit this feature soon. > > Builds on msys2 and msvc are on the way: > > https://jenkins.simonrichter.eu/job/windows-kicad-msys2-patch/495/ >

Re: [Kicad-developers] [RFC] Comments for a Layer Stack Manager in Pcbnew

I just finished the version of board stack manager that should fix all issues and remarks previously made, and has some tests to avoid incorrect parameters. The patch is against latest master branch version (5.99.0-48) The stackup settings is now in the board settings dialog. Note also the board

Re: [Kicad-developers] 5.1.5 RC?

Le 30/08/2019 à 16:35, Nick Østergaard a écrit : > What was the command that could be added the the schematic to make > ngspice print the version info about itself in the output text shown > in the bottom of the simulator window? > Hi Nick, You can try: .control version .endc It works for me

Re: [Kicad-developers] [RFC] Comments for a Layer Stack Manager in Pcbnew

od place for this stack manager could be inside a CAM tool that allows to create all files (Gerber, drill files and gbrjob file) in one command, with the same settings. The the current stack manager dialog should be seen only as a temporary dialog. What about merging the code to master, and us

Re: [Kicad-developers] [Patch] Fix some memory leaks

Le 12/08/2019 à 21:54, Wayne Stambaugh a écrit : > Sounds like a plan. If there are not bug reports against this over the > next month, I'll will cherry-pick it into 5.1. > > Wayne I am not sure this issue exists in 5.1. AFAIK it comes from moving code from our DLIST to std::deque, only in

[Kicad-developers] [RFC] Comments for a Layer Stack Manager in Pcbnew

Since a long time, I started (slowly...) a layer stack manager. The purpose is to allow users to define (for board fabrication) some important parameters like: - tech, copper and dielectric thickness - color of some tech layers - dielectric material - board constraints. All of these parameters

Re: [Kicad-developers] 5.1.3 release

Hi Wayne, If the 5.1.3 is built from tag 5.1.3 (jul 25) version, there is a very annoying bug: Bug #1838446 This bug was fixed the Jul 31. This bug make impossible updating footprints, both from the dialog and from schematic, because the new footprint is not at the right place (the old

Re: [Kicad-developers] Eeschema selection

Le 01/08/2019 à 06:54, Jeff Young a écrit : > Hi JP, > > I’ve pushed another version which uses the platform selection colour (blue on > OSX). Let me know how that looks on your machine. > > Cheers, > Jeff. > Much better now. Thanks. > >> On 30 Jul

Re: [Kicad-developers] Tool processing & RunHotKey return

oesn't seem like a good solution to the problem though, because it >> causes more issues with other keys as well (for instance, if nothing is >> assigned to shift+A, then it just runs the hotkey for A instead). >> >> Is there a reason not to just skip all keyboard events w

Re: [Kicad-developers] Eeschema selection

Le 30/07/2019 à 05:01, Jeff Young a écrit : > Hi Nhat, > > The colours of the “shadows” are the same as the elements themselves — > so they can be configured the normal way. > > And yes, the shadow width scales with the zoom factor.  It’s not 100% > the same across all zoom sizes as it looks

Re: [Kicad-developers] Tool processing & RunHotKey return

Le 28/07/2019 à 02:22, Jeff Young a écrit : > I think JP ran into this earlier, so he might know more about it. In fact issue I h=worked on was the fact the Char events where no correctly skipped. If I correctly understand the issue related by this mail, this is a dispatch issue. I am thinking

Re: [Kicad-developers] fp-info-cache question

Le 23/07/2019 à 20:09, Seth Hillbrand a écrit : > On 2019-07-23 13:38, jp charras wrote: >> Le 23/07/2019 à 19:22, Jeff Young a écrit : >>> Hi Seth, >>> >>> I think that would work.  And you’re right — there probably aren’t >>> enough project libs to

Re: [Kicad-developers] fp-info-cache question

Le 23/07/2019 à 19:22, Jeff Young a écrit : > Hi Seth, > > I think that would work. And you’re right — there probably aren’t enough > project libs to require a cache for them. I am not sure to understand. The cache is by lib table, or by library file? This is very different: if it is by lib

Re: [Kicad-developers] [PATCH] Board statistics dialog

Le 22/07/2019 à 10:13, Alexander Shuklin a écrit : > Hi! > I'll have a look to add vias count to dialog. > There's some questions: > > 1)I don't have too much experience with wxdialogs. There was commit on > master, which says: >>> remove settings for fg/bg color: the result is unpredictable: was

Re: [Kicad-developers] MOD_VIRTUAL flag

Le 22/07/2019 à 06:03, Jeff Young a écrit : > This flag tells us that there’s no physical object for a pick-n-place > machine. But is it also true that there’s no corresponding symbol in the > schematic, or are there some virtual footprints that would have a symbol? > > What about some

  1   2   3   4   5   6   7   8   9   10   >