Re: [Kicad-developers] 6.0 string proposal

ing to be re-writing the parsers and formatters for > s-expr so it’s going to be all different code anyway.  (Granted the new > code could have used the old infrastructure, but I think we need to wean > ourselves from wxString either way.) > >> On 30 Apr 2019, at 13:59, Wayne Stamba

Re: [Kicad-developers] Modern toolset usability improvements

> 5.1 does have a hotkey for delete node, but on OSX at least it steals the > delete key from other things, so users have to disable (or reassign) it > anyway. > > Cheers, > Jeff. > > >> On 30 Apr 2019, at 14:06, Wayne Stambaugh wrote: >> >> Just so I under

Re: [Kicad-developers] Modern toolset usability improvements

Just so I understand what you are proposing, backspace will remove a wire node (segment) and delete will remove the entire net. The legacy behavior was very convenient so we should think carefully before changing it. On 4/30/19 7:49 AM, Jeff Young wrote: > For the most part the modern toolset

Re: [Kicad-developers] 6.0 string proposal

Given that std::wstring is platform dependent, I would be opposed to using it. I'm not opposed to std::u32string but UTF8 is pretty well vetted so please keep that in mind. I think the possibility of breakage is low but I'm not naive enough to think that it's zero. You would have to do some

Re: [Kicad-developers] Kudos to Michael Kavanagh

On 4/29/19 2:51 PM, Seth Hillbrand wrote: > Am 2019-04-29 14:39, schrieb Wayne Stambaugh: >> On 4/26/19 6:01 PM, Michael Kavanagh wrote: >>> Ha, thanks! >>> >>> On that note, there are a lot of old bugs marked as "Fix Committed", but >>> bec

Re: [Kicad-developers] Kudos to Michael Kavanagh

On 4/26/19 6:01 PM, Michael Kavanagh wrote: > Ha, thanks! > > On that note, there are a lot of old bugs marked as "Fix Committed", but > because they were never associated to a milestone (or some other reason) > the Janitor never cleaned them up to "Fix Released" when they were in > fact

Re: [Kicad-developers] GLM 0.9.9.3 and GLM_FORCE_PURE

Rather than remove it completely, how about build option to disable the SIMD on platforms that don't support it. Even better, there is probably a way to query the compiler to check if it supports SIMD and enable/disable accordingly. Wayne On 4/29/19 5:45 AM, Mário Luzeiro wrote: > Hi Seth,

Re: [Kicad-developers] eemodern branch

