[Kicad-developers] Moving developer mailing list
Hi Folks- We're not really sure who will receive this message. And that is the problem. Launchpad's e-mail list service has become increasingly unreliable. In the past month, multiple messages have not been delivered to the lead developer team members, leading to a lack of communication. This has happened a few times over the past two years. While each time is eventually resolved, we have no control over its resolution and no visibility on when it happens. For this reason, we are moving to a new list server. You can subscribe to the new list by e-mailing devlist+subscr...@kicad.org For more details on the list, please see the KiCad Project blog post at https://www.kicad.org/blog/2022/07/New-Developer-Mailing-List/ After this message, the launchpad e-mail list will be shut down. Thank you all for your continued interest in KiCad, Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Should I start a new bug or is the reopened one suitable?
You commented in that bug report with the details. Usually, commenting in open reports with examples that show the issue is sufficient. If the issue were already closed, then opening a new report and referencing the old one is preferred. Seth On Fri, May 27, 2022 at 10:48 AM Steven A. Falco wrote: > I recently reopened an issue [1] because I found an old schematic that > could be opened properly by 5.1, but which gave "missing symbol" boxes when > opened with 6.0 and 6.99. > > However, while the effect is the same, the root cause may be different, so > maybe reopening the bug was the wrong approach. Should I instead start a > new bug for this? > > Looking at the .sch files, the original has entries like: > > $Comp > L RES-10M-5%-1/4W-CF R5 > ... > $EndComp > > But after opening and saving the schematic with 5.1, this component has > changed to: > > $Comp > L e202var-vlf-radio-receiver-rescue:RES-10M-5%-1_4W-CF R5 > ... > $EndComp > > At that point, 6.0 and 6.99 can correctly open the newly saved schematic. > > Thus, it looks like 6.0 and 6.99 have lost the ability to deal with a "/" > in a component name. I don't know if any other special characters also > fall into this category. > > Steve > > [1] https://gitlab.com/kicad/code/kicad/-/issues/11563 > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] V7 Python API Development
Hi Oliver- I'm still working on backend stuff to synchronize eeschema/pcbnew. Is there something in particular that you'd like to work on? Maybe I can spin off a section for you. Seth On Fri, May 20, 2022 at 5:55 AM Oliver Holt wrote: > Hello all, > > I have seen a few posts regarding progress on implementing the new Python > API (moving away from SWIG) on the forum and here on the mailing list but I > cannot find anything formal about it on Gitlab. It sounds like there is > some kind of, currently private, specification and there is (or at least > was in December) intent to have it ready to include in v7.0 so I presume > the necessary dev work is ongoing? > > Please see: > https://lists.launchpad.net/kicad-developers/msg44066.html > https://forum.kicad.info/t/python-api-development-discussion/23604/6 > https://forum.kicad.info/t/python-api-status-in-v6/31929/ > > I am interested in getting involved in development in this area, in Python > and/or C++, I just need an entry point. Can anyone point me in the > direction of relevant issues, branches, documentation etc? > > Thanks, > > Oliver > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Files drag & drop.
Hello Fabrice, Thank you for handling the initial issue. Since the schematic editor and pcb editor will only work with project-based files unless opened standalone, I would suggest the following: - Gerber files can be D handled to either the Gerber Viewer editor window or the project manager window - All other file types can only be D handled in a standalone editor window. Best, Seth On Mon, May 16, 2022 at 9:20 AM Lu Lu wrote: > Good evening, > > Issue 8146, requesting the feature allowing drag and drop of project > files, is closed. > > Jon Evans wrote kicad should enable D to other editors, especially to > Gerbview editor. > > I think there are three ways to do this: > - D of a file to the kicad manager window and opening the associated > editor ; > - D of a file edited in an open editor ; > - both ways. > > Which should be implemented? > > Fabrice. > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Unable to build on Ubuntu 18.04 for 6.0 branch
Hi Gabriel- The support periods listed on the kicad.org website are for the free builds provided and maintained at no cost to the end user. We set limits here to best utilize our available developer resources. Maintaining software for out of date operating systems is time consuming and difficult. Companies that require extended support periods or use unsupported operating systems for their business operations should consider purchasing that support [1]. This differentiation both maximizes the feature development for all KiCad users while providing a cost-efficient solution for businesses looking to avoid "tremendously difficult and costly" upgrades. All of that said, as Wayne notes, we should have corrected the INSTALL.txt and CMakeList.txt files to the proper Boost version when we updated the code. Seth [1] https://www.kicad.org/help/professional-support/ On Tue, May 10, 2022 at 8:26 AM Gabriel Staples, ElectricRCAircraftGuy.com < erca...@gmail.com> wrote: > Also, > > If you're wondering how prevalent Ubuntu is in industry, I can't say > exactly, but I'll say this: for software development on self-driving cars, > both of the last 2 companies I've worked at, each with around 2000 > employees, have used Ubuntu as their primary workstations and build > systems. The first kept Ubuntu 14.04 until the year 2019, several months > *after* the 5 year LTS support was up, at which point they upgraded to > Ubuntu 18.04, which was **tremendously difficult and costly**, and the > latter gave me an Ubuntu 18.04 machine in January 2020, and it's still > 18.04 today, and they won't upgrade it. A lot of large and influential > companies have substantial reliance on Ubuntu releases for long periods of > time. > > Thanks! > > Gabriel Staples > > > > > On Tue, May 10, 2022 at 8:22 AM Gabriel Staples, ElectricRCAircraftGuy.com > wrote: > >> Seth, >> >> You/KiCad might consider supporting Ubuntu for the full 5 year duration >> that LTS releases are supported by Ubuntu. On my home machines, for >> instance, I run Ubuntu 20.04 right now. On my work machines, however, I run >> Ubuntu 18.04 right now because the cost of upgrading a distro is so >> significant they only do it when the Long Term Support period of 5 years is >> over. I shouldn't manually upgrade my own work machine if I wanted to >> because it must remain compatible with my work's build systems and other >> software. I think many companies operate this way. If you want to get KiCad >> to be used by more companies, which I would like to see myself, I think >> KiCad will need to support Ubuntu for the full 5 years of the LTS term or >> else it may automatically be ruled out as a potential candidate as >> companies evaluate software to use and support. >> >> Thanks! >> >> Gabriel Staples >> >> >> >> >> On Mon, May 9, 2022 at 8:53 AM Seth Hillbrand wrote: >> >>> Hi Wayne, >>> >>> From the page you linked, 18.04 is not a supported system and has never >>> been supported for v6. We had decided some time ago that we would support >>> Ubuntu LTS versions for 1 year after the release of the next LTS [1]. >>> >>> Jean-Samuel, you may be able to use the mhier PPA[2] as the source for >>> newer Boost versions that will allow KiCad on older Ubuntus. >>> >>> -Seth >>> >>> [1] https://lists.launchpad.net/kicad-developers/msg43255.html >>> [2] >>> https://launchpad.net/~mhier/+archive/ubuntu/libboost-latest/+packages >>> >>> On Mon, May 9, 2022 at 6:06 AM Wayne Stambaugh >>> wrote: >>> >>>> It looks like someone back ported some random number generator fixes >>>> from master that are not available in boost 1.56 which is the minimum >>>> version in the 6.0 branch. We should address this since 18.04 LTS is a >>>> supported system[1]. >>>> >>>> >>>> [1]:https://www.kicad.org/help/system-requirements/ >>>> >>>> On 5/9/22 4:05 AM, Jean-Samuel Reynaud wrote: >>>> > Hi, >>>> > >>>> > As I see, since one of those commits: >>>> > 891c919c239223ef601284a8f166d0f229f6b030 >>>> > 0ea7dabc1271dbc77b8d5764e4eecbeba85903d6 >>>> > e1cd74dd78031b002737a79ddffcf3489d74105c >>>> > 4d8297a1f6f18d59cb38361b88a959d7af062480 >>>> > >>>> > KiCad is unable to build on Ubuntu 18.04. I guess it's a boost version >>>> > issue (Boost is 1.65.1 on Ubuntu 18.04). >>>> > The build error: >>>> > kicad/common/kiid.cpp:50:73
Re: [Kicad-developers] Unable to build on Ubuntu 18.04 for 6.0 branch
Hi Wayne, >From the page you linked, 18.04 is not a supported system and has never been supported for v6. We had decided some time ago that we would support Ubuntu LTS versions for 1 year after the release of the next LTS [1]. Jean-Samuel, you may be able to use the mhier PPA[2] as the source for newer Boost versions that will allow KiCad on older Ubuntus. -Seth [1] https://lists.launchpad.net/kicad-developers/msg43255.html [2] https://launchpad.net/~mhier/+archive/ubuntu/libboost-latest/+packages On Mon, May 9, 2022 at 6:06 AM Wayne Stambaugh wrote: > It looks like someone back ported some random number generator fixes > from master that are not available in boost 1.56 which is the minimum > version in the 6.0 branch. We should address this since 18.04 LTS is a > supported system[1]. > > > [1]:https://www.kicad.org/help/system-requirements/ > > On 5/9/22 4:05 AM, Jean-Samuel Reynaud wrote: > > Hi, > > > > As I see, since one of those commits: > > 891c919c239223ef601284a8f166d0f229f6b030 > > 0ea7dabc1271dbc77b8d5764e4eecbeba85903d6 > > e1cd74dd78031b002737a79ddffcf3489d74105c > > 4d8297a1f6f18d59cb38361b88a959d7af062480 > > > > KiCad is unable to build on Ubuntu 18.04. I guess it's a boost version > > issue (Boost is 1.65.1 on Ubuntu 18.04). > > The build error: > > kicad/common/kiid.cpp:50:73: required from here > > /usr/include/boost/random/detail/seed_impl.hpp:269:9: error: ‘class > > boost::uuids::detail::seed_rng’ has no member named ‘generate’ > > seq.generate([0], [0] + ((w+31)/32) * n); > > ^~~~ > > > > > > You can take a look as the build output at > > > https://launchpadlibrarian.net/600354670/buildlog_ubuntu-bionic-amd64.kicad_6.0.0+nightly-202205081117+43b8adad1a~116~ubuntu18.04.1_BUILDING.txt.gz > > (large log, error message near the end ;) > > > > > > Is this version of Ubuntu is still supported for 6.0 branch ? (for me > > yes since the Ubuntu support is up to April 2023)... > > Note that it affect version 6.0.5 (6.0.4 was built correctly) > > > > Regards, > > > > ___ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : kicad-developers@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Two bugs reported on the Fedora bugzilla
Ah, thanks! Looks like that was fixed in master but didn't get cherry-picked. The fix is in the v6 branch now. Seth On Fri, May 6, 2022 at 11:08 AM Ian McInerney wrote: > The second bug appears to be an assertion due to an invalid vector access. > > The stack trace is below. > > Truncated backtrace: > Thread no. 1 (10 frames) > #2 std::__replacement_assert at > /usr/include/c++/11/x86_64-redhat-linux/bits/c++config.h:2660 > #3 std::vector, std::allocator > >::operator[] > at /usr/include/c++/11/bits/stl_vector.h:1043 > #5 ZONE::HatchBorder at > /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/zone.cpp:1031 > #6 ZONE::SetBorderDisplayStyle at > /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/zone.cpp:882 > #7 PCB_PARSER::parseZONE at > /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_parser.cpp:5437 > #8 PCB_PARSER::parseFOOTPRINT_unchecked at > /usr/include/c++/11/bits/unique_ptr.h:173 > #9 PCB_PARSER::parseFOOTPRINT at > /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_parser.cpp:3211 > #10 PCB_PARSER::Parse at /usr/include/c++/11/bits/unique_ptr.h:185 > #11 FP_CACHE::Load at > /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_plugin.cpp:274 > #12 PCB_PLUGIN::FootprintEnumerate at > /usr/src/debug/kicad-6.0.4-1.fc34.x86_64/pcbnew/plugins/kicad/pcb_plugin.cpp:2390 > > > This is trying to read the > `/usr/share/kicad/footprints//RF_Module.pretty/MOD-nRF8001.kicad_mod` file > provided in the standard footprint library (and apparently there is an > extra slash entering the path somewhere, but that is extraneous to this). > What seems to be happening is that during the parsing, it is finding a > hatched zone, but the hatch border has an empty pointbuffer, which then > causes the stdlib assert to fire when it is accessed at any index. > > -Ian > > On Fri, May 6, 2022 at 7:00 PM Seth Hillbrand wrote: > >> Hi Steven- >> >> The second bug is locked down. We can't see it without proper access >> credentials. >> >> Seth >> >> On Fri, May 6, 2022 at 6:45 AM Steven A. Falco >> wrote: >> >>> There are two SIGABRT bugs reported on Fedora: >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=2079984 >>> >>> https://bugzilla.redhat.com/show_bug.cgi?id=2082394 >>> >>> The first bug was closed because it was not able to be reproduced. The >>> second one has apparently happened to the reporter several times, but again >>> I don't know if it is reproducible on demand. >>> >>> Do either of these ring a bell with anyone? >>> >>> Steve >>> >>> _______ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 >> Long Beach, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Two bugs reported on the Fedora bugzilla
Hi Steven- The second bug is locked down. We can't see it without proper access credentials. Seth On Fri, May 6, 2022 at 6:45 AM Steven A. Falco wrote: > There are two SIGABRT bugs reported on Fedora: > > https://bugzilla.redhat.com/show_bug.cgi?id=2079984 > > https://bugzilla.redhat.com/show_bug.cgi?id=2082394 > > The first bug was closed because it was not able to be reproduced. The > second one has apparently happened to the reporter several times, but again > I don't know if it is reproducible on demand. > > Do either of these ring a bell with anyone? > > Steve > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] List testing messages
Hi Folks- A quick update on this issue. Launchpad thinks that they have resolved the root cause [1], so this message is intended as a test of their new system configuration. Seth [1] https://bugs.launchpad.net/launchpad/+bug/1970448 On Tue, Apr 26, 2022 at 1:01 PM Seth Hillbrand wrote: > Hi Folks- > > You may have received a bounced message over the list to verify a new > email address. You can ignore the message. > > We've had a few issues over the past year with Launchpad losing/not > delivering some messages. We've reported the issue to Launchpad each time. > > This may be due to Launchpad messages failing DKIM/DMARC checks or it may > be due to other issues. We don't really have much visibility into the root > cause. > > At this point, we are exploring alternate list options. We may not need > to migrate to a different list but we want to make sure that we are > prepared should the need arise. > > Unfortunately, our primary means of communication is via this mailing list > and, with messages not being delivered, it is unclear if updates will get > through. In the event that we do change list servers, we'll post the > announcement to this list multiple times as well as to the forum and > discord servers. > > Sorry for the technical difficulties. > -Seth > > -- > [image: KiCad Services Corporation Logo] > Seth Hillbrand > *Lead Developer* > +1-530-302-5483 > Long Beach, CA > www.kipro-pcb.comi...@kipro-pcb.com > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] List testing messages
Hi Folks- You may have received a bounced message over the list to verify a new email address. You can ignore the message. We've had a few issues over the past year with Launchpad losing/not delivering some messages. We've reported the issue to Launchpad each time. This may be due to Launchpad messages failing DKIM/DMARC checks or it may be due to other issues. We don't really have much visibility into the root cause. At this point, we are exploring alternate list options. We may not need to migrate to a different list but we want to make sure that we are prepared should the need arise. Unfortunately, our primary means of communication is via this mailing list and, with messages not being delivered, it is unclear if updates will get through. In the event that we do change list servers, we'll post the announcement to this list multiple times as well as to the forum and discord servers. Sorry for the technical difficulties. -Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Automatic label rotation
Hello Miklos- Thank you for the useful suggestion. Please open a merge request on GitLab. This will help us to more easily review the changes you are proposing. Best, Seth On Sat, Apr 16, 2022 at 7:07 AM Miklos Marton wrote: > Dear Kicad developers! > > I made a feature which allows automatic alignment of the hierarchial and > global labels depending on where did they got placed. > I would like to have some discussion about it before I submit a MR. > > The code lives here: > > https://gitlab.com/martonmiklos/kicad/-/tree/add_label_rotate > > You could find a short video about what it does: > > https://www.youtube.com/watch?v=CGyEttFy7PM > > At the moment it is limited to hierarchial and global labels, and only the > following connections: > >- Wires >- Symbol pins >- Bus entries > > Are there any other label types where this auto alignment feature would > make sense? > > Are there any connection points where it could be useful (other than than > what is implemented now)? > > I found two other possible item types in the code: SCH_SHEET_PIN_T, > SCH_PIN_T. > > As for SCH_SHEET_PIN_T I added hierarchial sheet symbols and added the > hierarchual pins to them, > however if I place a global label right into the sheet imported pins they > does not get connected automatically: > if I move away the placed label no wires got added (like they do when I > place a label on a symbol's pin). > > About the SCH_PIN_T I thought that the power taps are fall into this > category, > but it looks like that they are not (simply Symbol pins at least for the > GND). > > I have wondered if the temporary label alignment change should be > visualized when the cursor get moved above a placement point, > however it might be just waste of computational time. > > -- > Best regards, > Miklos Marton > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Icon for 3D Mouse center of rotation
those of >> 3Dconnexion GmbH. >> 3Dconnexion GmbH processes and stores for commercial purposes your >> personal data, collected upon your consent, in accordance with its privacy >> policy available at https://www.3dconnexion.eu/privacy.html, which has >> been drafted in accordance with Regulation (EU) no. 679/2016 and all >> applicable local data protection laws and regulations of the countries >> where the company operates. To revoke your consent or exercise all your >> rights with regards to personal data, please contact us at >> priv...@3dconnexion.com. >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] [abrt] kicad: wxDataViewCtrlInternal::BuildBranch(wxGtkTreeModelNode*)(): kicad killed by SIGSEGV
Hi Steve- I think that this is related to https://gitlab.com/kicad/code/kicad/-/issues/7422 (and the other bugs near it). This is a particularly problematic section of wx/gtk interaction. I believe that the way this widget works has been improved in wx3.1, so once the new wxWidgets is available for Fedora, the issue should be resolved. If there are steps to reproduce, we can maybe work around it as we have with the similar issues. Seth On Fri, Mar 25, 2022 at 6:36 AM Steven A. Falco wrote: > A segfault has been reported in Fedora, but the reporter says it is not > reproducible. Below is a link to the bug. > > https://bugzilla.redhat.com/show_bug.cgi?id=2068449 > > Please let me know if this is a known issue, or if there is anything > further that we can do about it, given that it is not reproducible. > > Steve > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Fedora and major version changes
Thanks for pushing this through Steve! -Seth On Mon, Feb 28, 2022 at 1:36 PM Steven A. Falco wrote: > I'm not sure how many folks on this list care about what follows, but for > those who do... > > KiCad has been granted an exception to the Fedora "major update policy". > The exception will only be used in the case of critical bugs / security > issues. > > Consequently, I'm currently building 6.0.2 for F34 and F35, to address the > recent CVE's. The builds should complete tonight, but won't go live for a > week, given the Fedora testing policy. > > The most up-to-date KiCad releases will continue to be available via Copr > for those who want them. > > Steve > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] CVE announcement
Hi Folks- On February 1 and 2, we received reports from Cisco Talos of vulnerabilities in the text handling used by GerbView to parse gerber and drill files. We addressed these reports immediately and scheduled a release for version 6.0.2 to get the fixes out to our user base as soon as possible. There are 4 CVE reports [1][2][3][4]. Each presents a potential buffer overflow attack from a specially-crafted Gerber file. Our fixes removed the use of static-sized buffers, preventing this type of attack in the future. We coordinated with Cisco Talos on the release of the CVEs, following the full release of KiCad 6.0.2. All users are encouraged to upgrade their KiCad installations to avoid this potential issue. A summary of the timeline is provided by KiCad [5] and a full writeup of the vulnerability is published by Cisco Talos[6]. The KiCad team takes security vulnerabilities seriously and will address them in a timely manner. To report security issues, please file an issue in the KiCad bug tracker and mark it "Confidential". We will reach out to coordinate vulnerability disclosure timelines. Seth [1] https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23946 [2] https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23947 [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23803 [4] https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23804 [5] https://www.kicad.org/blog/2022/02/KiCad-6.0.2-Release/ [6] https://talosintelligence.com/vulnerability_reports/TALOS-2022-1460 -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] CVE-2022-23803, CVE-2022-23804, CVE-2022-23946, CVE-2022-23947
Distributions that would like to release a patched version of 5.1, 5.0 or 4.0 can cherry-pick the patch series. They should apply cleanly. Seth On Wed, Feb 16, 2022 at 9:16 AM Steven A. Falco wrote: > One additional question - I know that 5.1.12 was the last planned release > in the 5.x series, and that 5.1.12 has the vulnerability. Currently, > because of Fedora policy, both F34 and F35 still ship 5.1.12. > > I'll ask on the Fedora list if this event qualifies as an exception to the > policy, but if not, how involved would it be to patch 5.1.12, or perhaps to > spin a 5.1.13 just to fix this issue? > > Steve > > On 2/16/22 11:49 AM, Steven A. Falco wrote: > > Excellent! I'll note that on the Fedora bugs. > > > > Thanks, > > Steve > > > > On 2/16/22 09:44 AM, Ian McInerney wrote: > >> All 4 CVEs were fixed in the 6.0.2 release and the release announcement > was updated last night to say this (to coincide with the public disclosure > that happened today). There will be another email on the developer list > later today with more details. > >> > >> -Ian > >> > >> On Wed, Feb 16, 2022 at 2:18 PM Steven A. Falco <mailto:stevenfa...@gmail.com>> wrote: > >> > >> I've just received a large number of bugs against KiCad, supposedly > due to CVE-2022-23803, CVE-2022-23804, CVE-2022-23946, CVE-2022-23947. > >> > >> I don't have time to look into them, but I wanted to make them > known. There are apparently also bugs for this on the gentoo site - here > is one: https://bugs.gentoo.org/833426 <https://bugs.gentoo.org/833426> > >> > >> Here are the Fedora bugs: > >> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054956 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054956> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054957 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054957> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054959 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054959> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054960 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054960> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054955 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054955> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054973 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054973> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054974 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054974> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054979 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054979> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054980 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054980> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054958 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054958> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054972 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054972> > >> https://bugzilla.redhat.com/show_bug.cgi?id=2054978 < > https://bugzilla.redhat.com/show_bug.cgi?id=2054978> > >> > >> ___ > >> Mailing list: https://launchpad.net/~kicad-developers < > https://launchpad.net/~kicad-developers> > >> Post to : kicad-developers@lists.launchpad.net kicad-developers@lists.launchpad.net> > >> Unsubscribe : https://launchpad.net/~kicad-developers < > https://launchpad.net/~kicad-developers> > >> More help : https://help.launchpad.net/ListHelp < > https://help.launchpad.net/ListHelp> > >> > > > > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 6.0.2 tagged.
OK. The link should be updated now. Let me know if there are any issues. Seth On Fri, Feb 11, 2022 at 10:06 AM Seth Hillbrand wrote: > Thanks for the heads up guys. I'll re-package now > > On Fri, Feb 11, 2022 at 7:24 AM Nick Østergaard wrote: > >> You need to use the package target when buildign the doc tar >> >> On Fri, 11 Feb 2022, 16.15 Jon Evans, wrote: >> >>> @seth - I think the docs need to be re-packed in the manner Christoph >>> says, IIRC that is a requirement for the Mac packaging. >>> >>> On Fri, Feb 11, 2022 at 10:09 AM Christoph Moench-Tegeder < >>> c...@burggraben.net> wrote: >>> >>>> Hi, >>>> >>>> ## Wayne Stambaugh (stambau...@gmail.com): >>>> >>>> > All of the repos have been tagged for 6.0.2 and the documentation >>>> > archive can be download from >>>> > https://kicad-downloads.s3.cern.ch/docs/kicad-doc-6.0.2.tar.gz. >>>> >>>> That docs archive... Previously (until and including 6.0.1), that >>>> archive had been breated with kicad-doc-$version as the top level >>>> directory, but with 6.0.2 the top level directory is "share". >>>> In practical terms: >>>> >>>> cmt@elch:Sources$ tar tzf kicad-doc-6.0.1.tar.gz | sort | head -5 >>>> kicad-doc-6.0.1/share/ >>>> kicad-doc-6.0.1/share/doc/ >>>> kicad-doc-6.0.1/share/doc/kicad/ >>>> kicad-doc-6.0.1/share/doc/kicad/help/ >>>> kicad-doc-6.0.1/share/doc/kicad/help/ca/ >>>> >>>> cmt@elch:Sources$ tar tzf kicad-doc-6.0.2.tar.gz | sort | head -5 >>>> share/ >>>> share/doc/ >>>> share/doc/kicad/ >>>> share/doc/kicad/help/ >>>> share/doc/kicad/help/ca/ >>>> >>>> Is that meant to stay this way in 6.0.2? It's easy to handle in >>>> packaging >>>> either way round, but if you plan to reroll the tarball, I'll wait for >>>> the new package (and the new checksums) before pushing. >>>> >>>> Regards, >>>> Christoph >>>> >>>> -- >>>> Spare Space >>>> >>>> _______ >>>> Mailing list: https://launchpad.net/~kicad-developers >>>> Post to : kicad-developers@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~kicad-developers >>>> More help : https://help.launchpad.net/ListHelp >>>> >>> ___ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> > > -- > [image: KiCad Services Corporation Logo] > Seth Hillbrand > *Lead Developer* > +1-530-302-5483 > Long Beach, CA > www.kipro-pcb.comi...@kipro-pcb.com > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 6.0.2 tagged.
Thanks for the heads up guys. I'll re-package now On Fri, Feb 11, 2022 at 7:24 AM Nick Østergaard wrote: > You need to use the package target when buildign the doc tar > > On Fri, 11 Feb 2022, 16.15 Jon Evans, wrote: > >> @seth - I think the docs need to be re-packed in the manner Christoph >> says, IIRC that is a requirement for the Mac packaging. >> >> On Fri, Feb 11, 2022 at 10:09 AM Christoph Moench-Tegeder < >> c...@burggraben.net> wrote: >> >>> Hi, >>> >>> ## Wayne Stambaugh (stambau...@gmail.com): >>> >>> > All of the repos have been tagged for 6.0.2 and the documentation >>> > archive can be download from >>> > https://kicad-downloads.s3.cern.ch/docs/kicad-doc-6.0.2.tar.gz. >>> >>> That docs archive... Previously (until and including 6.0.1), that >>> archive had been breated with kicad-doc-$version as the top level >>> directory, but with 6.0.2 the top level directory is "share". >>> In practical terms: >>> >>> cmt@elch:Sources$ tar tzf kicad-doc-6.0.1.tar.gz | sort | head -5 >>> kicad-doc-6.0.1/share/ >>> kicad-doc-6.0.1/share/doc/ >>> kicad-doc-6.0.1/share/doc/kicad/ >>> kicad-doc-6.0.1/share/doc/kicad/help/ >>> kicad-doc-6.0.1/share/doc/kicad/help/ca/ >>> >>> cmt@elch:Sources$ tar tzf kicad-doc-6.0.2.tar.gz | sort | head -5 >>> share/ >>> share/doc/ >>> share/doc/kicad/ >>> share/doc/kicad/help/ >>> share/doc/kicad/help/ca/ >>> >>> Is that meant to stay this way in 6.0.2? It's easy to handle in packaging >>> either way round, but if you plan to reroll the tarball, I'll wait for >>> the new package (and the new checksums) before pushing. >>> >>> Regards, >>> Christoph >>> >>> -- >>> Spare Space >>> >>> ___ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Possible build failure using gcc 12
gt;&
> std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::operator=(const
> std::__cxx11::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char;
> _Traits = std::char_traits; _Alloc = std::allocator]'
>801 | operator=(const basic_string& __str)
>| ^~~~
> /usr/include/c++/12/bits/basic_string.h:842:7: note: candidate:
> 'std::__cxx11::basic_string<_CharT, _Traits, _Alloc>&
> std::__cxx11::basic_string<_CharT, _Traits,
> _Alloc>::operator=(std::__cxx11::basic_string<_CharT, _Traits, _Alloc>&&)
> [with _CharT = char; _Traits = std::char_traits; _Alloc =
> std::allocator]'
>842 | operator=(basic_string&& __str)
>| ^~~~
> gmake[2]: ***
> [thirdparty/json_schema_validator/CMakeFiles/nlohmann_json_schema_validator.dir/build.make:107:
> thirdparty/json_schema_validator/CMakeFiles/nlohmann_json_schema_validator.dir/json-validator.cpp.o]
> Error 1
> gmake[2]: Leaving directory
> '/builddir/build/BUILD/kicad-826154d666cf192a7123005bf565168fd447fd86/redhat-linux-build'
> gmake[1]: *** [CMakeFiles/Makefile2:2464:
> thirdparty/json_schema_validator/CMakeFiles/nlohmann_json_schema_validator.dir/all]
> Error 2
> gmake[1]: *** Waiting for unfinished jobs
> gmake[2]: Leaving directory
> '/builddir/build/BUILD/kicad-826154d666cf192a7123005bf565168fd447fd86/redhat-linux-build'
> [ 2%] Built target metadata
> gmake[1]: Leaving directory
> '/builddir/build/BUILD/kicad-826154d666cf192a7123005bf565168fd447fd86/redhat-linux-build'
> gmake: *** [Makefile:169: all] Error 2
> error: Bad exit status from /var/tmp/rpm-tmp.BSrNqc (%build)
> RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.BSrNqc (%build)
> Child return code was: 1
> EXCEPTION: [Error()]
> Traceback (most recent call last):
>File "/usr/lib/python3.9/site-packages/mockbuild/trace_decorator.py",
> line 93, in trace
> result = func(*args, **kw)
>File "/usr/lib/python3.9/site-packages/mockbuild/util.py", line 600, in
> do_with_status
> raise exception.Error("Command failed: \n # %s\n%s" % (command,
> output), child.returncode)
> mockbuild.exception.Error: Command failed:
> # /usr/bin/systemd-nspawn -q -M cb1aaede17484c84bcb849188ee71bce -D
> /var/lib/mock/fedora-rawhide-x86_64-1642529229.077379/root -a -u mockbuild
> --capability=cap_ipc_lock --rlimit=RLIMIT_NOFILE=10240
> --capability=cap_ipc_lock --bind=/tmp/mock-resolv.bl3q0m6l:/etc/resolv.conf
> --bind=/dev/btrfs-control --bind=/dev/loop-control --bind=/dev/loop0
> --bind=/dev/loop1 --bind=/dev/loop2 --bind=/dev/loop3 --bind=/dev/loop4
> --bind=/dev/loop5 --bind=/dev/loop6 --bind=/dev/loop7 --bind=/dev/loop8
> --bind=/dev/loop9 --bind=/dev/loop10 --bind=/dev/loop11 --console=pipe
> --setenv=TERM=vt100 --setenv=SHELL=/bin/bash --setenv=HOME=/builddir
> --setenv=HOSTNAME=mock --setenv=PATH=/usr/bin:/bin:/usr/sbin:/sbin
> --setenv=PROMPT_COMMAND=printf "\033]0;\007"
> --setenv=PS1= \s-\v\$ --setenv=LANG=C.UTF-8 --resolv-conf=off
> bash --login -c /usr/bin/rpmbuild -bb --target x86_64 --nodeps
> /builddir/build/SPECS/kicad-nightly.spec
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Was the initial graphics mode screen removed?
On Tue, Jan 11, 2022 at 12:48 PM Steven A. Falco wrote: > On 1/11/22 03:24 PM, Seth Hillbrand wrote: > > We will not directly disable running in a VM. > > > > Our stance is that if there are issues running KiCad in a VM, they > should be reported to the maker of the VM, not KiCad. > > I'm going to have to disagree with that stance a little, Seth. The > initial bug report https://gitlab.com/kicad/code/kicad/-/issues/8944 was > from a Virtualbox user. Then I saw the problem using the native Linux > KVM. Two different VM implementations. And I think the root cause was a > KiCad bug where the code didn't properly test for > GLX_EXT_swap_control_tear. So reporting to either of those VM makers would > not have been effective, in this case. > Root cause was Mesa/X11 reporting that it was able to handle a call to GLX_EXT_swap_control_tear. And then crashing when that call was made. The "fix" was to test for a Mesa driver and then prevent it from calling the adaptive sync. I stand by the statement that this is a bug in other programs (in this case, the Mesa driver used by the VM softwares. KiCad can work around this issue (and all of the other fallback issues as well). But then, that is where developer time goes instead of into developing new schematic and layout features that will be of use to our whole userbase. This is why we will not be focussing on supporting VMs or fallback graphics in the future. Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Was the initial graphics mode screen removed?
acts won't know >>> what to do about them, and may give up. >>> >>> Steve >>> >>> >>> >>> >>> >>> ___ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Was the initial graphics mode screen removed?
Hi Steve- Please open an issue with the details of your machines that crash when trying to use accelerated graphics. We thought that we had addressed all or almost all of these cases. Our current plan is to shift our backend graphics away from the OpenGL/Cairo engines and use a third-party library like libbgfx. This may remove any option for Cairo rendering in the future, so it'll be good to work out the kinks. And for the peanut gallery: of course we check libraries and query features before using them. The segfaults happen when libraries return values that they don't actually support. Mesa/X11 is a big culprit here on Linux and older bulit-in intel drivers on Windows do the same. The way we do better is to get detailed system reports when segfaults happen. If folks just sit on these issues because fallback works for them, then we'll never fix them. Seth On Mon, Jan 10, 2022 at 8:55 PM Steven A. Falco wrote: > In the past, when running eeschema or pcbnew for the first time, it would > ask if I wanted to try accelerated graphics. That no longer seems to be > the case - I don't get that dialog. > > I don't know if the dialog was intentionally removed or if it is a bug, > but I think it is an issue either way, because the default is now > accelerated graphics, which results in segfaults on some machines that I > have here. > > Today I was trying some experiments in a new VM, and I couldn't launch > eeschema, either from the main app or standalone. It would segfault before > putting up its window. Then I remembered that I had had that problem in > the past when I was trying out accelerated graphics. But in the past, I > was able to select fallback graphics from that initial dialog. > > In this case, my only way to fix the situation was to copy the json config > files from another machine that was already configured for fallback > graphics. That worked. KiCad was now usable in the VM. > > Most people won't have a set of suitable json files laying around to get > past the segfault, or even know to try that. Thus, I think the initial > dialog needs to be there, or perhaps the default should be changed to > fallback graphics. > > Steve > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] KiCad moving to C++17
Hi Folks- With the release of KiCad v6, we are moving our codebase forward. In this case, we are moving from C++14 to C++17. This will allow us to use more readable, efficient syntax as well as using more cross-platform, standard libraries that are built into modern compilers. This does come at a price, however. Older compilers will not support all of the potential features used by C++17 code. In general, we expect g++ version 8 and higher to be supported, clang++ version 7 and higher as well as MSVC 2019 and higher. One or more of these versions is available on all supported KiCad platforms. If you are using an older Linux distro such as Ubuntu 18.04, you may need to compile KiCad with clang++ instead of g++ in order to use built-in distro packages. We plan on making this switch only in the master branch, not in the 6.0 branch. 6.0 will remain C++14. Please let us know if you have any questions or concerns. We will be making this change next week. Best regards, Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] PPA for KiCad nightly builds is no longer updated
There are currently QA failures on the master branch. These will prevent new updates to the PPA until we fix them. The 6.99 branch will be rocky for a couple of months. Users with deadlines are advised to use the 6.0 stable branch for a while. Regards, Seth On Wed, Dec 29, 2021 at 10:33 AM Stefan Weber wrote: > Hi, > > I added the following PPA to my Linux System a couple of months ago: > > https://launchpad.net/~kicad/+archive/ubuntu/kicad-dev-nightly > > I got every day the latest kicad build. > But since a week I do no longer get updates, the latest version I got is: > > Version: 6.99.0-a9ca49a600~144~ubuntu20.04.1, release build > Build Info: Date: Dec 23 2021 15:10:40 > > since then, no never nightly builds arrived via this PPA. > > It seem after > https://gitlab.com/kicad/code/kicad/-/commit/4b6bf3095a3b1984268ca797aea92029ab4d4b63 > all CI Builds for Linux failed on gitlab. > > Best regards, > > Stefan > > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Why has my name been removed from the translators-Other credits?
Hi David- I'm sorry for the issue. We removed the Translator-other section as it wasn't associated with a language. Was there a language you should be listed with? Again, my apologies for the confusion Seth On Fri, Dec 17, 2021, 9:24 PM David J S Briscoe wrote: > Hi, > I've noticed that the category translators-Other (along with my name) > has been removed from the latest version 6.0 RC2 credits. Why has this > happened? Please explain. Thank you. > > Regards, > > David J S Briscoe > > PS I can send proof of my contribution to the project if required. > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Version 6 release candidate 1
Hi Steven- The other 5 repos (docs, symbols, footprints, templates and packages3d) are tagged. i18n is integrated into the v6 source repository and won't be tagged separately. Seth On Tue, Nov 16, 2021 at 7:14 AM Seth Hillbrand wrote: > They'll be tagged today > > -Seth > > On Tue, Nov 16, 2021, 6:27 AM Steven A. Falco > wrote: > >> So far, only the code/kicad repo has been tagged for 6.0.0-rc1. In order >> to build trial Fedora packages, as you describe below, I'll need the other >> 6 repos tagged to match. >> >> I realize that we are very early in this process, but is there a feel for >> when the remaining repos will be tagged? >> >> Steve >> >> On 11/15/21 10:00 PM, Wayne Stambaugh wrote: >> > Release candidate 1 of version 6 has been tagged and pushed. Package >> builds should be available in the next few days for most systems. There >> are still a few minor issues which should get fixed by stable release >> 6.0.0. If all goes well, the stable release should be ready by the end of >> the year. Thank you to the entire KiCad development team for there effort >> in getting RC1 out. >> > >> > Enjoy, >> > >> > Wayne >> > >> > ___ >> > Mailing list: https://launchpad.net/~kicad-developers >> > Post to : kicad-developers@lists.launchpad.net >> > Unsubscribe : https://launchpad.net/~kicad-developers >> > More help : https://help.launchpad.net/ListHelp >> >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Python Status and a way forward
Hi Folks- Unfortunately, we were not able to get the Python revisions into version 6. As such, we'll be using the legacy SWIG implementation for pcbnew during v6 and will introduce the updated API early in the v7 development process. ## What happened? Our goals for the Python API were to make a stable set of calls that plugin developers could rely on to work over multiple KiCad versions and to expand python scripting to eeschema. This required abstracting a number of underlying concepts and re-writing a set of core applications. And it didn't get done in time. We decided that it was more important to get v6 out to our userbase with the status quo python scripting than for an indefinite delay to get the first API out. ## What's the plan going forward? Following the release of v6, the KiCad core dev team will be meeting to plan out our work for v7. One of the items on our agenda will be to review where things went well and poorly in the v6 development. We do this with the intention of improving both our development work and our communication with the community during upcoming releases. We're also going to be reaching out to some of our plugin developers to get their input on things that they'd like to use the API for and ways that we might be able to facilitate that in v7. If you have interest in being a part of that discussion (and you have published a couple plugins for KiCad or other projects), please reach out. We're happy to include you. I deeply regret that we won't have a shiny new python interface in v6. I know that this will be a disappointment to a number of people. Hopefully, the major advancements that we have built into v6 will assuage that somewhat. --- Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] please let me translate KiCad more directly (Was: Version 6 release schedule)
Hi Marco- The largest concern is that this requires us to remove the language from Weblate. This will limit our community of Italian translators (such as it is) and so we become very dependent on you for up-to-date translations. If you ever need to step back from KiCad for a few months or longer, you would please let us know so that we can re-enable the Weblate Italian translations. If you are up for this, please let me know off-list and I'll connect you with the required information. Seth On Tue, Nov 16, 2021 at 1:06 AM Marco Ciampa wrote: > On Fri, Nov 05, 2021 at 07:58:00AM +, Marco Ciampa wrote: > > On Thu, Oct 28, 2021 at 05:09:56PM -0400, Wayne Stambaugh wrote: > > > The lead development team has agreed on a version 6 release schedule as > > > follows: > > > > > > > Hello devs, > > (oh I hate Weblate...) > > > > > - String freeze November 1. > > [...] > > > > I usually update strings manually from the source so ... I uploaded my > > translations on the weblate interface (that I hate, did I mention it? ;-) > > but that does not trigger any commit on the dev tree. How can I be sure > that > > my translation update will get committed on time for release? > > Is there a way to force the weblate to commit the translations? > > > > Why I hate Weblate. > > Someone said to me: you don't have to have write access to the git repo > since you can upload the .po file directly on weblate... > > Yes and no... since Weblate filters the .po strings on the content of ITS > internal .pot file DISCARDING all the more recent translations. So, for > an almost completely untranslated language project weblate can help since > there is a huge amount of strings to translate, and nobody really cares > it those strings are not really up-to-date with the current status of the > master git repo. > > When instead your translation status is approaching 99% then Weblate gets > in the way since you can never be sure to have translated all strings > since, as I said earlier, you cannot update the strings on the content of > the current git master branch. > > To sum up: please give me write access to the master branch! > > I promise, I'll never fiddle with source files, only translation files > (and if you trust me enough, typos...). And BTW, it is almost impossible > to mess things up with the git log that shows all and each commit one > did... > > TIA > > -- > > Saluton, > Marco Ciampa > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Version 6 release candidate 1
They'll be tagged today -Seth On Tue, Nov 16, 2021, 6:27 AM Steven A. Falco wrote: > So far, only the code/kicad repo has been tagged for 6.0.0-rc1. In order > to build trial Fedora packages, as you describe below, I'll need the other > 6 repos tagged to match. > > I realize that we are very early in this process, but is there a feel for > when the remaining repos will be tagged? > > Steve > > On 11/15/21 10:00 PM, Wayne Stambaugh wrote: > > Release candidate 1 of version 6 has been tagged and pushed. Package > builds should be available in the next few days for most systems. There > are still a few minor issues which should get fixed by stable release > 6.0.0. If all goes well, the stable release should be ready by the end of > the year. Thank you to the entire KiCad development team for there effort > in getting RC1 out. > > > > Enjoy, > > > > Wayne > > > > ___ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : kicad-developers@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Update on the domain name
Hi Folks- A quick update on our domain name situation. We filed a complaint with GoDaddy and Cloudflare about the kicad - pcb.org masquerading as the official KiCad website. Immediately after this, the new owners took down the site and have listed it for auction. Please do not bid on the auction. We are working to acquire the domain name but would like to avoid other parties involved. Thanks, Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Version 6 release schedule
Hello Marco- We usually pull in translations to the tree once per week. But if you'd like it pulled in more quickly, just ask here or on Zulip. -Seth On Fri, Nov 5, 2021 at 12:59 AM Marco Ciampa wrote: > On Thu, Oct 28, 2021 at 05:09:56PM -0400, Wayne Stambaugh wrote: > > The lead development team has agreed on a version 6 release schedule as > > follows: > > > > Hello devs, > (oh I hate Weblate...) > > > - String freeze November 1. > [...] > > I usually update strings manually from the source so ... I uploaded my > translations on the weblate interface (that I hate, did I mention it? ;-) > but that does not trigger any commit on the dev tree. How can I be sure > that > my translation update will get committed on time for release? > Is there a way to force the weblate to commit the translations? > > TIA > > -- > > Saluton, > Marco Ciampa > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Update to Footprint/Symbol paths
Correct. This change handles the default names of the final directories.
Versioning could be implemented with a build arg that would change one of
the higher-level directories. i.e. /usr/share/kicad6/footprints or
/usr/share/kicad/v6/footprints depending on the distribution's conventions.
Seth
On Tue, Oct 19, 2021 at 2:38 PM Nick Østergaard wrote:
> What about versioning these folders? Or is that handled by the packager on
> a given platform with a build arg?
>
> On Mon, 18 Oct 2021 at 01:32, Seth Hillbrand wrote:
>
>> Hi Folks-
>>
>> There's a small change brewing to where the default symbol/footprint
>> libraries are installed.
>>
>> Previously, KiCad had default paths for schematic symbols in
>> `/usr/share/kicad/library` and for footprints in
>> `/usr/share/kicad/modules/` (Windows users found these at
>> %{KICAD_PROGRAM}\share\kicad\library and
>> %{KICAD_PROGRAM}\share\kicad\modules)
>>
>> Starting with tomorrow's nightly build, we will be installing these to
>> `/usr/share/kicad/symbols` for schematic symbols and
>> `/usr/share/kicad/footprints` for layout footprints.
>>
>> I know what you are thinking. "Why would you guys decide to name the
>> directories for what is actually in them? Won't that make it easier for
>> new users to find things?" Well, maybe... The original directory names
>> have a lot of history and were descriptive for the original intent. We've
>> standardized our nomenclature throughout KiCad in advance of v6 and the
>> directory structure was one of the last holdouts.
>>
>> Hopefully the transition will be smooth. If you compile locally, you
>> will need to update your locally installed libraries or set the PATHs
>> variable to point to the libraries (footprints and symbols) you currently
>> have installed. Users who run from one of the packages should find their
>> changes to be transparent.
>>
>> Seth
>>
>> --
>> [image: KiCad Services Corporation Logo]
>> Seth Hillbrand
>> *Lead Developer*
>> +1-530-302-5483
>> Long Beach, CA
>> www.kipro-pcb.comi...@kipro-pcb.com
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help : https://help.launchpad.net/ListHelp
>>
>
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Warning about potentially malicious software
Hi Folks- As you know, the original KiCad domain name (kicad-pcb.org) was recently sold. This happened without notification to the KiCad Project or members of the KiCad Development Team. This sale was unexpected and may pose a risk to KiCad users. The new owners may simply post advertisements or (worst-case scenario) they may host malicious versions of the KiCad software for download. # How did this happen? The domain name was originally registered in 2012 by the then project lead Dick Hollenbeck. As KiCad did not have a formal entity at the time, he registered it in his own name through his company SoftPLC. When the KiCad Project formally became registered under the Linux Foundation, we attempted to secure the rights to the original domain name from Dick without success. In the meantime, Digikey Corporation purchased the kicad.org domain name from squatters and donated it to the KiCad Project. This is now our current domain name. # What is the KiCad Project doing now to protect its users? We are removing all links to the old domain name in the software for version 5.1.11 as well as 6.0. We are also contacting various sites that host content related to KiCad to update their links. # What can I do? Please do not contact Dick about this. He cannot undo the damage at this point. If you host KiCad videos on YouTube or content on a blog that has links to kicad-pcb.org, please update them to kicad.org as soon as possible. This will decrease the visibility of the old domain-name and limit the damage. You can also contact tech sites that post reviews of KiCad or otherwise have links to the old site and ask them to update their links. When installing KiCad, please always verify the installation signature. Starting with KiCad version 5.99, all installs are signed by KiCad Services Corporation. # What is KiCad doing to prevent this in the future? The current kicad.org domain name is not under control of a single person. We have built in safeguards to our transfer process. Additionally, all KiCad trademarks are registered to the Linux Foundation for the sole purpose of advancing open-source EDA software. We regret that this was done to the KiCad project and its users. -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Update to Footprint/Symbol paths
Hi Folks-
There's a small change brewing to where the default symbol/footprint
libraries are installed.
Previously, KiCad had default paths for schematic symbols in
`/usr/share/kicad/library` and for footprints in
`/usr/share/kicad/modules/` (Windows users found these at
%{KICAD_PROGRAM}\share\kicad\library and
%{KICAD_PROGRAM}\share\kicad\modules)
Starting with tomorrow's nightly build, we will be installing these to
`/usr/share/kicad/symbols` for schematic symbols and
`/usr/share/kicad/footprints` for layout footprints.
I know what you are thinking. "Why would you guys decide to name the
directories for what is actually in them? Won't that make it easier for
new users to find things?" Well, maybe... The original directory names
have a lot of history and were descriptive for the original intent. We've
standardized our nomenclature throughout KiCad in advance of v6 and the
directory structure was one of the last holdouts.
Hopefully the transition will be smooth. If you compile locally, you will
need to update your locally installed libraries or set the PATHs variable
to point to the libraries (footprints and symbols) you currently have
installed. Users who run from one of the packages should find their
changes to be transparent.
Seth
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] OpenCascade dependency version bump
This issue is fixed in OpenCascade 7.5+ We use 7.5 for all of our official builds. We are maintaining 7.3 as the minimum OCC version for the time being to support legacy builds on Debian oldstable (buster). Once our support for Buster expires, we will move the CMake minimum version to 7.5. MinGW also uses 7.5 FWIW ( https://packages.msys2.org/base/mingw-w64-opencascade) Seth On Wed, Oct 13, 2021 at 1:39 PM Cirilo Bernardo wrote: > Hi Seth, > > I think it would be good if someone could check that everything works OK > on Windows with non-ascii characters in the path. At the time I created > the support for STEP a patch (an awful hack really) was needed for OCE and > OCC just didn't work. I think OCC fixed the issues a few years later but > I'm not 100% sure. There is also a possibility that a natively built OCC > works fine but one built within MinGW won't be able to handle non-ASCII > characters in paths. > > Cirilo > > > On Thu, Oct 14, 2021 at 4:07 AM Seth Hillbrand wrote: > >> Hi Folks- >> >> After a transition period, we are officially dropping support for the >> OpenCascade Community Edition (OCE) fork. The official OpenCascade >> releases (libocct for most *nix distros) fix a number of bugs in 3d model >> loading and export. >> >> The effect of this in KiCad is that we are dropping the build flag >> KICAD_USE_OCE. Developers should change their builds (if they haven't >> already) to the flag KICAD_USE_OCC, which has been the default for the past >> couple of months. >> >> Let us know if you have any questions or concerns. >> >> Seth >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 >> Long Beach, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] OpenCascade dependency version bump
Hi Folks- After a transition period, we are officially dropping support for the OpenCascade Community Edition (OCE) fork. The official OpenCascade releases (libocct for most *nix distros) fix a number of bugs in 3d model loading and export. The effect of this in KiCad is that we are dropping the build flag KICAD_USE_OCE. Developers should change their builds (if they haven't already) to the flag KICAD_USE_OCC, which has been the default for the past couple of months. Let us know if you have any questions or concerns. Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Launchpad bug tracker closure
Looks like you got them all. Thank you very much Orson! -Seth On Fri, Oct 8, 2021 at 11:31 AM Maciej Suminski wrote: > Hi everyone, > > It is time so say goodbye to the Launchpad bug tracker. Seth has asked > to me run a script which will close all bugs in the Launchpad bug > tracker. I have just done a test run with several reports and I already > see it will generate a massive amount of e-mail notifications. > > I plan to close all bugs tomorrow evening (UTC+2), so if you want to > avoid flooding your message box, then it is a good moment to disable > Launchpad notifications or set up a spam filter. > > Cheers, > Orson > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] please re-write it
Thanks for catching this. I've shortened this down to "Each keyword is replaced by its value" -Seth On Mon, Sep 20, 2021 at 12:06 AM Marco Ciampa wrote: > There is something wrong here.. > > #: pagelayout_editor/dialogs/properties_frame.cpp:559 > msgid "Keywords are replaced by they actual value in strings" > > I would rather say: > > "The keywords are replaced by their actual string values" > > TIA > > -- > > Saluton, > Marco Ciampa > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Modifier Key Modification
OK, slight modification then. Thanks to some clever Windows work today by Mark R, the Alt key no longer locks up the application when released. This is sufficient for us to keep the alt key as an option for v6, so we've re-enabled it. Long-click and Alt should now do the same thing with the caveat that we may be re-purposing the Alt key in v7 but we'll cross that bridge once we get there. Seth On Sun, Sep 5, 2021 at 6:44 PM Andrew Lutsenko wrote: > Track pads either have buttons or have a clicking surface. Press click and > hold is the equivalent to mouse button long click. > > On Sun, Sep 5, 2021 at 2:05 PM Jeff Young wrote: > >> Umm… how do you do a long-click on a track-pad set up for tapping? >> >> On 5 Sep 2021, at 21:53, Seth Hillbrand wrote: >> >> Hi Folks- >> >> A final update to the 5.99 modifier key situation has been pushed. This >> resolves a number of conflicting modifier keys for different actions. >> >> Part of this changes how you work with the 45° limitation and part of >> this changes how you get the disambiguation menu. >> >> Previously 45° was a hotkey (Shift or in v5 Ctrl/Cmd). This is now set >> as a state. By default, the TAB key switches between states but you can >> customize this action hotkey to your liking. >> >> Previously, Ctrl (and earlier Alt in v5) allowed you to show the full >> disambiguation menu (which item should I choose) without KiCad applying >> heuristics to the items under the cursor. Now, you access this option by >> clicking and holding the left mouse button down. >> >> Moving these actions allows us to standardize the modifier key mapping >> (Ctrl/Alt/Shift) for selections without the use of the Alt key, which was >> problematic for Windows users. >> >> Currently: >> >> Shift + Click = Add to selection >> Shift + Ctrl + Click = Remove from selection >> Ctrl + Click = Highlight net >> >> When not using the selection tool, the Ctrl modifier key still allows you >> to ignore grid snaps when drawing and the Shift modifier still allows you >> to ignore item snaps. >> >> Seth >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 <+1%20530-302-5483> >> Long Beach, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Modifier Key Modification
Hi Folks- A final update to the 5.99 modifier key situation has been pushed. This resolves a number of conflicting modifier keys for different actions. Part of this changes how you work with the 45° limitation and part of this changes how you get the disambiguation menu. Previously 45° was a hotkey (Shift or in v5 Ctrl/Cmd). This is now set as a state. By default, the TAB key switches between states but you can customize this action hotkey to your liking. Previously, Ctrl (and earlier Alt in v5) allowed you to show the full disambiguation menu (which item should I choose) without KiCad applying heuristics to the items under the cursor. Now, you access this option by clicking and holding the left mouse button down. Moving these actions allows us to standardize the modifier key mapping (Ctrl/Alt/Shift) for selections without the use of the Alt key, which was problematic for Windows users. Currently: Shift + Click = Add to selection Shift + Ctrl + Click = Remove from selection Ctrl + Click = Highlight net When not using the selection tool, the Ctrl modifier key still allows you to ignore grid snaps when drawing and the Shift modifier still allows you to ignore item snaps. Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] First Merge Request
Hi Mike- Thank you for the contributions! We're always glad to have new contributors interested in improving KiCad. In the merge request workflow, people will sometimes mark their merge requests as "Draft" or "WIP" as you did for 883. When you do this, we generally won't look it over unless you ask for specific feedback. Otherwise, we'll assume that it isn't ready for review and just leave it in the queue. In general, we prefer MRs address specific issues. Typically, we will discuss the problem in the issue report (sometimes you will get feedback that the issue shouldn't be address). In the MR, we typically only discuss the code and how it is implemented. We do not have any documentation at the moment on the KiWay system outside of the doxygen comments. Sending a KiWay is usually reserved for communication between apps. Inside the application, you would typically call the routine directly or send a tool event, depending on the action you want. Thanks for the contributions and we look forward to working with you! One last aside: as you probably know, we are currently in a feature freeze for version 6. There are a number of outstanding issues that we are working through but we are not adding new features at the moment. If you'd like to take a swing at fixing some of the remaining issues, you can find them here: https://gitlab.com/kicad/code/kicad/-/issues?scope=all=opened_title=6.0.0-rc1_id=None Seth On Tue, Jul 20, 2021 at 10:57 AM Mike Williams wrote: > Hello All, > > I've posted my first merge request to the KiCad gitlab. It seems to be > within the guidelines now, sorry for spamming the previous requests. I was > having some trouble with GitLab identifying whether or not the commits > could be rebased onto master with fast forwarding only. It was almost > certainly my mistake, I'm more used to patch submission using git > format-patch than merge requests. > > https://gitlab.com/kicad/code/kicad/-/merge_requests/883 > > My goal is to contribute by fixing a few small annoyances here and there. > Is it preferred that I open an Issue for each fix that I can reference in > my merge request, or to just send the merge request with the changes > described? > > Also, is there any documentation outside of doxygen for the KiWay and > Hotkey subsystems? For KiWay, I was unsure whether it was better to call > functions directly or to use KiWay events when both would have the same > functionality. For hotkeys, I was thinking about adding more hotkeys to the > pin table editor. > > The codebase in general seems very clean. Thanks for a great product, I've > shipped numerous designs with it. > > Mike > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Problems regarding Weblate checks
Sorry, I responded too quickly. Looking at this, it appears that Weblate doesn't allow replacing a plain format string with a positional format string. I'll open a bug report with Weblate to fix this. -Seth On Thu, Jul 1, 2021 at 8:43 AM Seth Hillbrand wrote: > Hello Rigo- > > The mismatching line breaks check can be useful in catching issues where > there is semantic information in the break. But you are correct that this > check is not critical. Since it breaks your translation, we should disable > it. > > The issue of the C-format check is curious. According to > https://docs.weblate.org/en/latest/user/checks.html#c-format, your > placeholder should be valid. Perhaps there is another C-format check that > it doesn't pass? > > -Seth > > On Thu, Jul 1, 2021 at 8:30 AM RigoLigo RLC wrote: > >> Recently I've found some annoying checks that are preventing some >> proper translation being done (translations that don't pass the checks >> won't be compiled into .mo file) when working on Simplified Chinese >> translation. >> >> 1. There must be same "lines" of text in original text and translated >> text. This one is preventing the custom DRC rule syntax helps being >> compiled. There's many manual line breaks in the text, probably to >> manually control the dialog width, however the translated Chinese text >> can be a bit shorter than English text, and there'll be a few lines >> less than English text. Weblate noticed this issue and prevented the >> text from being compiled. This check doesn't seem to make any sense >> for me. Could you guys provide a good explanation? >> >> 2. Words in English sentences can be different order from Chinese, for >> example, "Pad 1 of J3" is actually "J3 的焊盘 1" when translated, so I >> need to use order marks or whatever it is called in the translation >> text, so "Through hole pad %s of %s" is translated as "%2$s 的通孔焊盘 %1$" >> [1]. But this kind of order marking isn't in standard ISO C99 (it's an >> POSIX standard instead), and C-format check of Weblate fails. I >> checked GNU gettext docs and it said translators can rely on this >> feature [2]. How do we solve this problem? >> >> Rigo >> >> [1] >> https://hosted.weblate.org/translate/kicad/master-source/zh_Hans/?checksum=65ad27d657ff921f >> [2] >> https://www.gnu.org/software/gettext/manual/html_node/c_002dformat.html >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > > > -- > [image: KiCad Services Corporation Logo] > Seth Hillbrand > *Lead Developer* > +1-530-302-5483 > Long Beach, CA > www.kipro-pcb.comi...@kipro-pcb.com > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Problems regarding Weblate checks
Hello Rigo- The mismatching line breaks check can be useful in catching issues where there is semantic information in the break. But you are correct that this check is not critical. Since it breaks your translation, we should disable it. The issue of the C-format check is curious. According to https://docs.weblate.org/en/latest/user/checks.html#c-format, your placeholder should be valid. Perhaps there is another C-format check that it doesn't pass? -Seth On Thu, Jul 1, 2021 at 8:30 AM RigoLigo RLC wrote: > Recently I've found some annoying checks that are preventing some > proper translation being done (translations that don't pass the checks > won't be compiled into .mo file) when working on Simplified Chinese > translation. > > 1. There must be same "lines" of text in original text and translated > text. This one is preventing the custom DRC rule syntax helps being > compiled. There's many manual line breaks in the text, probably to > manually control the dialog width, however the translated Chinese text > can be a bit shorter than English text, and there'll be a few lines > less than English text. Weblate noticed this issue and prevented the > text from being compiled. This check doesn't seem to make any sense > for me. Could you guys provide a good explanation? > > 2. Words in English sentences can be different order from Chinese, for > example, "Pad 1 of J3" is actually "J3 的焊盘 1" when translated, so I > need to use order marks or whatever it is called in the translation > text, so "Through hole pad %s of %s" is translated as "%2$s 的通孔焊盘 %1$" > [1]. But this kind of order marking isn't in standard ISO C99 (it's an > POSIX standard instead), and C-format check of Weblate fails. I > checked GNU gettext docs and it said translators can rely on this > feature [2]. How do we solve this problem? > > Rigo > > [1] > https://hosted.weblate.org/translate/kicad/master-source/zh_Hans/?checksum=65ad27d657ff921f > [2] > https://www.gnu.org/software/gettext/manual/html_node/c_002dformat.html > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Python 3 now required
Hi Folks- KiCad now officially only supports Python 3. Note that this comes a full year and 6 months after Python 2 was deprecated (https://pythonclock.org/) and most, if not all, of our supporting packages have pledged to stop supporting Python 2 (https://python3statement.org/) We are now making the same transition. As part of this transition, we are also binding the Python interpreter more closely with KiCad. This means that we have removed the following build settings and set them all to 'ON': KICAD_SCRIPTING=ON KICAD_SCRIPTING_MODULES=ON KICAD_SCRIPTING_PYTHON3=ON KICAD_SCRIPTING_WXPYTHON=ON KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON KICAD_SCRIPTING_ACTION_MENU=ON For the moment, `KICAD_SCRIPTING_WXPYTHON` does remain an advanced build setting but we'll be moving that to the advanced_config file shortly as it does not control a build setting (only a run-time operation). The current minimum Python version is 3.7 (due to a module test call we use) but we are looking at potentially supporting Python 3.6 if we can handle dynamic reloads. A large thank you in this effort goes to Mark Roszko and Adam Wolf who wrangled the build requirements for Windows and Mac respectively. The transition was non-trivial and largely invisible. KiCad has come out better for the work that they contributed. Thank you! -Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] How many users does KiCAD have?
Hello Avishay- We do not currently have telemetry for KiCad directly. But we do have some metrics on downloads as a proxy for installations. We average ~1500 downloads per day from the KiCad website. This is relatively steady over time and works out to 225,000 downloads of KiCad 5.1.9. This accounts for Windows (90%) and MacOS (10%) but does not account for installations on linux and other *nixes. From the Ubuntu numbers given by Jean-Samuel, Ubuntu will account for another 30 downloads per day or a total of 5k users. The limitations of this method of counting: 1) It does not track _unique_ download (no IP logging), so a user downloading twice will count twice 2) It does not account for users that neglect to upgrade their minor versions, so it does not count users of 5.1.0-5.1.8 that have not upgraded. 3) It does not count Linux users who compile on their own or install versions directly from their package managers (and not the Ubuntu PPA) Overall, this is likely our baseline number. We don't have estimates for the rates of upgrades, so we can't say how much larger the true number is right now. It also does not capture users running nightly builds (they are more likely to download multiple times for the same installation) or users running older versions of KiCad. Also of interest might be this breakdown of the locations of users downloading KiCad: [image: image.png] As you can see, we are dominated by European users at the moment. I will note that both Asia and South America are becoming more prevalent. And, in case this graph concerns people, it is derived by major IP octets. We do not store IP addresses, but we do store coarse locations by zeroing out the lower two octets of IP addresses before geolocating to a country. This helps us to make informed decisions about features (e.g. ISO vs. ANSI vs JIS vs GOST?) to include in future versions of KiCad. While we do have some ideas of commercial usage, these are not data that we share publicly. I hope you understand. I hope this helps. Regards- Seth On Tue, May 18, 2021 at 3:22 AM Avishay Orpaz wrote: > I understand it's a tricky question to answer, especially when it comes to > open source software, but is there any estimation about the number of > active KiCAD users? How many (commercial) companies use KiCAD? How many > people downloaded each version of KiCAD? > > Avishay > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] OCE vs. OCC default build flag
After reviewing the thread that Nick linked ( https://gitlab.com/kicad/code/kicad/-/issues/6198) I recall this discussion more. I think that we should remove OCE altogether. The existing versions have bugs that we cannot fix and it is fully deprecated at the source repository (https://github.com/tpaviot/oce/releases) in that it only tags upstream releases and hasn't released any updates since 2018. Keeping OCE in the build tree as an option is just asking for headaches that we can avoid in v6. -Seth On Mon, May 17, 2021 at 12:07 PM Steven A. Falco wrote: > I confirm that Fedora already selects OCC in its build scripts, both for > the official 5.1 builds, and for the 5.99 nightlies. The default can > change without affecting Fedora. > > Steve > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] OCE vs. OCC default build flag
Yes, our plan has been to switch the default (if it is not already). We were waiting until both MSVC and Mac builds had OCC well tested, which I think has happened now. Seth On Sun, May 16, 2021, 2:10 PM Eeli Kaikkonen wrote: > While I was writing Linux and several distro specific build > instructions ( > https://gitlab.com/eelik-kicad/kicad/-/wikis/How-to-build-KiCad-on-Linux-(the-easy-way) > , discussion in > > https://forum.kicad.info/t/build-from-source-simple-instructions-to-compile-kicad-for-some-linux-distributions/28982 > ) I noticed that all distros I tried have OCC instead of OCE. > > Should the default build flag be changed to be OCC instead of OCE? > > Eeli Kaikkonen > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Feature request: Gerbview - Print - Pagination option
Welcome to the list! If you would like to log a feature request, please do so at https://gitlab.com/kicad/code/kicad/-/issues Regards- Seth On Wed, May 5, 2021 at 2:15 PM Clifford Neal Simon wrote: > Hi devs, > > New mailing-list member here. > > When I print multiple layers from Gerbview, the layers appear one per > page. Would like a radio button for pagination, to choose all layers on one > page or one layer on each page. Pcbnew has this but not Gerbview. > > In my engineering workflow I print out a paper PCB "model" showing (only) > the edges, drills, and silkscreen. With office tools I cut the edges and > accurately punch out the drill holes for all mounting hardware, then I > "install" the piece of paper in the mounting to show board shape and > silkscreen in the actual housing and mounting. This is also a test of > gerber integrity since the "model" is produced from preliminary gerbers. In > my current workflow I have to print from Gerbview (to PDF) then postprocess > the PDF to flatten it to one page. > > Note, I think pcbnew can print "real" drill if you include a copper layer > but my "model" must not show any copper or soldermask. Silkscreen only. > Also, a print from pcbnew is useless for gerber integrity. Whence, I am > inquiring about the pagination feature for Gerbview, to be sure > verification of gerber is included in the workflow. > > > > Clifford Simon > I'm using (5.1.9)-1. I just saw the 5.1.10 release but I haven't > downloaded it yet. > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build issue
You will need to upgrade ngspice as well. The variable is renamed to NG_BOOL. -Seth On Wed, May 5, 2021 at 12:21 PM BERTRAND Joël wrote: > Thanks for your patch. > > Nevertheless, after make clean && make, build process now aborts > with : > > [ 47%] Building CXX object > eeschema/CMakeFiles/eeschema_kiface_objects.dir/sim/ngspice.cpp.o > In file included from /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:31: > /home/bertrand/git/kicad/eeschema/sim/ngspice.h:138:35: error: ‘NG_BOOL’ > has not been declared > 138 | static int cbBGThreadRunning( NG_BOOL aFinished, int aId, > void* aUser ); > | ^~~ > /home/bertrand/git/kicad/eeschema/sim/ngspice.h:139:47: error: ‘NG_BOOL’ > has not been declared > 139 | static int cbControlledExit( int aStatus, NG_BOOL > aImmediate, NG_BOOL aExitOnQuit, int aId, > | ^~~ > /home/bertrand/git/kicad/eeschema/sim/ngspice.h:139:67: error: ‘NG_BOOL’ > has not been declared > 139 | atic int cbControlledExit( int aStatus, NG_BOOL aImmediate, > NG_BOOL aExitOnQuit, int aId, > | ^~~ > > /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:635:5: error: ‘int > NGSPICE::cbBGThreadRunning’ is not a static data member of ‘class NGSPICE’ > 635 | int NGSPICE::cbBGThreadRunning( NG_BOOL aFinished, int aId, > void* aUser ) > | ^~~ > /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:635:33: error: > ‘NG_BOOL’ was not declared in this scope; did you mean ‘BOOL’? > 635 | int NGSPICE::cbBGThreadRunning( NG_BOOL aFinished, int aId, > void* aUser ) > | ^~~ > | BOOL > /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:635:52: error: > expected primary-expression before ‘int’ > 635 | int NGSPICE::cbBGThreadRunning( NG_BOOL aFinished, int aId, > void* aUser ) > |^~~ > /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:635:61: error: > expected primary-expression before ‘void’ > 635 | int NGSPICE::cbBGThreadRunning( NG_BOOL aFinished, int aId, > void* aUser ) > | ^~~~ > /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:635:73: error: > expression list treated as compound expression in initializer > [-fpermissive] > 635 | t NGSPICE::cbBGThreadRunning( NG_BOOL aFinished, int aId, void* > aUser ) > | > ^ > > /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:646:45: error: > ‘NG_BOOL’ has not been declared > 646 | int NGSPICE::cbControlledExit( int aStatus, NG_BOOL aImmediate, > NG_BOOL aExitOnQuit, int aId, void* aUser ) > | ^~~ > /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:646:65: error: > ‘NG_BOOL’ has not been declared > 646 | NGSPICE::cbControlledExit( int aStatus, NG_BOOL aImmediate, > NG_BOOL aExitOnQuit, int aId, void* aUser ) > | ^~~ > > make[2]: *** > [eeschema/CMakeFiles/eeschema_kiface_objects.dir/build.make:2846 : > eeschema/CMakeFiles/eeschema_kiface_objects.dir/sim/ngspice.cpp.o] Erreur 1 > make[1]: *** [CMakeFiles/Makefile2:3021 : > eeschema/CMakeFiles/eeschema_kiface_objects.dir/all] Erreur 2 > make: *** [Makefile:182 : all] Erreur 2 > > In my case, NGSPICE_PACKAGE_VERSION is defined in sharedspice.h > thus > NG_BOOL is never defined in eeschema/sim/ngspice.h. > > Regards, > > JB > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build issue
I have conditionally adjusted the signature based on a secondary tag that also seems new since NGSPICE34. We can't adjust the API without packaging sharedspice.h ourselves, which I don't think we want. As an aside, it would be very helpful when typedefing a new value to include a define (like #define HAS_NG_BOOL 1) with it. That would allow us to test for the new signature when compiling. Best- Seth On Wed, May 5, 2021 at 1:46 AM Holger Vogt wrote: > > > Am 04.05.2021 um 23:32 schrieb Seth Hillbrand: > > We can adjust our interface to cope with the change to int as an > > underlying type. > > > > That is great. Thus we may avoid any potential problems. > > > However, one concern is that the typedef exists unscoped inside a header > > file. The term "BOOL" is relatively generic and so there are likely to > > be some conflicts with other libraries that use this term differently. > > > > Would you be able to scope it with a "using" keyword, or, alternatively, > > with a less common term such as NGSPICE_BOOL? > > That's what I will do immmediately for the ngspice master and pre-master > branches. > > Btw I do not see this discussion in the kicad-developers team mailing > list archive. Does is add to a very old thread? > > Holger > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build issue
We can adjust our interface to cope with the change to int as an underlying
type.
However, one concern is that the typedef exists unscoped inside a header
file. The term "BOOL" is relatively generic and so there are likely to be
some conflicts with other libraries that use this term differently.
Would you be able to scope it with a "using" keyword, or, alternatively,
with a less common term such as NGSPICE_BOOL?
Best-
Seth
On Tue, May 4, 2021 at 2:29 PM Holger Vogt wrote:
> The last commit to ngspice master branch is
>
>
> https://sourceforge.net/p/ngspice/ngspice/ci/ded0f79c01079eaa6f4cdbd49292897c73273e23/
>
> ded0f79c0 ("Avoid type 'bool', as ist is a built-in type in C++, not
> equaling 'int' which ngspice is using.", 2021-03-28)
>
> This patch is a reaction to bug report
> https://sourceforge.net/p/ngspice/bugs/545/.
>
> We may discuss this change.
>
> Holger
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build issue
Looks like Holger just added this:
https://github.com/imr/ngspice/commit/ded0f79c01079eaa6f4cdbd49292897c73273e23
I'm not sure why. I think Holger is on this list, so hopefully he can help
explain the reasoning.
-Seth
On Tue, May 4, 2021 at 2:04 PM Jon Evans wrote:
> What version of ngspice are you using?
>
> Sourceforge is down right now so I can't check the latest tree easily, but
> in my cached version, the ControlledExit function signature in
> sharedspice.h is using bool (not BOOL), and so is KiCad.
>
> Is there some version of ngspice where those function signatures are BOOL
> (aka int) not bool?
>
> -Jon
>
> On Tue, May 4, 2021 at 4:49 PM BERTRAND Joël
> wrote:
>
>> Hello,
>>
>> I use KiCAD 5.99 as rolling release. For a few days, compilation
>> aborts
>> with :
>>
>> [ 32%] Building CXX object
>> eeschema/CMakeFiles/eeschema_kiface_objects.dir/sim/ngspice.cpp.o
>> /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp: In member function
>> ‘void NGSPICE::init_dll()’:
>> /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:486:47: error: invalid
>> conversion from ‘int (*)(int, bool, bool, int, void*)’ to ‘int (*)(int,
>> BOOL, BOOL, int, void*)’ {aka ‘int (*)(int, int, int, int, void*)’}
>> [-fpermissive]
>> 486 | m_ngSpice_Init( , , ,
>> NULL, NULL,
>> | ^
>> | |
>> | int (*)(int, bool,
>> bool, int, void*)
>> /home/bertrand/git/kicad/eeschema/sim/ngspice.cpp:487:21: error: invalid
>> conversion from ‘int (*)(bool, int, void*)’ to ‘int (*)(BOOL, int,
>> void*)’ {aka ‘int (*)(int, int, void*)’} [-fpermissive]
>> 487 | , this );
>> | ^~
>> | |
>> | int (*)(bool, int, void*)
>> make[2]: ***
>> [eeschema/CMakeFiles/eeschema_kiface_objects.dir/build.make:2846 :
>> eeschema/CMakeFiles/eeschema_kiface_objects.dir/sim/ngspice.cpp.o] Erreur
>> 1
>> make[1]: *** [CMakeFiles/Makefile2:3021 :
>> eeschema/CMakeFiles/eeschema_kiface_objects.dir/all] Erreur 2
>> make: *** [Makefile:182 : all] Erreur 2
>>
>> I have built ngspice library from source (git).
>>
>> To be sure that this issue is reproductible, I have rebuild
>> ngspice
>> library and kicad from scratch with the same error.
>>
>> My workstation runs with Linux Debian/testing (up to date) with
>> gcc
>> 10.2.1. If I understand gcc error, compiler complains about mistake
>> between BOOL (that seems to be 'int') and bool, but I don't known C++
>> enough to fix it.
>>
>> Best regards,
>>
>> --
>> KACHELHOFFER-BERTRAND Joël
>> http://www.systella.fr
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help : https://help.launchpad.net/ListHelp
>>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 5.1.10 stable release tagged
Docs and i18n have been tagged. -Seth On Tue, Apr 27, 2021 at 7:05 AM Steven A. Falco wrote: > +1 > > I will need doc and i18n to start the Fedora build. > > Steve > > On 4/27/21 8:59 AM, Jean-Samuel Reynaud wrote: > > Hi, > > > > Same with kicad-i18n... > > > > > > Le 27/04/2021 à 14:35, Christoph Moench-Tegeder a écrit : > >> Hi, > >> > >> ## Wayne Stambaugh (stambau...@gmail.com): > >> > >>> I just pushed the stable release tag to GitLab. Please update any repo > >>> tags as required so we can get the packages build. > >> > >> Any chance to get kicad-doc tagged before the release? I'd rather > >> push kicad, all the libraries and docs at once instead of piecemeal. > >> > >> Regards, > >> Christoph > >> > > > > > > ___ > > Mailing list: https://launchpad.net/~kicad-developers > > Post to : kicad-developers@lists.launchpad.net > > Unsubscribe : https://launchpad.net/~kicad-developers > > More help : https://help.launchpad.net/ListHelp > > > > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] translation issues
Hi Marco- I'm sorry to hear that this process has been so painful. I'll try to make it easier. Maybe a once-per week scheduled update of the Weblate files? Would that work? To use the pofile upload, you will need to grab the pofile from Weblate (I think you discovered this) rather than generating one yourself. Best- Seth On Tue, Apr 13, 2021 at 12:53 AM Marco Ciampa wrote: > Hello devs, > sorry but I'm a little frustrated. > > I think that the actual translation workflow is inefficient and not > really helping translators. > > I spent o lot of hours last week updating the Italian translation of the > master branch: hundreds of strings. > > I first tried to upload the translation on Weblate but it discharged > hundreds of strings (the vast majority of my work) since Weblate does not > updates the strings from the sources but simply discharges all strings > that do not match with the current template even if it is very old and > un-updated. > > Then I tried that convoluted procedure of requesting a merge even if for > one single translation file. It did not work either because of a conflict > with the old and un-updated weblate inserted translation file. Somebody > decided to merge weblate, then updated all strings, then my merge request > that obviously failed. > > Now, since git keeps track of every single commit, is it possible to > authorize commits to some translators? What security concerns can we > possibly have? > > Or to make weblate update the po files automatically in order to > translate without having to wait for someone to commit the new templates? > > Or to automatically update the po files templates automatically every now > and then? > > In the meantime I'll try again with a merge request, with fingers crossed. > > TIA > > -- > > Saluton, > Marco Ciampa > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] KiCAD 5.99/6 Python API status & time schedule
Hi Folks- Sorry for the slow response on this message. The Python work is slower than we had hoped for a few reasons. Only partially pandemic related. 1) We need to move to Python3. This is no longer optional because we use an interface to wxWidgets that has moved to Python3. While our scripts have been generally compatible with Python2 and Python3, this is not as straight-forward when packaging. Our build systems have grown up around Python2, so there is quite a bit that is baked into the systems. Unfortunately, our Windows build system (msys2) was not packaging the new requirements and wxPython (our python interface to the GUI) was only building for MSVC. We have now moved our nightly builds to MSVC to support this. MacOS is taking a bit longer. There are additional requirements on MacOS due to the security restrictions that make it difficult to package KiCad in the manner we have before. When the security restrictions place the application in quarantine, we cannot access the python application to run our scripts. There are solutions to this and we are working through them now. 2) We try not to break nightly builds. This means that some actions need to be sequential. Get the nightly builds running with Python 3 first, then move the python interface. The upshot is that we are almost there. Once we get the signed MacOS nightly builds out (this week?), we can move the Python interface over to v3 and start finding bugs in the new API. The reason we are not accepting bug reports on the old API is that this needs to move and re-basing gets progressively more difficult the more changes we introduce to the legacy API. We have merged some changes where these did not impact our work. Regards- Seth On Sat, Apr 10, 2021 at 10:39 PM José Ignacio wrote: > I am an avid user of Jan's tools (KiKit mostly) and it has become > increasingly difficult to keep them working with current v6 code as api > calls keep getting removed or moved around. I know that having an open > development process for the new API can be counter productive (bikeshedding > and all) but if there is not a defined deadline for this to land on in this > feature freeze, would the developers consider accepting bug reports and > merge requests against api regressions from 5.1 as bugs in the interim? > > > On Thu, Apr 1, 2021 at 4:15 AM Jan Mrázek wrote: > >> Hello, >> >> I develop and maintain several KiCAD plugins. Many of my users started >> switching/would like to KiCAD 5.99 as it brings many exciting features. >> Therefore, I get frequently a question when KiCAD v5.99 will be >> supported. However, as there were some breaking changes and some parts >> of the API are gone and their substitutes are missing, I cannot support >> nightly (e.g., [1]). I remember there were some promises on the API for >> 5.99/6 during summer-autumn 2020 that it could be ready around end of >> January 2021. However, as I checked the source code, there are no news >> regarding the API. I also did not found any draft on the proposed >> feature of the API. >> >> Therefore, I would like to ask you: >> >> - is there any proposal of the new API for pcbnew and eeschema we could >> check out? I am interested to see it, possibly start adapting my plugins >> to it and e.g., give you feedback on missing functionality/hard to use >> parts before it gets freeze (basically my concerns from [2]) >> - is there any work-in-progress we can test? If not, is there a known >> time estimate when KiCAD can reach first testable version of the Python >> API? >> - I know that maintaining large open-source project is hard and time >> consuming, so I would like to ask if there is anything I could do to >> help your regarding the API? I have already contributed to KiCAD and I >> think am a skillful C++ programmer, so if there are some isolated tasks >> that you can delegate, I am willing to contribute! >> >> PS: As I am not a native speaker, so I am not sure if I set the tone of >> the e-mail right. To clarify; I am writing in a curious and caring >> matter. I do not blame you guys for not having the API yet. I value your >> work and appreciate it a lot! >> >> Jan >> >> [1] https://gitlab.com/kicad/code/kicad/-/issues/6885 >> [2] https://gitlab.com/kicad/code/kicad/-/issues/7134 >> >> >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > _______ > Mailing list: https://launchpad.net/~kicad-developer
Re: [Kicad-developers] Can we merge a change to STEP export despite code freeze?
Hi Cirilo- How would you envision this feature being used? -Seth On Sat, Apr 10, 2021 at 8:36 PM Cirilo Bernardo wrote: > I made a small change to the STEP exporter: > https://gitlab.com/cbernardo/kicad > > The change implements the creation of STEP models based on IDF outlines. > This makes it possible for users to specify simple extruded models for some > parts and more complex STEP models where the size and form matter. > > Although in code freeze, this only affects the (standalone) STEP exporter > and should have no impact on the main KiCad suite so I think it's safe to > put > it in. > > Let me know if a merge for this change would be OK and I can create > the merge request. > > Regards, > Cirilo > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Scaling of models in STEP export
We did. It hasn't been implemented yet, so this remains the v5 status quo at the moment. -Seth On Fri, Apr 9, 2021 at 9:37 PM Cirilo Bernardo wrote: > I pulled the latest kicad source and was inspecting the STEP exporter. > I was surprised that it is allowing scaling of STEP models. I thought > we had already established before that this is abject nonsense and > should never be allowed? > > Regards, > Cirilo > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 5.1.10 stable release
Thanks Marco. Should be fixed now.
-S
On Fri, Apr 2, 2021 at 11:09 AM Marco Ciampa wrote:
> On Fri, Apr 02, 2021 at 01:21:11PM -0400, Wayne Stambaugh wrote:
> > I would like to tag 5.1.10 for release by the end of April for release in
> > early May. This is a heads up to the rest of the development teams to
> > please get everything ready to go by then. Please let me know if you
> > anticipate any issues with that date so I can push back the schedule.
> Thanks
> > in advance for the help.
>
> In kicad/tree_project_frame.cpp line 1086
>
> else
> {
> m_Parent->SetStatusText( _( "" ), 0 );
> }
>
> rises this warning:
>
> ./update-po-files.sh it
> Using default SOURCEDIR=../kicad
> kicad/tree_project_frame.cpp:1086: warning: Empty msgid. It is reserved
> by GNU gettext:
> gettext("") returns the header
> entry with
> meta information, not the
> empty string.
>
> please add a space or something or just delete it (why did someone make
> it?) ...
>
> --
>
> Saluton,
> Marco Ciampa
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] possible license mismatch in bitmaps_png/sources ?
The correct license is CC-BY-SA. We'll update the SVG to the correct license. Seth On Fri, Apr 2, 2021, 8:05 AM Carsten Schoenert wrote: > Hi, > > while working on a current snapshot (42c6af4) of the KiCad development > tree and adjusting the build environment for Debian unstable I'm facing > the output of the Lintian QS tool about the usage of the non-free > Creative Commons Non-Commercial Share-Alike (CC-NC-SA) license for some > source files. The used license is considered as non-free within Debian. > > > $ grep -r by-nc-sa bitmaps_png/sources/ > > bitmaps_png/sources/dark/gbr_select_mode2.svg: rdf:resource=" > http://creativecommons.org/licenses/by-nc-sa/4.0/; /> > > bitmaps_png/sources/dark/gbr_select_mode2.svg: rdf:about=" > http://creativecommons.org/licenses/by-nc-sa/4.0/;> > > bitmaps_png/sources/dark/bug.svg: rdf:resource=" > http://creativecommons.org/licenses/by-nc-sa/4.0/; /> > > bitmaps_png/sources/dark/bug.svg: rdf:about=" > http://creativecommons.org/licenses/by-nc-sa/4.0/;> > > bitmaps_png/sources/light/gbr_select_mode2.svg: rdf:resource=" > http://creativecommons.org/licenses/by-nc-sa/4.0/; /> > > bitmaps_png/sources/light/gbr_select_mode2.svg: rdf:about=" > http://creativecommons.org/licenses/by-nc-sa/4.0/;> > > bitmaps_png/sources/light/bug.svg: rdf:resource=" > http://creativecommons.org/licenses/by-nc-sa/4.0/; /> > > bitmaps_png/sources/light/bug.svg: rdf:about=" > http://creativecommons.org/licenses/by-nc-sa/4.0/;> > > The CREDIT file in the same folder is saying something different. > > > $ cat bitmaps_png/sources/CREDITS > > ICONS: > > > > Original KiCad Icon work by Inigo Zuluaga and Fabrizio Tappero among > others > > > > KiCad icons were redesigned in 2020 by Aleksandr Zyrianov > > > > License: CC-BY-SA 4.0 > > No matter how the correct situation is, I see here a mismatch between > the source license and the later used license. I'm not sure if the > source license is by-nc-sa-4.0 (CC-NC-SA) then the derived work can be > licensed as CC-BY-SA. > > If the source files with the critical license aren't used for building > the KiCad package I can drop them while importing the source into the > Debian working tree. The KiCad package is already using the 'dfsg' > suffix due other files we need to exclude. > > So, how is the correct license situation for the SVG files in questions? > And, are these files critical for building the KiCad package? > > -- > Regards > Carsten > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Updating Paths
Accidental build directory has been removed. Thanks! I'm fine with using any name for the repository that the Protectors of the Footprint Realm (formerly known and the librarian team) decides to use. But as that is a non-user-facing change, I'm not going to push for it. Best- Seth On Sun, Mar 21, 2021 at 11:05 AM Diego Herranz < diegoherr...@diegoherranz.com> wrote: > Hi, Seth > > I can merge the kicad-symbols and kicad-footprints MRs later today when > we're OK to go. > > Reviewing those two, the kicad-symbols MR contains many files. I don't > think that one looks correct. > > Given that we're tidying this up, the repo for 3D models is > kicad-packages3D but the folder is 3dmodels. Would we want to make them > match by naming the folder packages3D or the repo kicad-3dmodels? > > Thanks, > Diego > > > On Sun, 21 Mar 2021, 16:39 Jeff Young, wrote: > >> Woot! >> >> On 21 Mar 2021, at 14:41, Seth Hillbrand wrote: >> >> Hi All- >> >> I've submitted a series of merge requests to coordinate renaming the >> default paths from "library" to "symbols" and from "modules" to >> "footprints" >> >> https://gitlab.com/kicad/code/kicad/-/merge_requests/741 >> https://gitlab.com/kicad/libraries/kicad-footprints/-/merge_requests/2618 >> https://gitlab.com/kicad/libraries/kicad-symbols/-/merge_requests/3229 >> https://gitlab.com/kicad/packaging/kicad-win-builder/-/merge_requests/116 >> >> https://gitlab.com/kicad/packaging/kicad-ubuntu-builder/kicad-daily-package/-/merge_requests/3 >> >> https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/merge_requests/55 >> >> These should be merged at the same time to minimize disruption to our >> daily packages. Please look over any areas that affect you and let me know >> if anything looks amiss. >> >> Also, packagers not in our GitLab repository, please note that this is >> changing (hopefully today). >> >> -Seth >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 >> Long Beach, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > >> >> -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Updating Paths
Hi All- I've submitted a series of merge requests to coordinate renaming the default paths from "library" to "symbols" and from "modules" to "footprints" https://gitlab.com/kicad/code/kicad/-/merge_requests/741 https://gitlab.com/kicad/libraries/kicad-footprints/-/merge_requests/2618 https://gitlab.com/kicad/libraries/kicad-symbols/-/merge_requests/3229 https://gitlab.com/kicad/packaging/kicad-win-builder/-/merge_requests/116 https://gitlab.com/kicad/packaging/kicad-ubuntu-builder/kicad-daily-package/-/merge_requests/3 https://gitlab.com/kicad/packaging/kicad-fedora-builder/-/merge_requests/55 These should be merged at the same time to minimize disruption to our daily packages. Please look over any areas that affect you and let me know if anything looks amiss. Also, packagers not in our GitLab repository, please note that this is changing (hopefully today). -Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Current development status?
On Sat, Mar 20, 2021 at 8:02 AM RigoLigo RLC wrote: > I have a few questions about the current KiCad development. > > 1. new features after feature freeze? > > Most significantly, the separate icon set. While everyone is looking > forward to having this small feature, it's still kinda offending the term > feature "freeze". > On the issue of the new icon set, we explicitly waited for feature freeze before starting this work specifically to allow our design team the full menu list and feature set that needed icons. I expect future explicit icon cleanup to follow the same pattern. > 3. Development iteration... > > Currently KiCad will push big version leaps for all the features > developers add into it. I know it's got reasons (difficulty of maintaining > two branches, plugin API consistency) but a big leap requires a LONG wait. > For OSS users this might not be a big problem but in Chinese community > there are companies that use KiCad as alternatives. > KiCad is still, primarily, community-driven. We are working toward supporting a full-time development team but this requires the business users of KiCad--who depend on its development for their livelihoods--to step up and support the development team. If any companies are interested in discussing how they can help speed up development times, my phone number and contact information are listed below. Regards- Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] schematic.cpp includes sim/ngspice.h and consequently sharedspice.h
I agree that this is one area where we can improve the user experience. By first-class, I mean only that it is an integral part of KiCad that we develop and support. We are no longer in the testing phase where it would make sense to have a conditional compilation. -Seth On Thu, Mar 18, 2021 at 4:51 PM Mark Roszko wrote: > You say it's first class but the spice gui needs alot of loving. The tool > framework is also ducktaped poorly into it. > > On Thu, Mar 18, 2021 at 7:14 PM Seth Hillbrand wrote: > >> Do we still need spice as a build option? It would be nice to bring down >> the number of permutations out there and the SPICE simulator is really a >> first-class KiCad citizen nowadays. >> >> -S >> >> On Thu, Mar 18, 2021 at 4:04 PM Jon Evans wrote: >> >>> Saving in the project file is fine, I just mean if you split out >>> NGSPICE_SIMULATOR_SETTINGS to a different file (not sim/ngspice.h) with no >>> dependencies on ngspice itself, the settings class can be built without >>> ngspice. >>> >>> On Thu, Mar 18, 2021 at 6:57 PM Wayne Stambaugh >>> wrote: >>> >>>> I thought about that but in what context does a simulation make sense >>>> out side of a schematic or a netlist generated from a schematic? I >>>> saved the ngspice simulator settings in the project file because that is >>>> the proper scope of the setting. I really don't see a more logical >>>> place to save the setting. I suppose I could split out the simulator >>>> settings code but it would be awkward at best. >>>> >>>> On 3/18/21 6:42 PM, Jon Evans wrote: >>>> > Wayne, I haven't checked this code carefully but I'd recommend >>>> building >>>> > the settings always, and moving the #ifdef to a different level (i.e. >>>> > make the settings not depend on ngspice) >>>> > >>>> > That way if the same settings files are shared between a build with >>>> > ngspice and a build without, they won't get thrown away. >>>> > >>>> > On Thu, Mar 18, 2021 at 6:37 PM Wayne Stambaugh >>> > <mailto:stambau...@gmail.com>> wrote: >>>> > >>>> > My bad. I forgot the simulator was a build option so I will have >>>> to >>>> > #ifdef the offending settings code. >>>> > >>>> > - Wayne >>>> > >>>> > On 3/18/21 6:02 PM, Eeli Kaikkonen wrote: >>>> > > I have disabled ngspice in cmake settings but in a recent >>>> commit by >>>> > > Wayne #include , which in turn includes >>>> > > ngspice/sharedspice.h, was added to schematic.cpp which makes >>>> > > compilation fail apparently because I don't have ngspice at all. >>>> > > >>>> > > Eeli Kaikkonen >>>> > > >>>> > > ___ >>>> > > Mailing list: https://launchpad.net/~kicad-developers >>>> > <https://launchpad.net/~kicad-developers> >>>> > > Post to : kicad-developers@lists.launchpad.net >>>> > <mailto:kicad-developers@lists.launchpad.net> >>>> > > Unsubscribe : https://launchpad.net/~kicad-developers >>>> > <https://launchpad.net/~kicad-developers> >>>> > > More help : https://help.launchpad.net/ListHelp >>>> > <https://help.launchpad.net/ListHelp> >>>> > > >>>> > >>>> > ___ >>>> > Mailing list: https://launchpad.net/~kicad-developers >>>> > <https://launchpad.net/~kicad-developers> >>>> > Post to : kicad-developers@lists.launchpad.net >>>> > <mailto:kicad-developers@lists.launchpad.net> >>>> > Unsubscribe : https://launchpad.net/~kicad-developers >>>> > <https://launchpad.net/~kicad-developers> >>>> > More help : https://help.launchpad.net/ListHelp >>>> > <https://help.launchpad.net/ListHelp> >>>> > >>>> >>> ___ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 >> Long Beach, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > > > -- > Mark > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] schematic.cpp includes sim/ngspice.h and consequently sharedspice.h
Do we still need spice as a build option? It would be nice to bring down the number of permutations out there and the SPICE simulator is really a first-class KiCad citizen nowadays. -S On Thu, Mar 18, 2021 at 4:04 PM Jon Evans wrote: > Saving in the project file is fine, I just mean if you split out > NGSPICE_SIMULATOR_SETTINGS to a different file (not sim/ngspice.h) with no > dependencies on ngspice itself, the settings class can be built without > ngspice. > > On Thu, Mar 18, 2021 at 6:57 PM Wayne Stambaugh > wrote: > >> I thought about that but in what context does a simulation make sense >> out side of a schematic or a netlist generated from a schematic? I >> saved the ngspice simulator settings in the project file because that is >> the proper scope of the setting. I really don't see a more logical >> place to save the setting. I suppose I could split out the simulator >> settings code but it would be awkward at best. >> >> On 3/18/21 6:42 PM, Jon Evans wrote: >> > Wayne, I haven't checked this code carefully but I'd recommend building >> > the settings always, and moving the #ifdef to a different level (i.e. >> > make the settings not depend on ngspice) >> > >> > That way if the same settings files are shared between a build with >> > ngspice and a build without, they won't get thrown away. >> > >> > On Thu, Mar 18, 2021 at 6:37 PM Wayne Stambaugh > > <mailto:stambau...@gmail.com>> wrote: >> > >> > My bad. I forgot the simulator was a build option so I will have to >> > #ifdef the offending settings code. >> > >> > - Wayne >> > >> > On 3/18/21 6:02 PM, Eeli Kaikkonen wrote: >> > > I have disabled ngspice in cmake settings but in a recent commit >> by >> > > Wayne #include , which in turn includes >> > > ngspice/sharedspice.h, was added to schematic.cpp which makes >> > > compilation fail apparently because I don't have ngspice at all. >> > > >> > > Eeli Kaikkonen >> > > >> > > ___ >> > > Mailing list: https://launchpad.net/~kicad-developers >> > <https://launchpad.net/~kicad-developers> >> > > Post to : kicad-developers@lists.launchpad.net >> > <mailto:kicad-developers@lists.launchpad.net> >> > > Unsubscribe : https://launchpad.net/~kicad-developers >> > <https://launchpad.net/~kicad-developers> >> > > More help : https://help.launchpad.net/ListHelp >> > <https://help.launchpad.net/ListHelp> >> > > >> > >> > ___ >> > Mailing list: https://launchpad.net/~kicad-developers >> > <https://launchpad.net/~kicad-developers> >> > Post to : kicad-developers@lists.launchpad.net >> > <mailto:kicad-developers@lists.launchpad.net> >> > Unsubscribe : https://launchpad.net/~kicad-developers >> > <https://launchpad.net/~kicad-developers> >> > More help : https://help.launchpad.net/ListHelp >> > <https://help.launchpad.net/ListHelp> >> > >> > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] compile warnings about copying loop variable
Almost certainly not. These warnings are that the string is going to be copied one way or another, so we shouldn't be marking them for reference because it is misleading. There may be a way for us to improve the code in places, knowing that the values cannot be referenced but just removing the references will make the code do the same thing, just without the warning. -Seth On Wed, Mar 10, 2021 at 6:13 AM Jonatan Liljedahl wrote: > Would it make any noticeable performance improvements, avoiding all those > string copying? > > On Wed, Mar 10, 2021 at 2:58 PM Seth Hillbrand wrote: > >> That's fun! New warning flags. Those are from -Wrange-loop-analysis >> that is specific to clang. Those of us using gcc won't see them. >> >> They are suggesting minor improvements. You should feel free to submit a >> MR to correct these cases or you can set your flags to >> -Wno-range-loop-analysis to disable them. >> >> Best- >> Seth >> >> On Wed, Mar 10, 2021 at 5:26 AM Jonatan Liljedahl >> wrote: >> >>> I get a lot of compile warnings like this: >>> >>> In file included from /Users/lijon/Coding/kicad/include/dialog_shim.h:29: >>> /Users/lijon/Coding/kicad/include/hashtables.h:87:26: warning: loop >>> variable 'c' is always a copy because the range of type 'const >>> wxString' does not return a reference >>> [-Wrange-loop-analysis] >>> for( const auto& c : aString ) >>> ^ >>> /Users/lijon/Coding/kicad/include/hashtables.h:87:14: note: use >>> non-reference type 'wxUniChar' >>> for( const auto& c : aString ) >>> ^~~ >>> >>> >>> -- >>> /Jonatan >>> http://kymatica.com >>> >>> ___ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 >> Long Beach, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> > > > -- > /Jonatan > http://kymatica.com > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] compile warnings about copying loop variable
That's fun! New warning flags. Those are from -Wrange-loop-analysis that is specific to clang. Those of us using gcc won't see them. They are suggesting minor improvements. You should feel free to submit a MR to correct these cases or you can set your flags to -Wno-range-loop-analysis to disable them. Best- Seth On Wed, Mar 10, 2021 at 5:26 AM Jonatan Liljedahl wrote: > I get a lot of compile warnings like this: > > In file included from /Users/lijon/Coding/kicad/include/dialog_shim.h:29: > /Users/lijon/Coding/kicad/include/hashtables.h:87:26: warning: loop > variable 'c' is always a copy because the range of type 'const > wxString' does not return a reference > [-Wrange-loop-analysis] > for( const auto& c : aString ) > ^ > /Users/lijon/Coding/kicad/include/hashtables.h:87:14: note: use > non-reference type 'wxUniChar' > for( const auto& c : aString ) > ^~~ > > > -- > /Jonatan > http://kymatica.com > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Code execution context
Hi Markus-
We are GPLv3 licensed. So, we are able to link to system libraries that
are installed on users' computers in order to interoperate with
components. But we cannot distribute the system libraries with KiCad. [1]
So, your code snippet would be fine as long as we do not distribute the
TDxNavlib.dll file with KiCad.
Best-
Seth
[1] https://www.gnu.org/licenses/gpl-faq.html#SystemLibraryException
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
On Mon, Mar 1, 2021 at 10:34 PM Markus Bonk
wrote:
> Hi Wayne,
>
> Just to ensure that I understand you correctly:
>
> Code that (in this case _Win32) reads
>
> HRESULT error = S_OK;
> HMODULE h = LoadLibrary("TDxNavlib.dll");
> if (!h) {
> // No SpaceMouse support exit gracefully.
> error = HRESULT_FROM_WIN32(GetLastError());
> }
> else {
> }
>
> where TDxNavlib.dll is delivered as part of the 3Dconnexion device driver
> package is not an issue?
>
> Markus
>
>
>
> Markus Bonk
> Senior Software Engineer
>
> 3Dconnexion GmbH
> Clarita-Bernhard-Str. 18
> 81249 München
> Germany
>
>
>
> markus_b...@3dconnexion.com
> www.3dconnexion.com
>
> Geschäftsführer: Antonio Pascucci
> Sitz der Gesellschaft: München
> Registergericht: München HRB 99232
>
> This email and any files transmitted with are from 3Dconnexion GmbH. The
> contents of this email and any attachments are confidential to the intended
> recipient. They may not be disclosed to or used by or copied in any way by
> anyone other than the intended recipient. If this email is received in
> error, please contact 3Dconnexion GmbH by calling +49 89 8974542-0 and then
> delete it. Please note that neither 3Dconnexion GmbH nor the sender accepts
> any responsibility for viruses and it is your responsibility to scan or
> otherwise check this email and any attachments. Any opinion expressed in
> this email are those of the individual and not necessarily those of
> 3Dconnexion GmbH.
> 3Dconnexion GmbH processes and stores for commercial purposes your
> personal data, collected upon your consent, in accordance with its privacy
> policy available at https://www.3dconnexion.eu/privacy.html, which has
> been drafted in accordance with Regulation (EU) no. 679/2016 and all
> applicable local data protection laws and regulations of the countries
> where the company operates. To revoke your consent or exercise all your
> rights with regards to personal data, please contact us at
> priv...@3dconnexion.com.
> -Original Message-
> From: Kicad-developers 3dconnexion@lists.launchpad.net> On Behalf Of Wayne Stambaugh
> Sent: Thursday, February 25, 2021 6:06 PM
> To: kicad-developers@lists.launchpad.net
> Subject: Re: [Kicad-developers] Code execution context
>
> Any code contributed to KiCad would have to be release under the GPL3+ or
> compatible license to be accepted. Linking to proprietary drivers is not
> an issue since we already link to Windows and MacOS proprietrary libraries
> in order to provide KiCad on those platforms. We just cannot ship those
> libraries. Given that KiCad supports Linux, Windows, and macOS, we would
> prefer to provide a comparable experience on all supported platforms.
>
> Cheers,
>
> Wayne
>
> On 2/25/21 9:45 AM, Jon Evans wrote:
> > As long as the experience is the same on all platforms (Win, Mac,
> > Linux) and KiCad does not require any proprietary libraries to
> > compile, I think it is up to Wayne whether or not an optional
> > dependency on a proprietary library on Windows is acceptable.
> >
> > But, I would like to hear from Markus on the topic first -- if other
> > software is successfully using websockets to provide a good interface
> > to 3dconnexion hardware on Windows, maybe it is not as bad as you fear?
> >
> > -Jon
> >
> > On Thu, Feb 25, 2021 at 9:38 AM Mark Roszko > <mailto:mark.ros...@gmail.com>> wrote:
> >
> > On another note, I personally am not a fan of websockets usage
> > locally on Windows. In corporate environments there's going to be
> > hell with security software interfering and in general it's fragile.
> >
> > I personally would rather just link against the 3dconnexion library
> > directly. We have the MSVC builds now, we can compile against MSVC
> > built libraries no problem. MSYS2 builds would just remain without
> it.
> >
> > But just my opinion on this.
> >
> > On Thu, Feb 25, 2021 at 9:32 AM Jon Evans > <mailto:j...@craftyjon.com>> wrote:
> >
> > Th
Re: [Kicad-developers] Launch Pad ???
Not anymore. We've fully moved the project GitLab. You can find the tracked bugs at https://gitlab.com/kicad/code/kicad/issues Best- Seth On Fri, Feb 19, 2021 at 11:24 AM Christopher Buckley < mallardproducti...@yahoo.com> wrote: > Are you guys still using launchpad for bug reporting / tracking? > > Latest bug I've found there is for June 2020... > > Am searching through the inventory... > > C > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] kicad last stable BOM error ubuntu
Hi Marco- Error 40 is a key error from Python, so my guess would be that the user is feeding a bad xml file. -Seth On Fri, Feb 19, 2021 at 3:23 AM Marco Ciampa wrote: > > https://stackoverflow.com/questions/66151510/kicad-error-40-when-exporting-bom-using-python > > any hint? > > -- > > Saluton, > Marco Ciampa > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] PCB Calculator text problem
You can click Help->Report Bug Thanks- Seth On Fri, Feb 19, 2021 at 9:43 AM David wrote: > Hi, > > Just to let you know that there is a problem with the text on the first > column fourth row of the board classes tab of the PCB Calculator (Please > see attached screenshot). The text overflows the box. > > I don't know how to report bugs so thought I'd mention it here. Thanks. > > Thanks. > > David. > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Bug Reports???
This will get you where you need to be. https://go.kicad.org/bug Depending on what kind of bug you are reporting, we have a couple of different places. Welcome back! -Seth On Tue, Feb 16, 2021 at 11:08 AM Christopher Buckley < mallardproducti...@yahoo.com> wrote: > Okay, it's been like two years since I've been on here cause I haven't had > time to do anything in my 7 days per week, 14 hour per day trucking job I > had to take for the sake of survival. > > So, I can't remember if there's a formal bug reporting system or just > submit to this list. > > I think it's the latter > > Anyone? :) > > THX - C > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Linux Packaging heads up
This is a heads up for our Linux packagers that the launcher locations have changed in the master branch. You will now find the .desktop launcher files in the build directory, under `resources/linux/launchers/` -Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Questions to the QA code
Hi Sylwester- I haven't used HippoMocks but in general, adding QA tests is always welcome as long as they run as expected under the Fedora docker we use for online QA with GitLab. The downside of HippoMocks from what I can gather is that the project appears abandoned. If I'm incorrect here, can you link to the current repository/documentation? Thanks- Seth On Fri, Jan 15, 2021 at 2:49 PM Sylwester Kocjan wrote: > Hello, > > I have two questions regarding QA code for KiCad and I'd like to ask for > your comments about them: > > 1. I reviewed contents of qa directory in KiCad repo and I saw some issues > that can be fixed. >Could you please take a look at the summary and let me know if they are > valid: > > > https://docs.google.com/spreadsheets/d/14QAy9rRIHqRr4YuXfQO2GicURAG1BgJmwKe7B1H6xXI/edit#gid=326687467 > > 2. What do you think about adding mocking library to the KiCad code? I > found that PGM object is mocked few times > >https://gitlab.com/kicad/code/kicad/-/issues/4446#note_342766728 > >A libary for creating mocks would simplify creting the tests. In this > MR and commit: > >https://gitlab.com/kicad/code/kicad/-/merge_requests/542 > > https://gitlab.com/kicad/code/kicad/-/merge_requests/542/diffs?commit_id=b7b401d7128057831c049a723ffc895453d65a0e > >there is added HippoMocks, a single-header mocking tool and it does > it's job. >If that's ok, it could help to get rid of these duplicated mocks (maybe > even hand-written mocks at all). > > Best regards, > Sylwester > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Nightly Ubuntu packages - 3d models path problem
Hi Mark-
Please report a bug to our issue tracker at
https://gitlab.com/kicad/code/kicad/-/issues
The updated Ubuntu package should have included the updated environmental
variable. If it didn't, that would be a problem.
-Seth
On Tue, Jan 5, 2021 at 8:35 AM Mark Robson wrote:
> Hi,
>
> I've been testing the amazing nightly builds on Ubuntu 20 for some time
> now - but now the 3d models are gone on newly placed footprints.
>
> I think this is probably due to the model path changing, for example
>
> A previously placed 0603 capacitor has 3d model path:
>
> ${KISYS3DMOD}/Capacitor_SMD.3dshapes/C_0603_1608Metric.wrl
>
> Which works ok, but a newly placed 0603 has
>
> ${KICAD6_3DMODEL_DIR}/Capacitor_SMD.3dshapes/C_0603_1608Metric.wrl
>
> So it seems it's a change to this variable name KICAD6_3DMODEL_DIR
>
> Is this a packaging problem? Or do I need to reset some settings in my
> setup?
>
> I didn't report this as a bug because I don't think it's the Kicad code's
> fault.
>
> Any idea how I can fix it or who I need to tell?
>
> Regards
>
> Mark
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483
Long Beach, CA
www.kipro-pcb.comi...@kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Hello Carsten- We agree with you. This is why we moved the generated files to the build tree and out of the source tree. But legacy files in the source tree are still considered first, so older build directories need the fix-up that Jeff mentioned. We might be able to get around this by changing the .gitignore but we haven't tested that. Regards- Seth On Sat, Jan 2, 2021 at 7:07 AM Carsten Schoenert wrote: > Hello Jeff, > > Am 02.01.21 um 15:45 schrieb Jeff Young: > > Hi Carsten, > > > > Known problem when building 5.99 in a tree that used to hold 5.1. > > > > Try: > > > > cd include > > rm *_lexer.h > ahh, yes that fixed the build. > > But I see the build of additional required files within the source tree > rather as issue if I build out of tree. Is this behavior a problem of > cmake or more a miss configuration of the build controlling? > > -- > Mit freundlichen Grüßen > Carsten Schönert > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Please change name from David Briscoe to David J S Briscoe in help > About KiCad > translators > Others
Done. Thank you for your contributions! Best- Seth On Fri, Dec 25, 2020 at 1:43 AM David J S Briscoe < da...@djsbriscoe.vispa.com> wrote: > Hello, > Could someone please change my name from > > David Briscoe > > To > > David J S Briscoe > > in > > Help > About KiCad > Translators > Others > > This is to distinguish my self from other people with a similar name and > to avoid any confusion. > > Please do this when it is convenient. Thanks. > > Regards, > > David J S Briscoe > > Hertfordshire, UK. > > PS I can do this myself if you could tell me how. Or maybe it would be > quicker for someone who knows what they are doing. > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 5.1.9 tagged for release
We'll be home in time for Life Day! On Tue, Dec 22, 2020 at 2:05 PM Jon Evans wrote: > The KiCad Christmas special? > > On Tue, Dec 22, 2020 at 5:02 PM Nick Østergaard wrote: > >> I don't think we need that long. Everything seems to be tagged. I have >> triggered the windows build and it should just be a simple pkgver bump >> for macos and ubuntu ppa as well. >> >> >> On Tue, 22 Dec 2020 at 21:14, Wayne Stambaugh >> wrote: >> > >> > 5.1.9 has been tagged for release. Please tag the library, doc, and >> > translation repos for release. I don't think we have much in the way of >> > changes there so is a week to get these repos tagged and another week to >> > get packages built for a January 5th release work for everyone? Please >> > let me know an I will adjust the release schedule accordingly. As >> > always, thank you to everyone who made this possible. >> > >> > Cheers, >> > >> > Wayne >> > >> > ___ >> > Mailing list: https://launchpad.net/~kicad-developers >> > Post to : kicad-developers@lists.launchpad.net >> > Unsubscribe : https://launchpad.net/~kicad-developers >> > More help : https://help.launchpad.net/ListHelp >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Tiling Algorithm Improvements
Hi Alex- You are probably not getting many replies to this message as we're not quite sure what aspect of KiCad you are looking at. We might be able to comment better with a bit more detail. Best- Seth On Fri, Nov 20, 2020 at 1:03 AM Alex wrote: > Hi everyone, > > I started doing some C++11 modernization and Standard Library insertion in > the rectangular placement segment of the PCBNew, and in the process I went > down the rabbit hole of documentation for the algorithm. Out of curiosity I > adjusted the Greater algorithm from only sorting on the longest side, to > first sorting by longest side, and then sorting by shortest side. > > I found that this small adjustment seemed to increase packing density > enough that when presented with 500 rectangles of randomly generated size > of (15x15) - (85x85) fit into surfaces of (255 x 255), the total number of > required surfaces went from ~28 to ~26. The catch is that the initial > sorting of the algorithm takes a little longer. > > Always the skeptic, I would like to know if there is currently a > methodology or recommendation for incorporating a benchmark test for both > space and time performance. At minimum, I can use Google Benchmark, but I'd > like to know if I should place the tests in the same folder, or if there is > another place for this kind of stuff. > > Thanks, > Alex > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] KiCad GitHub plugin opinions
Hi Folks- We are currently discussing the removal of the GitHub plugin from KiCad library management. Didn’t know that KiCad had a GitHub plugin? Then this will not affect you at all. We’re looking for users that actively use the GitHub plugin for their professional work and would be affected by its removal. If this is you, please reply here with how you are using the plugin and we’ll see what we can do to support your use case going forward. Thanks- Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Lack of CJK /Full width symbols fonts
Hi Rigo- Yes, we can add the additional symbols. I still need to regenerate the CJK symbols to be wider and I'm happy to work to add symbols as well. Can you please open an issue at GitLab for this? This will help me to track the remaining issues. Best- Seth On Fri, Oct 23, 2020 at 3:15 AM RigoLigo RLC wrote: > Hi, > > I have just discovered that KiCad has got Chinese characters included in > the newstroke fonts, but no symbols, therefore a Chinese user must switch > to English mode to enter symbols and punctuations. > > U+3000~303F and U+FF00~FFEF are where those symbols are located. I'm > wondering if those symbols can be added to the fonts in the same way as the > Chinese characters, despite v6 is already at feature freeze (this really > annoys Chinese users though). > > Regards, > Rigo > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] KiCAD nightly builds for Arch
Hi Rachel and Nick- Nick is the current maintainer of kicad-git in AUR. But this isn't currently tracked in our packaging repositories. Because of this, I can see why suggesting a new package to the list would make sense. There is certainly room in the packaging subproject for the Arch packages. I've looked them both over and the two packages take different approaches. There may be good reasons for Arch users to prefer to use one over the other. Ideally, we would keep a single "official" AUR set. But this should be in the packaging project. So, for now, let's bring both package sets into the kicad-arch packaging group[1] and we can work out the best way to support our arch users. Rachel, please send me your GitLab username and the link to the git repository where you are currently keeping your scripts (or the tarball if there's no repository yet). Nick, I think you have permission in the packaging group to create the kicad-git repository. Thank you again Rachel for offering to help contribute to KiCad. We look forward to working with you. -Seth [1] https://gitlab.com/kicad/packaging/kicad-arch On Fri, Oct 23, 2020 at 4:27 AM Nick Østergaard wrote: > Hi Rachel > > I wonder why you wouldn't just propose the changes to the maintainer of > kicad-git in AUR. > > I didn't review your scripts, but that is where I woukd start. > > > fre. 23. okt. 2020 12.32 skrev : > >> Hi folks, >> >> I recently got fed up enough of not having a parallel installable >> nightly for Arch that I could use at the same time as release KiCAD so >> I could toy with new features and yet still keep my main projects in >> 5.x format, so I put in the effort to create a set of PKGBUILD files >> for such a nightly. >> >> The result of this are the two sets of packages on the AUR known as >> kicad-nightly and kicad-library-nightly. However, updating these is >> presently a touch unwieldy and I wish to put together a meta-repo with >> my scripts for updating the packages. >> >> To this end, I'm seeking a packaging repo on GitLab such as >> `kicad-arch-builder`, and possibly a couple of mirroring repos for >> each of the two AUR packages, if that is possible please? >> >> Many thanks, >> Rachel. >> >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Some V6 features
Hi Andrew- First, my apologies for the lateness of this reply. I've unfortunately fallen a bit behind in my e-mails and yours was set aside to respond to but I hadn't yet gotten around to it. 1. I haven't published the api for this yet. The basic work is bringing eeschema into the plugin architecture and getting both old and new API to compile and work from the same codebase. I'm not sure who moved the eeschema api to v7 but it shouldn't have. 2. As you'll recall, I mentioned that the plugin manager did need to follow our basic goals pretty closely. If your development work has done that, then we may be able to incorporate some of your work into the release. If you send me a link to the branch where you are working on it, we can look together to see what can get merged into the manager. -Seth On Sat, Oct 17, 2020 at 9:47 AM Andrew Lutsenko wrote: > Hi all, > > There were a couple features mentioned in KiCon 2020 q session that are > apparently planned to be in v6 but it was a surprise for me since I'm > closely following these and even directly involved (or I thought I was) in > one of them. > > I'd appreciate some info. I know Seth is working on these but I can't seem > to reach him by email so I'm trying the broader mailing list. > > 1. The stable python API. Is there a spec for it? I didn't see a > discussion for it on the mailing list. As an author of one of the popular > plugins I'd like to start looking into it early and provide feedback if > possible. > Also I'm assuming this is about pcbnew api only, as eeschema api was > pushed to 7.0 https://gitlab.com/kicad/code/kicad/-/issues/2077 > > 2. Plugin manager. If you recall last year I started a design doc for my > vision of this feature and I admittedly dropped the ball on it for a while > and, well, 2020 happened. But I've been chipping away at it and got pretty > far. I even have a gui mock up almost ready. > Link to the doc can be provided to interested parties but I was asked to > not share it broadly until it gets initial approval by the core team. > > Hearing that you are close to merging your own implementation means I > shouldn't continue with my work? I'm assuming you are close because it is > supposedly on ff-exception list. > Is the documentation for your implementation available somewhere? Again, > it was not mentioned on the mailing list so maybe I'm not subscribed to the > right sources. > > Regards, > Andrew Lutsenko > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Translations Locations
Hi All- Currently, and for some time, our translations of KiCad have lived in a separate repository from the codebase. I'd like to merge the translations into the KiCad codebase in a subdirectory called "translation" This will allow our translators to only have to check out a single repository instead of two. This will also allow us to begin using an online collaborative translation platform called Weblate[1] that is used by Fedora, openSUSE, LibreOffice, etc. The online translation system is optional, translators are not required to use it, but it does add a number of useful features and quality checks. Does anyone have objections to moving the i18n repository into a subdirectory of the source code repository or know of a reason why we shouldn't? Best- Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] New lead developer announcement.
Welcome Mark and Thomas! I look forward to working with you to make KiCad even better. We're fortunate to have you on board. Best- Seth On Wed, Oct 7, 2020 at 6:24 AM Wayne Stambaugh wrote: > I am happy to announce that Mark Roszko and Thomas Pointhuber have > accepted invitations to the KiCad lead development team. Mark and > Thomas have be long time contributors to the KiCad project and I look > forward to their contributions as lead developers. Please join me in > congratulating them in their new roles. > > Cheers, > > Wayne > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Version 6 feature freeze.
Hooray! That is great news Wayne! And don't forget to join us tomorrow for the KiCad v6 Open Chat. All the details are at https://kicad-kicon.com/ You can submit your questions, see everyone's quarantine digs and get some neat demos of the new v6 features. On to spit and polish! Best- Seth On Fri, Oct 2, 2020 at 3:46 PM Wayne Stambaugh wrote: > As of now, the development branch of KiCad is closed for new feature > merges except for the items on the exception list. A new feature freeze > exception tag has been created to tag existing merge requests that fall > into the exception category. All new feature merge requests will be > pushed back until the main repo is opened for version 7 development. > The focus will now be on getting ready to release version 6 early in > 2021. Thank you to everyone who made this possible. > > Cheers, > > Wayne > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 3D-Viewer: limit scale to positive values?
The document I linked is the HTML version of the ISO/IEC standard as published by the Web3D consortium (previously known as the VRML consortium). There is no textual difference between the PDF of the ISO document and the webpage. If Wings3D doesn't use this, then it makes sense that we may have originally chosen the unit used in Wings. But that doesn't mean that we need to continue this practice. -Seth On Tue, Sep 29, 2020 at 4:08 PM Cirilo Bernardo wrote: > Hi Seth, > What you have on the w3 site is essentially an interpretation by the > author of that page; > the spec referred to reads differently. At any rate, that doesn't change > the fact that existing > software for creating VRML (including Wings3D that many KiCad users used > long ago) > don't use a unit of 1m - and it all really comes back to the spec being > poorly worded and > various implementers interpreting it differently. If it sounds like I'm > being pedantic it's > because I've implemented too many standards specs over the years and > suffered > poor implementations even on points where I thought the language was clear. > > > On Wed, Sep 30, 2020 at 8:58 AM Seth Hillbrand wrote: > >> I don't follow your statement. The standard says "ISO/IEC 14772 defines >> the unit of measure of the world coordinate system to be metres." There is >> no ambiguity here, so I would feel comfortable with saying that KiCad also >> defines the VRML standard unit to be meters (metres). >> >> As to the file savings, this is easily addressed by defining a single, >> new coordinate system in inches or microns that scales the global system. >> All units in the file are then in scaled coordinates. >> >> -Seth >> >> On Tue, Sep 29, 2020 at 3:50 PM Cirilo Bernardo < >> cirilo.berna...@gmail.com> wrote: >> >>> That's the same reference - the problem is with the wording 'is', not >>> 'shall' or 'must be'. >>> The reality is that for every tool you pick that generates VRML models, >>> the unit used is >>> anyone's guess. On top of that, for KiCad's purposes using meters would >>> actually >>> be a nuisance and would unnecessarily bloat the VRML file. Many parts >>> often have >>> features on the order of 10 microns; using mm or even 0.1 inches shaves >>> off a lot of >>> zeroes (or repetitive exponents). >>> >>> Cirilo >>> >>> >>> On Wed, Sep 30, 2020 at 7:40 AM Seth Hillbrand >>> wrote: >>> >>>> >>>> >>>> On Tue, Sep 29, 2020 at 2:33 PM Cirilo Bernardo < >>>> cirilo.berna...@gmail.com> wrote: >>>> >>>>> Oh, I wish VRML specified meters - that would have made life much >>>>> easier. >>>>> >>>> >>>> See >>>> https://www.web3d.org/documents/specifications/14772/V2.0/part1/concepts.html#4.4.5 >>>> This reads pretty clear to me. Was there a different reference you are >>>> referring to? >>>> >>>> -Seth >>>> >>>> -- >>>> [image: KiCad Services Corporation Logo] >>>> Seth Hillbrand >>>> *Lead Developer* >>>> +1-530-302-5483 <+12126039372> >>>> Davis, CA >>>> www.kipro-pcb.comi...@kipro-pcb.com >>>> >>> >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 <+12126039372> >> Davis, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 3D-Viewer: limit scale to positive values?
I don't follow your statement. The standard says "ISO/IEC 14772 defines the unit of measure of the world coordinate system to be metres." There is no ambiguity here, so I would feel comfortable with saying that KiCad also defines the VRML standard unit to be meters (metres). As to the file savings, this is easily addressed by defining a single, new coordinate system in inches or microns that scales the global system. All units in the file are then in scaled coordinates. -Seth On Tue, Sep 29, 2020 at 3:50 PM Cirilo Bernardo wrote: > That's the same reference - the problem is with the wording 'is', not > 'shall' or 'must be'. > The reality is that for every tool you pick that generates VRML models, > the unit used is > anyone's guess. On top of that, for KiCad's purposes using meters would > actually > be a nuisance and would unnecessarily bloat the VRML file. Many parts > often have > features on the order of 10 microns; using mm or even 0.1 inches shaves > off a lot of > zeroes (or repetitive exponents). > > Cirilo > > > On Wed, Sep 30, 2020 at 7:40 AM Seth Hillbrand wrote: > >> >> >> On Tue, Sep 29, 2020 at 2:33 PM Cirilo Bernardo < >> cirilo.berna...@gmail.com> wrote: >> >>> Oh, I wish VRML specified meters - that would have made life much >>> easier. >>> >> >> See >> https://www.web3d.org/documents/specifications/14772/V2.0/part1/concepts.html#4.4.5 >> This reads pretty clear to me. Was there a different reference you are >> referring to? >> >> -Seth >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 <+12126039372> >> Davis, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 3D-Viewer: limit scale to positive values?
On Tue, Sep 29, 2020 at 2:33 PM Cirilo Bernardo wrote: > Oh, I wish VRML specified meters - that would have made life much easier. > See https://www.web3d.org/documents/specifications/14772/V2.0/part1/concepts.html#4.4.5 This reads pretty clear to me. Was there a different reference you are referring to? -Seth -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 3D-Viewer: limit scale to positive values?
I've never seen another package use VRML. Everyone uses STEP. I suspect if we were implementing this today, we would look at the tradeoff on support/benefit for VRML and limit ourselves to STEP as well. I like Ian's suggestion for unit options. -Seth On Tue, Sep 29, 2020 at 10:22 AM Jon Evans wrote: > Do other EDA tools allow model scaling? Altium doesn't even allow VRML > import in the first place. > > On Tue, Sep 29, 2020 at 1:10 PM Seth Hillbrand wrote: > >> Well, we've backed ourselves into a bit of a corner. VRML is specified >> in meters, so if we're assuming inches, we're a bit off in left field. But >> do we need three separate scale parameters? We could reduce to 1, correct? >> >> In the official footprint library, we have 7 footprints that specify >> non-unity scaling. (Banana_Jack_[1-3], NS-Tech_Grove_1x04, Fuse_Blade_ATO, >> Fuse_Blad_Mini, Oscillator_SMD_TXC0_G158). >> >> -Seth >> >> >> >> >> On Tue, Sep 29, 2020 at 9:30 AM Ian McInerney >> wrote: >> >>> We can't remove the scaling option until we make the VRML importer >>> handle proper unit selection. I have routinely run into the case where I go >>> OpenSCAD -> Wings3D -> KiCad and design a model using mm in OpenSCAD >>> because it makes for easier computations (all the datasheet values are >>> nicely given in mm) and then have to apply a scaling factor of 0.3937 to >>> all the axes in KiCad to make it the proper size because we seem to have a >>> hardcoded assumption about what unit system the VRML file is in. >>> >>> In fact, the KLC says: WRL files do not specify absolute dimensions. >>> KiCad normalizes model parameters to units of inches and the internal units >>> (dimensionless) of the WRL model must be scaled accordingly. >>> >>> -Ian >>> >>> On Tue, Sep 29, 2020 at 4:50 PM Seth Hillbrand >>> wrote: >>> >>>> There has been some discussion to removing the scale option here >>>> altogether. The logic being that if you need the model scaled, you should >>>> be doing this in your solid CAD not in your electronic CAD. I have come >>>> around to this idea and it might be worth implementing rather than doing >>>> the scale limiting. >>>> >>>> -Seth >>>> >>>> On Tue, Sep 29, 2020 at 4:52 AM Mário Luzeiro wrote: >>>> >>>>> Hi all, >>>>> >>>>> I'm wondering if it is safe to limit the scale of shapes to be >>>>> positive values? >>>>> >>>>> Applying negative scales will cause inverted shapes and render issues >>>>> on the models. >>>>> >>>>> Could be that anyone in the world is using negative scale values? >>>>> or should be safe to limit it? >>>>> >>>>> This is related with this issues: >>>>> https://gitlab.com/kicad/code/kicad/-/issues/5817 >>>>> >>>>> Mario >>>>> ___ >>>>> Mailing list: https://launchpad.net/~kicad-developers >>>>> Post to : kicad-developers@lists.launchpad.net >>>>> Unsubscribe : https://launchpad.net/~kicad-developers >>>>> More help : https://help.launchpad.net/ListHelp >>>>> >>>> >>>> >>>> -- >>>> [image: KiCad Services Corporation Logo] >>>> Seth Hillbrand >>>> *Lead Developer* >>>> +1-530-302-5483 <+12126039372> >>>> Davis, CA >>>> www.kipro-pcb.comi...@kipro-pcb.com >>>> ___ >>>> Mailing list: https://launchpad.net/~kicad-developers >>>> Post to : kicad-developers@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~kicad-developers >>>> More help : https://help.launchpad.net/ListHelp >>>> >>> >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 <+12126039372> >> Davis, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 3D-Viewer: limit scale to positive values?
Well, we've backed ourselves into a bit of a corner. VRML is specified in meters, so if we're assuming inches, we're a bit off in left field. But do we need three separate scale parameters? We could reduce to 1, correct? In the official footprint library, we have 7 footprints that specify non-unity scaling. (Banana_Jack_[1-3], NS-Tech_Grove_1x04, Fuse_Blade_ATO, Fuse_Blad_Mini, Oscillator_SMD_TXC0_G158). -Seth On Tue, Sep 29, 2020 at 9:30 AM Ian McInerney wrote: > We can't remove the scaling option until we make the VRML importer handle > proper unit selection. I have routinely run into the case where I go > OpenSCAD -> Wings3D -> KiCad and design a model using mm in OpenSCAD > because it makes for easier computations (all the datasheet values are > nicely given in mm) and then have to apply a scaling factor of 0.3937 to > all the axes in KiCad to make it the proper size because we seem to have a > hardcoded assumption about what unit system the VRML file is in. > > In fact, the KLC says: WRL files do not specify absolute dimensions. KiCad > normalizes model parameters to units of inches and the internal units > (dimensionless) of the WRL model must be scaled accordingly. > > -Ian > > On Tue, Sep 29, 2020 at 4:50 PM Seth Hillbrand wrote: > >> There has been some discussion to removing the scale option here >> altogether. The logic being that if you need the model scaled, you should >> be doing this in your solid CAD not in your electronic CAD. I have come >> around to this idea and it might be worth implementing rather than doing >> the scale limiting. >> >> -Seth >> >> On Tue, Sep 29, 2020 at 4:52 AM Mário Luzeiro wrote: >> >>> Hi all, >>> >>> I'm wondering if it is safe to limit the scale of shapes to be positive >>> values? >>> >>> Applying negative scales will cause inverted shapes and render issues on >>> the models. >>> >>> Could be that anyone in the world is using negative scale values? >>> or should be safe to limit it? >>> >>> This is related with this issues: >>> https://gitlab.com/kicad/code/kicad/-/issues/5817 >>> >>> Mario >>> ___ >>> Mailing list: https://launchpad.net/~kicad-developers >>> Post to : kicad-developers@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~kicad-developers >>> More help : https://help.launchpad.net/ListHelp >>> >> >> >> -- >> [image: KiCad Services Corporation Logo] >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 <+12126039372> >> Davis, CA >> www.kipro-pcb.comi...@kipro-pcb.com >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] 3D-Viewer: limit scale to positive values?
There has been some discussion to removing the scale option here altogether. The logic being that if you need the model scaled, you should be doing this in your solid CAD not in your electronic CAD. I have come around to this idea and it might be worth implementing rather than doing the scale limiting. -Seth On Tue, Sep 29, 2020 at 4:52 AM Mário Luzeiro wrote: > Hi all, > > I'm wondering if it is safe to limit the scale of shapes to be positive > values? > > Applying negative scales will cause inverted shapes and render issues on > the models. > > Could be that anyone in the world is using negative scale values? > or should be safe to limit it? > > This is related with this issues: > https://gitlab.com/kicad/code/kicad/-/issues/5817 > > Mario > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Linux support for wxGLCanvas and Wayland/EGL
It's definitely good to have a backup. That last wx packaging fiasco with the halfway switch from gtk2 to gtk3 was not pleasant. -S On Mon, Sep 28, 2020 at 3:43 PM Ian McInerney wrote: > The upcoming wxWidgets 3.1.5 release has added a new backend supporting > Wayland/EGL to the wxGLCanvas that we use for displaying the OpenGL drawing > canvas. This backend appears to be the new default backend for wxGTK unless > it is explicitly disabled on the wxWidgets configure step (you > pass --disable-glcanvasegl to the configure script). It is also not > currently possible to change this backend at runtime. This means that we > will be forced to use whatever the distro-defaults are for the canvas > backend once wx 3.1/3.2 is being used in the wild. > > I was just working with it some, and our main bottleneck for supporting it > natively is currently the GLEW dependency we have in our rendering code. > GLEW requires a compile-time selection of either X11 or EGL backends, and > all distributions seem to only ship a library built for the X11 backend. > > I have done some experimenting, and building a version of GLEW that is > meant for EGL is fairly simple and uses a single C file and the public > headers. It can be compiled into a static library that we then link into > our code, so we don't actually need to bundle a shared library. My thinking > currently is that we provide these GLEW files in the thirdparty directory, > and only use them if a specific compile-time option to use EGL is provided. > That will mean that linux packaging will still use distro-provided GLEW > libraries when using the X11 backend, and if the distro can supply an > EGL-capable GLEW version we can try to use that (I am not sure how the > distros will manage this though). > > -Ian > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] string translation error
Should be fixed
On Sat, Sep 19, 2020, 8:55 AM Marco Ciampa wrote:
> On Mon, Sep 14, 2020 at 07:39:08PM +0200, Nick Østergaard wrote:
> > I think JP fixed this in
> >
> https://gitlab.com/kicad/code/kicad/-/commit/ff0a728753adf701a9d723b9f2b6484114e5dff1
> >
> > On Mon, 14 Sep 2020 at 08:11, Marco Ciampa wrote:
> >
> > > See the message:
> > >
> > > pcbnew/drc/drc_engine.cpp:492: warning: Empty msgid. It is reserved by
> > > GNU gettext:
> > > gettext("") returns the header
> > > entry with
> > > meta information, not the empty
> > > string.
> > >
> > > TIA
> > >
>
> Just a heads up,
> it looks like it popped up again...
>
> --
>
> Saluton,
> Marco Ciampa
>
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Some linker errors, and question about qa
You might have a dirty build. I'm not seeing this error locally. Can you
try `make clean` before you re-make?
-Seth
On Mon, Sep 14, 2020 at 1:26 PM Eeli Kaikkonen
wrote:
> I get some linker errors:
>
> [3/3] Linking CXX executable qa/drc_proto/drc_proto
> FAILED: qa/drc_proto/drc_proto
> ...
> /usr/bin/ld:
> qa/drc_proto/CMakeFiles/drc_proto.dir/__/pcbnew_utils/board_file_utils.cpp.o:
> in function `KI_TEST::DumpBoardToFile(BOARD&,
> std::__cxx11::basic_string,
> std::allocator > const&)':
> /work/ohjelmointi/kicad/kicad-master/qa/pcbnew_utils/board_file_utils.cpp:40:
> undefined reference to `PCB_IO::PCB_IO(int)'
> /usr/bin/ld:
> /work/ohjelmointi/kicad/kicad-master/qa/pcbnew_utils/board_file_utils.cpp:41:
> undefined reference to `PCB_IO::Save(wxString const&, BOARD*, PROPERTIES
> const*)'
> /usr/bin/ld:
> /work/ohjelmointi/kicad/kicad-master/qa/pcbnew_utils/board_file_utils.cpp:40:
> undefined reference to `PCB_IO::~PCB_IO()'
> /usr/bin/ld:
> /work/ohjelmointi/kicad/kicad-master/qa/pcbnew_utils/board_file_utils.cpp:40:
> undefined reference to `PCB_IO::~PCB_IO()'
> /usr/bin/ld: common/libpcbcommon.a(io_mgr.cpp.o): in function
> `{lambda()#2}::operator()() const':
> /work/ohjelmointi/kicad/kicad-master/pcbnew/io_mgr.cpp:209: undefined
> reference to `PCB_IO::PCB_IO(int)'
>
>
>
> What might be the reason?
>
> BTW, why does it link anything under qa at all while I don't have
> KICAD_BUILD_QA_TESTS enabled? I'm not sure what the qa subdir should do,
> but I don't think I need or want it.
>
> Eeli Kaikkonen
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
>
--
[image: KiCad Services Corporation Logo]
Seth Hillbrand
*Lead Developer*
+1-530-302-5483 <+12126039372>
Davis, CA
www.kipro-pcb.comi...@kipro-pcb.com
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Pad SHAPE, SH_RECT vs SH_SIMPLE
That might happen if the shape cache is dirty. You can call 'pad->IsDirty()' to check. One related question: if you get the SH_SIMPLE and check the coordinates, do they form a rectangle with angle 0? -Seth On Sun, Sep 6, 2020 at 3:52 PM Mário Luzeiro wrote: > Hi all, > > I noticed that (if I looked correctly) that there are some Pads, that are > marked as Rectangles but its shape Type is set to be SH_SIMPLE (both angles > are 0) > So I got some rectangles that are SH_RECT and other rectangles are > SH_SIMPLE > > Could some one clarify this differences and what originate it? > > Mario > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] D_PAD contributing to solder mask
Hi Mário- Jeff is correct. You can also use the IsPadOnLayer() for this purpose because it defaults to IsOnLayer() when the pad hasn't been automatically removed. IsOnLayer will tell you if the object passes through the copper layer, or has a technical layer selected. IsPadOnLayer will return false if the copper annulus of a through-hole pad has been removed by the 'Remove unconnected pads' logic Otherwise, it will return the result of `IsOnLayer()` It's good practice to use IsPadOnLayer for D_PADs unless you want to know if the pad passes through a layer. Best- Seth On Sun, Sep 6, 2020 at 11:13 AM Mário Luzeiro wrote: > I was using IsPadOnLayer .. > What should be the differences for use IsPadOnLayer vs IsOnLayer ? > > > From: Jeff Young > Sent: 06 September 2020 19:04 > To: Mário Luzeiro > Cc: kicad-developers@lists.launchpad.net > Subject: Re: [Kicad-developers] D_PAD contributing to solder mask > > IsOnLayer( F_Mask ) || IsOnLayer( B_Mask ) > > > > On 6 Sep 2020, at 18:43, Mário Luzeiro mrluze...@ua.pt>> wrote: > > Hi all, > what is the correct way to check that a D_PAD is contributing to solder > mask? > eg: on the Pad Properties editor, the F.Mask or B.Mask is ticked.. > > Mario > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net kicad-developers@lists.launchpad.net> > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] DXF export generates non-closed polygons, and other problems interchanging data w/ Sonnet
It would be helpful if you could generate a minimal example file where a polygon is not closed and create a bug report with that file. To my knowledge, polygons are closed in the dxf plotter (at least the code is written in such a way as to attempt to do this). We do not yet support real drill outlines in the plotter. We've added this to the printer and could probably do the same for the plotter. Here, again it will be helpful to submit a bug report requesting this feature. Multiple layers in a single dxf has already been requested but has not yet been implemented (https://gitlab.com/kicad/code/kicad/-/issues/2526) Best- Seth On Wed, Sep 2, 2020 at 4:17 PM Andrew Zonenberg wrote: > Hi, > > Kicad's DXF export seems to be broken, causing many tools (such as the > Sonnet field solver) to not import layouts correctly. > I contacted Sonnet support and they did some digging; it seems like > KiCAD is producing malformed DXFs that have non-closed polygons in them. > > I've also encountered two other problems getting KiCAD designs into Sonnet: > > 1) Sonnet's DXF import expects a *single* DXF, with one drawing layer > per PCB/via layer. KiCAD generates one DXF per layer and I don't think > there is currently a way to do a multilayer export. This isn't a fatal > problem as I can just do multiple imports, but it's annoying. > > 2) More seriously, There does not seem to be any way to get via drill > *outlines* in DXF format. The "drill map" file just has an X at each via > location which is useless when trying to import layout into an external > tool. > > Anybody have suggestions on how to proceed, or interested in helping to > fix this? I'm not super familiar with the DXF file format although back > in the v4.x days I did do some work on the microvia/blind via Excellon > drill export code so I've done at least a little bit of work there. > > Andrew > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Evaluating cross-selection between the 3D-Viewer and Pcbnew
I'll second what Ian has said with one caveat. When we replace the Kiway
interface in v7, we'll be ripping out all previous interfaces, so I think
we should be fine even if there is a new probe from pcbnew->3d Viewer.
That said, we are about 1 month away from feature freeze, so any
implementation would need to be on that timescale.
Best-
Seth
On Wed, Sep 2, 2020 at 6:25 AM Ian McInerney
wrote:
> The 3d viewer does have access to the kiway, but I really think we need to
> think about how this is done before we just go adding a cross-probing
> interface between pcbnew and the 3d viewer. As our kiway is written
> currently, adding the cross-probing will basically be adding a brand-new
> messaging protocol between those two frames - and I would like for us to
> avoid adding a new cross-probing specification when we already have two in
> existence (the pcbnew <-> eeschema one and eeschema <-> simulator) that
> both are different.
>
> Jon, Seth and I had been discussing the future of the kiway off and on for
> the last few months, and I think we are going to propose upgrading the
> kiway to be a more structured interface (possibly using something like
> JSON-RPC, but that hasn't been spec'd yet and I don't want to start the
> discussion at this moment) with every frame listening on a local port for
> the messages (instead of the current wx-event system relying on passing
> strings/objects in memory) for v7. The thinking is then we define a
> "cross-probe" command in the new RPC system that will be sent over the
> kiway and all frames receive it and act on it if they want (so then you can
> select a module in pcbnew and it will send a single cross-probe request
> that can be ingested by both eeschema and the 3d-viewer instead of having
> to send two different requests in possibly two different formats).
>
> I don't think Seth, Jon or I will have much time in the next month to
> write up a spec on this new interface yet since we all have work to do
> before feature freeze. But I think this can definitely be something we
> ensure is inside the kiway spec so it will be implementable in v7.
>
> The part I have never been sure of is how the actual 3d-viewer parts would
> be implemented, because it is not obvious to me if there is a nice way to
> show the selection in the rendering, or if we can get user-input to select
> models in the 3d viewer and then cross-probe them back to the board in our
> system. This is something that is possible in the OpenCascade viewer system
> though, so we might be able to add similar functionality to ours.
>
> -Ian
>
> On Wed, Sep 2, 2020 at 2:04 PM Wayne Stambaugh
> wrote:
>
>> It's part of the kiway mail messaging system. Take a look at the
>> kiway*.{h/cpp} files. I'm not sure if the 3D viewer is derived from
>> KIWAY_PLAYER. If it is, this should be fairly straight forward assuming
>> you can figure out the component position from the model geometry and
>> translate that back to the board position. If not, you will have a lot
>> more work to do. I do no want to add another messaging protocol to the
>> board editor.
>>
>> On 9/1/20 6:15 PM, Mário Luzeiro wrote:
>> > Hello all,
>> >
>> > I'm evaluating how/ if it will be possible to implement some kind of
>> cross footprint selection between the 3D-Viewer and Pcbnew.
>> > I know that it works with Schematic and Board so I believe there are
>> already some existent mechanisms.. but I don't know what exists in KiCad
>> source-code for that.
>> >
>> > Could someone point me where can I find relevant code that is already
>> used or implemented for this purpose?
>> >
>> > I have the following questions do clarify:
>> > - Can I notify 3D-Viewer to update the render from pcbnew/eeschema?
>> > - How can I flag/or select a footprint and notify pcbnew/eeschema?
>> > - Does a footprint has a flag that says it is selected? or there is
>> some other list of selected footprints?
>> >
>> > Any other concerns or things that I should have a look?
>> >
>> > Regards,
>> > Mario Luzeiro
>> >
>> > ___
>> > Mailing list: https://launchpad.net/~kicad-developers
>> > Post to : kicad-developers@lists.launchpad.net
>> > Unsubscribe : https://launchpad.net/~kicad-developers
>> > More help : https://help.launchpad.net/ListHelp
>> >
>>
>> ___
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to : kicad-developers@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~kicad-dev
Re: [Kicad-developers] request for comment about perhaps clearer strings
On Mon, Aug 31, 2020 at 9:30 AM Marco Ciampa wrote: > On Mon, Aug 31, 2020 at 07:08:51AM -0700, Seth Hillbrand wrote: > > There are a couple reasons not to change the term from "Power" to > "Supply". > > First, we have symbol libraries with the "Power" term. Changing the > > software to "Supply" would need to include changing the library. Second, > > the term "Supply" in electrical engineering is reserved. It refers to a > > direction of current. It is the pair of "Drain". > > clear & right > My apologies. I wrote this before finishing my coffee. The pairs (in english) are "Source" and "Drain" not "Supply" and "Drain". But the first reason is valid. -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] request for comment about perhaps clearer strings
In the code, we have only one location that refers to "Power Pins" (backannotate). And we have two that refer to "Power Ports" (Edit component and Add Power button). We should definitely unify those. There are a couple reasons not to change the term from "Power" to "Supply". First, we have symbol libraries with the "Power" term. Changing the software to "Supply" would need to include changing the library. Second, the term "Supply" in electrical engineering is reserved. It refers to a direction of current. It is the pair of "Drain". Can you say a bit more about the confusion you are trying to solve? Maybe we can address it another way? -Seth On Sun, Aug 30, 2020 at 10:33 PM Marco Ciampa wrote: > Hello devs, > a trivial rfc (I may be wrong of course): > Why not call the "supply" pins "supply pins" and not "power pins"? > I think it could be clearer. > > TIA > > -- > > Saluton, > Marco Ciampa > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 <+12126039372> Davis, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