On 4/29/19 12:56 PM, Andy Peters wrote: > > >> On Apr 28, 2019, at 8:22 PM, hauptmech wrote: >> >> On 29/04/2019 12:52 AM, Jeff Young wrote: >>> 3) Cut/copy/paste is now text-based over the system clipboard. (This means >>> you can also copy/paste between schematics, or even between your

Re: [Kicad-developers] Project annuouncement.

JP, On 4/28/19 3:30 AM, jp charras wrote: Le 27/04/2019 à 20:05, Wayne Stambaugh a écrit : For those you who haven't heard yet, I made the announcement yesterday at KiCon that I am now work for WIT and I will be working full time on KiCad.  I really excited about the possibilities for KiCad

Re: [Kicad-developers] Project annuouncement.

Thank you everyone for the congrats. WIT is a start up that is attempting to open the full stack from top to bottom (software and hardware at all levels). There website is WIT.com but there is not a lot of information there yet but there are lots of things in progress that I am not at

Re: [Kicad-developers] Project annuouncement.

/19 4:33 AM, Javier Serrano wrote: Great news, and quite a milestone for KiCad! Congratulations Wayne! Cheers, Javier On Sat, Apr 27, 2019 at 8:05 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote: For those you who haven't heard yet, I made the announcement yesterday

[Kicad-developers] Project annuouncement.

For those you who haven't heard yet, I made the announcement yesterday at KiCon that I am now work for WIT and I will be working full time on KiCad. I really excited about the possibilities for KiCad going forward. Here is the moment when I made the announcement at KiCon.

[Kicad-developers] 5.1.2 release.

I just pushed the 5.1.2 release announcement. The website will be updated on the next build cycle. Thank you to everyone for your continued efforts. Cheers, Wayne ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

Re: [Kicad-developers] Kudos to Michael Kavanagh

Indeed! Keep up the great work Michael. Cheers, Wayne On 4/26/19 5:24 AM, Jeff Young wrote: Just wanted to send out a quick note of appreciation regarding all the work Michael is doing to keep the bug database clean. Cheers, Jeff. ___ Mailing

Re: [Kicad-developers] kicad_pcb, kicad_mod format change for daily build?

Dick, On 4/24/19 7:39 PM, Dick Hollenbeck wrote: On 4/15/19 8:50 AM, jp charras wrote: Le 15/04/2019 à 15:34, Jeff Young a écrit : Yes, this was intentional. It allows users to put things like spaces in layer names and other user-editable things. I’ll fix up the STEP exporter…. On 15 Apr

[Kicad-developers] KiCon update.

For those of you who are heading to KiCon and hoping to meet up with me before the meet up at Ballast Point Brewing, my flight has been delayed. I will not be arriving in Chicago until 4:15PM so I will be scrambling just to make the meet up. The joys of air travel :(. Cheers, Wayne

Re: [Kicad-developers] Improving library editor checks

set of checks that would return result objects that KiCad > could later show. > > Is this approach better? If so, given my lack of knowledge about KiCad > codebase, I would need some help designing that interface. > > Thank you for your feedback! > > > > > > &

Re: [Kicad-developers] Improving library editor checks

Antonio, Exactly what checks are you planning on implementing? As long as they are generic in nature like off grid pin checking, then I'm fine with that. If they are specific KLC checks like spacing, line width, etc, that is a different issue. We should not be forcing KLC rules on all users.

Re: [Kicad-developers] 5.1.2 release announcement initial draft

I believe they are in testing and ready to go. On 4/24/19 6:21 PM, Andrew Lutsenko wrote: > Windows 5.1.2 builds are still not available in stable folder  > https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/stable/ > > On Wed, Apr 24, 2019 at 3:04 PM Wayne Stambaugh <

[Kicad-developers] 5.1.2 release announcement initial draft

I just pushed the 5.1.2 release announcement initial draft to the website repo. As soon as we have macos builds ready, I will remove the draft tag unless there is something else holding up the release. Please let me know. Cheers, Wayne ___ Mailing

Re: [Kicad-developers] CI builds

; > Or, I can wait on doing anything and create a job that just builds. > > Adam > > On Wed, Apr 24, 2019 at 12:48 PM Wayne Stambaugh wrote: >> >> I wouldn't have an issue with forwarding build errors to the dev mailing >> list as long as the build failure message

Re: [Kicad-developers] CI builds

I wouldn't have an issue with forwarding build errors to the dev mailing list as long as the build failure messages were limited to compile/link errors due to broken source repo commits. I don't think it's necessary for devs to see all of the other unrelated build issues. I don't know if it

Re: [Kicad-developers] There seems to be an serious issue with netlist handling in KiCad 5.1.1

Thomas, This has been fixed in the master and 5.1 branches and 5.1.1 will not be officially released.  The next stable release will be 5.1.2 which is officially due out any day.  I apologize for the inconvenience. Cheers, Wayne On 4/21/2019 5:08 AM, Thomas Pointhuber wrote: Hi, I made a

Re: [Kicad-developers] recent macos build failures

I guess this means that on macos we will have to package 5.1.2-2-gb6c9d4a8 as stable instead of 5.1.2 for older versions of macos. Sigh! Cheers, Wayne On 4/24/2019 9:34 AM, John Beard wrote: Hi Adam, The fix was only made on master. I have pushed it to 5.1 as commit

Re: [Kicad-developers] [PATCH] Add return value to SCH_PIN::operator=

Jeff, Does this patch affect the 5.1 branch? If so, please cherry-pick it when you get a chance. Thanks, Wayne On 4/22/2019 7:28 PM, Jeff Young wrote: Thanks, Simon. I’ve merged your patch. On 22 Apr 2019, at 15:35, Simon Richter wrote: --- eeschema/sch_pin.cpp | 1 + 1 file changed,

Re: [Kicad-developers] Doxygen docs stylesheet seems broken

I'm using Chrome on windows right now so maybe it's a Chrome on linux issue. On 4/23/2019 1:55 PM, Jon Evans wrote: Looks like it is broken on Chrome and working on Firefox now On Tue, Apr 23, 2019 at 1:40 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote: I noticed this l

Re: [Kicad-developers] XSPICE code models in the simulator

Hi Dmitry, On 4/23/2019 9:16 AM, Dmitry Salychev wrote: On Tue, Apr 23, 2019 at 08:51:04AM -0400, Jon Evans wrote: Hi Dmitry, You probably want to start by looking at the netlist exporter: ./eeschema/netlist_exporters/netlist_exporter_pspice.cpp I think much of what you are looking for is in

Re: [Kicad-developers] Doxygen docs stylesheet seems broken

I noticed this last night but I just checked and it looks fine now. I'm not sure if something changed since last night or if it was the fact that I was using Chrome on linux versus windows. Wayne On 4/23/2019 11:56 AM, Jon Evans wrote: http://docs.kicad-pcb.org/doxygen/index.html This does

Re: [Kicad-developers] 5.1.1 issue

github and added a note that that release > got retracted.) > > On 22/04/19 14:43, Wayne Stambaugh wrote: >> I will tag the source repo to 5.1.2 this evening when I get home from >> work so please tag the other repos for 5.1.2 at the same commit as >> 5.1.1.  Hopefully

Re: [Kicad-developers] 5.1.0 nightlies?

put > these in nightlies/5.1? > > Adam > > On Mon, Apr 22, 2019 at 9:35 AM Wayne Stambaugh > mailto:stambau...@gmail.com>> wrote: > > > > Adam, > > > > Nightly 5.1 builds would be really helpful.  We have discuss

Re: [Kicad-developers] 5.1.1 issue

On 4/22/2019 11:22 AM, Seth Hillbrand wrote: Am 2019-04-22 08:43, schrieb Wayne Stambaugh: I will tag the source repo to 5.1.2 this evening when I get home from work so please tag the other repos for 5.1.2 at the same commit as 5.1.1.  Hopefully we can get this version released. Can we get

Re: [Kicad-developers] 5.1.0 nightlies?

Adam, Nightly 5.1 builds would be really helpful. We have discussed doing this so hopefully we can provide them for most platforms. Given that the 5.0 branch is no longer supported, I cannot think of a reason to continue nightly 5.0 builds. I'm guessing having testing branch folders is a

Re: [Kicad-developers] 5.1.1 issue

<mailto:stevenfa...@gmail.com>> wrote:     On 4/21/19 5:18 PM, Wayne Stambaugh wrote:     > It's looks like 5.1.1 has a serious issue which was fixed and     will be     > released in 5.1.2.  Since folks have already started downloading     5.1.1,     > I don't think changing the 5.1.1

Re: [Kicad-developers] 5.1.1 issue

ive us more testing of the current stable release branch between releases. It most likely would have prevented the current situation. Cheers, Wayne > > > > Den 21. april 2019 kl. 23.18.53 +02.00, skrev Wayne Stambaugh > : >> It's looks like 5.1.1 has a serious issue

[Kicad-developers] 5.1.1 issue

It's looks like 5.1.1 has a serious issue which was fixed and will be released in 5.1.2. Since folks have already started downloading 5.1.1, I don't think changing the 5.1.1 tag is a good idea. How much trouble would it be to spin 5.1.2 and skip formally releasing 5.1.1? I'm fine if we use the

Re: [Kicad-developers] A neat decision-making scheme

As long as the only members of the lead development team have voting rights and the project leader has veto power than I am fine with this. I haven't had to use veto power yet but I am not naive enough to believe that there are no circumstances which I wouldn't veto a majority vote. Cheers,

Re: [Kicad-developers] 5.1.1 release reminder.

are pointing fingers at each other and I don't see any upstream progress. :( It may be a few days. I apologize for holding up the releases! Adam On Fri, Apr 19, 2019 at 10:30 AM Wayne Stambaugh wrote: Are we ready to make the release announcement? I didn't see the macos 5.1.1 package

Re: [Kicad-developers] 5.1.1 release reminder.

15.32 skrev Adam Wolf mailto:adamw...@feelslikeburning.com>>: Are the rest of the parts tagged?  Is the docs tarball ready? Thanks! Adam On Wed, Apr 17, 2019 at 6:34 AM Wayne Stambaugh mailto:stambau...@gmail.com>> wrote: > > Nick, >

Re: [Kicad-developers] Release 5.1.1_1 Windows build

Hi Tedd, I just downloaded and installed kicad-5.1.1_1-x86_64.exe from https://kicad-downloads.s3.cern.ch/index.html?prefix=windows/testing/ without any issues so the issue appears to be with your download. Cheers, Wayne On 4/18/2019 7:49 AM, tedd.t...@gmail.com wrote: Hi, I've

Re: [Kicad-developers] 5.1.1 release reminder.

projects as usual. @Wayne Stambaugh <mailto:stambau...@gmail.com> do you have a release announcement ready? I don't see a draft pushed. On Mon, 15 Apr 2019 at 21:30, Jean-Samuel Reynaud <mailto:js.reyn...@gmail.com>> wrote: Hi all, Most of packages are ready now

Re: [Kicad-developers] [PATCH] Crash Reporter

Tom, On 4/16/19 4:52 PM, Seth Hillbrand wrote: > Am 2019-04-14 18:50, schrieb Tomasz Wlostowski: >> Dear all, >> >> The attached patchset introduces a builtin crash reporter for Kicad - >> that is a window that pops up in case of a segmentation fault/other >> serious error, kindly apologizes to

Re: [Kicad-developers] [PATCH 2/2] Remove two extraneous spaces from a tooltip

John, I fine with making string changes in 5.1.2 up to the point of the string freeze. I would prefer that we keep the changes to a minimum. The two patches that Simon submitted are fine. Cheers, Wayne On 4/15/19 6:13 PM, John Beard wrote: > Hi Wayne, > > What is the policy for minor string

Re: [Kicad-developers] Very slow all-most lockup, when using BS key, when add part to sch, 5.1.0-110-g3c2761778

Lachlan, I'm not seeing this on windows but my work computer is pretty fast so I may not be a good benchmark. I do not see any lag at all when I hit the BS key in symbol chooser dialog. Wayne On 4/2/2019 1:22 AM, Lachlan Audas wrote: Annoyance/Regression/Bug? When you hit the 'a' in sch

Re: [Kicad-developers] 5.1.1 release reminder.

Hi Jean-Samuel, Sorry about, I just pushed the tag. Wayne On 4/14/19 4:21 PM, Jean-Samuel Reynaud wrote: > Dear Wayne, > > I don't see the tag yet. Did you push it ? > Once done I'll launch ppa builds... > > Regards, > Le 14/04/2019 à 22:08, Wayne Stambaugh a écrit : >

[Kicad-developers] Availability

I just want to give everyone a quick heads up. Between tomorrow and until after KiCon is over I will be really busy at work and getting ready for KiCon so I will most likely not be as available as I normally am. If you don't hear from me promptly please be patient. I will do my best to

Re: [Kicad-developers] 5.1.1 release reminder.

aintainers thought there > will not be another version 5 release. I needed to revert one change > because of that the other 3 where ok in my mind.) > > Everything is detailed in the github issue > https://github.com/KiCad/kicad-symbols/issues/1724 > > On 12/04/19 22:23, Wayne

Re: [Kicad-developers] Zoom & Grid changes

Jeff, I just got this build error on my Ubuntu laptop: /home/wayne/src/kicad-trunk/common/legacy_gal/eda_draw_frame.cpp:66:10: fatal error: eeschema/tools/sch_actions.h: No such file or directory #include ^~ Cheers, Wayne On 4/13/19 1:45 PM, Jeff

[Kicad-developers] KiCon talk schedule.

The KiCon talk schedule[1] has been posted. Go check it out. I'm looking forward to seeing everyone there. Cheers, Wayne [1]: https://kicad-kicon.com/schedule/ ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

[Kicad-developers] 5.1.1 release reminder.

Just a reminder. I will be tagging 5.1.1 Sunday afternoon so any last minute bug fixes should probably be in by tomorrow so I can do a build check and some quick testing to make sure nothing went sideways. Also, please no translatable string changes until we start 5.1.2. Hopefully the library,

Re: [Kicad-developers] small typos (missing spaces)

Marco, Good catch. I just pushed the fix for this. Thanks, Wayne On 4/9/2019 6:51 AM, Marco Ciampa wrote: > Small typos in here (master branch): > > #: pcbnew/exporters/export_hyperlynx.cpp:190 > > m_reporter->Report( > _( "File contains pad shapes

Re: [Kicad-developers] Windows build error.

On 4/8/2019 11:24 AM, jp charras wrote: > Le 08/04/2019 à 17:10, Wayne Stambaugh a écrit : >> According to `git bisect`, commit >> 77f15eeeaf89a5d2179ee800f6faa11faf718d0e broke windows builds (32 and 64 >> bits) with the following error: >> >> C:/msys64/home

[Kicad-developers] Windows build error.

According to `git bisect`, commit 77f15eeeaf89a5d2179ee800f6faa11faf718d0e broke windows builds (32 and 64 bits) with the following error: C:/msys64/home/wstambaugh/src/kicad-trunk/kicad/import_project.cpp:144:46: error: conversion from 'wxString' to non-scalar type 'std::__cxx11::string {aka

Re: [Kicad-developers] Merge schedule

Tom, On 4/8/2019 7:34 AM, Tomasz Wlostowski wrote: > On 05/04/2019 12:09, Jeff Young wrote: >> I’ve got a changelist which cleans up the various SCH_ and LIB_ Draw() >> routines to remove the interactivity features (since they’re now print-only). >> > > Hi all, > > Since we're discussing

Re: [Kicad-developers] 5.1.1

On 4/7/19 10:14 AM, Seth Hillbrand wrote: > Am 2019-04-07 09:00, schrieb Wayne Stambaugh: >> Seth, >> >> I was actually considering this but I was holding off for one last high >> priority bug[1] to be fixed.  I'm fine with pushing the low and medium >> priority

Re: [Kicad-developers] Build Docs Page Not Working

Has this been fixed? It looks fine to me in Chrome. On 4/6/19 11:58 PM, Mark Roszko wrote: > Looks like the last docs build broke on upload. > > On Sat, Apr 6, 2019 at 11:57 PM Mark Roszko > wrote: > > >Resource interpreted as Stylesheet but transferred with

Re: [Kicad-developers] 5.1.1

Seth, I was actually considering this but I was holding off for one last high priority bug[1] to be fixed. I'm fine with pushing the low and medium priority bugs to 5.1.2. Any one have time to take a stab at fixing this bug? I could take a look at it but I really need to get moving on my KiCon

Re: [Kicad-developers] Are we still cascading merges?

Jeff, I've dropped the ball on this but we should try our best to not step on each others toes. I would think your escaped characters patch can be merged. AFAIK, your UpdatePCBFromSchematic work shouldn't cause too many conflicts either but I will defer to the group because I am not sure what

Re: [Kicad-developers] Possible error in project loading

Hey Jeff, Oh my! This is embarrassing since git blamed me. That should indeed be ConfigSave(). It looks like a copy and past error on my part. Nice catch. Cheers, Wayne On 4/5/19 3:34 PM, Jeff Young wrote: > Hi Wayne, > > Could you take a look at lines 75:77 in prjconfig.cpp: > > // Save

Re: [Kicad-developers] [PATCH] [RFC] Exporter for Mentor Hyperlynx

Tom, On 4/5/19 12:41 PM, Wayne Stambaugh wrote: > On 4/5/19 12:24 PM, Tomasz Wlostowski wrote: >> On 05/04/2019 18:04, Wayne Stambaugh wrote: >>> Tom, >>> >>> On 4/4/19 8:16 PM, Tomasz Wlostowski wrote: >>>> Hi, >>>> >>>&g

Re: [Kicad-developers] [PATCH] [RFC] Exporter for Mentor Hyperlynx

On 4/5/19 12:24 PM, Tomasz Wlostowski wrote: > On 05/04/2019 18:04, Wayne Stambaugh wrote: >> Tom, >> >> On 4/4/19 8:16 PM, Tomasz Wlostowski wrote: >>> Hi, >>> >>> We needed to do some signal/power integrity simulations on one of our >>> Ki

Re: [Kicad-developers] [PATCH] [RFC] Exporter for Mentor Hyperlynx

Tom, On 4/4/19 8:16 PM, Tomasz Wlostowski wrote: > Hi, > > We needed to do some signal/power integrity simulations on one of our > Kicad designs and in order to do that, we needed to convert a Kicad PCB > to Hyperlynx format. Luckily, the format is simple, all text and well > documented in [1],

Re: [Kicad-developers] [PATCH] [RFC] Exporter for Mentor Hyperlynx

Tom, On 4/5/19 10:40 AM, Tomasz Wlostowski wrote: > On 05/04/2019 02:16, Tomasz Wlostowski wrote: >> Hi, >> >> We needed to do some signal/power integrity simulations on one of our >> Kicad designs and in order to do that, we needed to convert a Kicad PCB >> to Hyperlynx format. Luckily, the

Re: [Kicad-developers] Auto zoom-to-fit and the symbol editor

This seems like a perfectly acceptable solution to me. You may also want to add this option to the symbol viewer as well. I'm sure someone will request that as well. On 4/5/19 9:08 AM, John Beard wrote: > Hi Jeff, > > I think the current default is somewhat reasonable. If editing a >

Re: [Kicad-developers] "auto" policy

On 4/5/19 6:39 AM, Jeff Young wrote: > Do we have a policy on when to use auto? No but we should create one since I'm seeing it being used fairly often. > > Personally, I like it when it removes repetition.  For instance: > >     auto pin = new SCH_PIN();   I'm fine with this since the type

Re: [Kicad-developers] Merge schedule

Jeff, I can't think of any reason not to clean up the SCH_ and LIB_ Draw() routines unless I'm missing something. It might be useful to merge this to the 5.1 branch once it is proven to be stable. This will help keep merge conflicts to a minimum. Wayne On 4/5/19 6:09 AM, Jeff Young wrote: >

Re: [Kicad-developers] Printing dangling flags

It might be handy in debug builds to show the dangling state for development purposes but I don't see this being useful for users. On 4/4/2019 1:39 PM, Jon Evans wrote: > I bet it's an oversight.  Dangling flags are in the category of "live > ERC warnings" in my opinion, and should never be

Re: [Kicad-developers] Git down?

Ditto. On 4/3/2019 3:28 PM, Jon Evans wrote: > Same for me > > On Wed, Apr 3, 2019 at 3:27 PM Jeff Young > wrote: > > Is launchpad’s git instance down?  It’s refusing my connection... > ___ > Mailing list:

Re: [Kicad-developers] Bus upgrades merge

Tom, On 4/3/2019 1:34 PM, Tomasz Wlostowski wrote: > On 02/04/2019 17:27, Wayne Stambaugh wrote: >> We should always be using wxLogTrace. Using printf and cout are >> meaningless on windows and wxLogDebug means that your debugging output >> is always spewed on debug

Re: [Kicad-developers] More wxString multi-threading issues

I would be reluctant to get behind this just because of the possibility of epic string breakage on lot's of levels. If there was some way to piece meal this transition, it might be more palatable but that may prove to be very difficult. The need to use threads, is less clear. It may be far less

Re: [Kicad-developers] Bus upgrades merge

Jeff, This makes sense to me so go ahead an push this to the main repo when it's ready. Wayne On 4/2/19 11:47 AM, Jeff Young wrote: >> ... I'm assuming SCH_PIN objects will only live inside the SCH_COMPONENT >> object. > > Correct. > > Cheers, > Jeff. >

Re: [Kicad-developers] Bus upgrades merge

_PIN; we just used LIB_PIN and every time a > component needed to specify something on a per-component basis, we’d add > an array of those values indexed by pin.  Obviously after a while it > turned into a mess.) > > Cheers, > Jeff. > > >> On 2 Apr 2019, at 14:14

Re: [Kicad-developers] Bus upgrades merge

mode! > > Cheers, > > John > > [1]: > http://docs.kicad-pcb.org/doxygen/md_Documentation_development_testing.html#trace-debug > [2]: > http://docs.kicad-pcb.org/doxygen/md_Documentation_development_testing.html#advanced-configuration > > On Tue, Ap

Re: [Kicad-developers] Bus upgrades merge

t; Jon > > On Mon, Apr 1, 2019 at 7:37 AM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote: > > No problem.  I wanted to get this merged so we can get some additional > testing.  Hopefully you will be able to resolve the performance issues > so we can h

Re: [Kicad-developers] Bus upgrades merge

gt;> beginning ‘/‘.  But maybe that’s just >>>>>> because I’m calling the wrong routine. >>>>>> >>>>>> Thanks, >>>>>> Jeff. >

Re: [Kicad-developers] [PATCH] Old Stable file handling

Seth, I only see two translations (looks like French and Spanish), I'm pretty sure there were more translations than this even way back in v3. I'm not opposed to it but there is a possibility that it's incomplete. I'm surprised that there any of these board files still around. This bug was not

Re: [Kicad-developers] Bus upgrades merge

yne! Everything looks good to me. > > Glad to finally have this merged so that I can start building other > improvements on top of it. > > On Sun, Mar 31, 2019 at 9:42 PM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote: > > Jon, > > I forgot to menti

Re: [Kicad-developers] Bus upgrades merge

Jon, I forgot to mention. Please take a look and make sure I didn't muck anything up when you get a chance. Wayne On 3/31/19 9:38 PM, Wayne Stambaugh wrote: Jon, I merged your patch set into the master branch.  Thank you for all of your efforts. Cheers, Wayne On 3/31/19 7:50 PM, Jon

Re: [Kicad-developers] Bus upgrades merge

Jon, I merged your patch set into the master branch. Thank you for all of your efforts. Cheers, Wayne On 3/31/19 7:50 PM, Jon Evans wrote: Yes I just squashed the parts that dont compile on their own. On Sun, Mar 31, 2019, 19:48 Wayne Stambaugh <mailto:stambau...@gmail.com>&

Re: [Kicad-developers] Bus upgrades merge

Jon, I thought we decided to squash your patch set or did you just squash part of the patch set? I see 17 separate patches the archive you sent. Wayne On 3/31/19 7:39 PM, Jon Evans wrote: Attached! On Sun, Mar 31, 2019 at 7:28 PM Wayne Stambaugh <mailto:stambau...@gmail.com>&

Re: [Kicad-developers] 5.1 release

On 3/30/19 11:17 PM, Kevin Cozens wrote: On 2019-03-10 5:39 p.m., Adam Wolf wrote: Nick, is the docs tarball ready? That is an interesting question. Who maintains the file format doc? The only version I can find is over 2 years old. I'm writing a script to convert the files from a schematic

Re: [Kicad-developers] Bus upgrades merge

Jon, Would you please post the squashed patch to the mailing list so I can get it merged? Thanks, Wayne On 3/31/19 3:07 PM, Jon Evans wrote: I went through and squashed the offending commits and updated the PRs. -Jon On Sun, Mar 31, 2019 at 2:22 PM Wayne Stambaugh <mailto:stam

Re: [Kicad-developers] License CC-BY-SA-4.0 used in KiCad

I reverted this commit so this should resolve the Fedora build issue. On 3/31/19 12:59 PM, Carsten Schoenert wrote: > Hello Aimylios, > > Am 30.03.19 um 20:42 schrieb Aimylios: >> Hi Carsten, > > (no need to address me directly, I'm subscribed to the list) > >> your third patch breaks the

Re: [Kicad-developers] Bus upgrades merge

intended to be built on their own.  > > On Sun, Mar 31, 2019, 14:16 Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote: > > When was the code that did not build on msvc introduced?  If was early > then it might make sense to squash everything.  Otherwise, it may b

Re: [Kicad-developers] Bus upgrades merge

d <mailto:s...@hillbrand.org>> wrote: > > Am 2019-03-30 17:33, schrieb Simon Richter: > > Hi Wayne, > > > > On 30.03.19 21:30, Wayne Stambaugh wrote: > > > >> Is this the last of it?  If so, I will attempt to get this merged >

Re: [Kicad-developers] Bus upgrades merge

Is this the last of it? If so, I will attempt to get this merged tomorrow. Cheers, Wayne On 3/30/19 3:35 PM, Jon Evans wrote: > Oops! fixed. > > On Sat, Mar 30, 2019 at 3:03 PM Simon Richter > wrote: > > Hi Jon, > > On 30.03.19 19:23, Jon Evans

Re: [Kicad-developers] Zone hatch filling patch

Hey JP, On 3/30/19 10:39 AM, jp charras wrote: > Le 29/03/2019 à 14:54, Wayne Stambaugh a écrit : >> JP, >> >> On 3/27/19 4:12 PM, jp charras wrote: >>> Le 20/03/2019 à 19:27, Wayne Stambaugh a écrit : >>>> Hi JP, >>>> >>>> R

Re: [Kicad-developers] Bus upgrades merge

there are no issues before we merge it. Cheers, Wayne On 3/29/2019 11:54 PM, Jon Evans wrote: > Has anyone else been doing any testing?  I have resolved some issues > that JP found, but haven't heard from anyone else. > > -Jon > > On Fri, Mar 22, 2019 at 5:08 PM Wayne Stambaug

Re: [Kicad-developers] Build error.

help for standalone utils headers though, unless, like this > one, they just happen to also come first in the list. > > Cheers, > > John > > On Fri, Mar 29, 2019 at 1:01 PM Wayne Stambaugh wrote: >> >> Hey John, >> >> Thanks for the quick fix. It could

Re: [Kicad-developers] Zone hatch filling patch

JP, On 3/27/19 4:12 PM, jp charras wrote: > Le 20/03/2019 à 19:27, Wayne Stambaugh a écrit : >> Hi JP, >> >> Rather than pollute the bug report[1] with feedback about your zone >> hatch filling patch, I moved the conversation to the mailing list. If >> anyone el

Re: [Kicad-developers] Build error.

orrect. Perhaps a header has a sneaky type > alias somewhere. > > Cheers, > > John > > On Fri, Mar 29, 2019 at 12:30 PM Wayne Stambaugh wrote: >> >> Commit ad76ebd8 broke builds when compiling with clang. >> >> home/wayne/src/kicad-trunk/qa/unit_test_util

[Kicad-developers] Build error.

Commit ad76ebd8 broke builds when compiling with clang. home/wayne/src/kicad-trunk/qa/unit_test_utils/include/unit_test_utils/unit_test_utils.h:121:24: error: unknown type name 'nullptr_t'; did you mean 'std::nullptr_t'? struct print_log_value ^

Re: [Kicad-developers] Should SCH_COMPONENT::m_convert default to 1?

> examination of the > code, it looks like the m_convert parameter of SCH_COMPONENT > should default to > 1.  It is initialized this way in all places except for the > Eagle conversion, > which is probably why this bug was triggered. &

Re: [Kicad-developers] Kicad Presentation

Hello Carlo, Thank you for giving a KiCad talk. It really does help spread the word. I hope you had a good turn out to see your talk. Cheers, Wayne On 3/27/19 5:43 PM, Carlo Maragno wrote: > Hi Everyone, > > I gave a presentation on Kicad and it's ecosystem. The event was a > student

Re: [Kicad-developers] License CC-BY-SA-4.0 used in KiCad

Carsten, On 3/27/2019 2:33 PM, Carsten Schoenert wrote: > Am 27.03.19 um 18:09 schrieb Wayne Stambaugh: >> Carsten, >> >> I'm still getting the following git error when applying patch 1: >> >> Applying: Adding license information for demo files >> Usin

Re: [Kicad-developers] License CC-BY-SA-4.0 used in KiCad

--skip" instead. To restore the original branch and stop patching, run "git am --abort". Any ideas? Cheers, Wayne On 3/27/2019 12:36 PM, Carsten Schoenert wrote: > Hello Wayne, > > Am 27.03.19 um 16:34 schrieb Wayne Stambaugh: >> Hey Carsten, >> >> I trie

Re: [Kicad-developers] [eeschema] Names/descriptions for units

as planning to just use the existing field functionality. >> >> If you want to bake it into the format instead, I'm 100% okay with that, >> but I don't think it's necessary. I'll look into implementing the UI >> functionality and defer to you on how/where to store the da

Re: [Kicad-developers] License CC-BY-SA-4.0 used in KiCad

Hey Carsten, I tried merging your patches and patch 1 does not merge cleanly. Would you please rebase patch 1 so I can get it merged? Thanks, Wayne On 3/8/2019 1:13 PM, Carsten Schoenert wrote: > Am 08.03.19 um 19:01 schrieb Wayne Stambaugh: >> This makes sense to me. > >

Re: [Kicad-developers] [PATCH] Option to not render 3D models for footprints

> Or a shield that covers some other parts. Might be useful to just hide > this alone. > > On 25/03/19 19:46, Jeff Young wrote: > > Multiple models is an existing feature (for building up parts).  > There’s just no individual control over visibility. &

Re: [Kicad-developers] [PATCH] Add preferences dialog hotkey

Hi Michael, Sorry it took so long. I'm going back through my list of outstanding patches and I ran across this one. Obviously this patch no longer applies cleanly by if you are still interested in getting this merged, please rebase it and I will merge it. Thanks, Wayne On 10/16/2018 5:24 PM,

Re: [Kicad-developers] Should SCH_COMPONENT::m_convert default to 1?

n the forum thread but > perhaps it fixed it the wrong way. > > -Jon > > On Wed, Mar 27, 2019 at 8:35 AM Wayne Stambaugh <mailto:stambau...@gmail.com>> wrote: > > Oops. > > On 3/27/2019 8:30 AM, Wayne Stambaugh wrote: > > Jon, > > &g

<    3   4   5   6   7   8   9   10   11   12   >