Re: [Kicad-developers] Stable release 4.0.7 status.

On 16/08/17 01:35, Wayne Stambaugh wrote: AFAIK we intend to use the 4.0.6 tag for libraries, docs, and i18n. The libraries in particular have changed significantly and I think it's a bad idea to break users schematics on a point release. Does the default setup of kicad use the github plugin

Re: [Kicad-developers] KiCad Libraries (again)

On 19 Sep 2017 2:05 am, "José Ignacio" wrote: Probably, contributors would need to agree to be attributed as a group when the work is embedded in a design (When the library is distributed in whole or part they should get attributed individually as the GPL requires).

Re: [Kicad-developers] KiCad Libraries (again)

On 19/09/17 00:59, José Ignacio wrote: The GPL with font exception is probably the better of the two, as it is the least restrictive one contributors seem to agree on Well we use this already for the 3d model lib. https://github.com/KiCad/kicad-packages3D/wiki/Model-Licencing So it would

Re: [Kicad-developers] GitHub Plugin (my nemesis)

On 02/10/17 11:37, Simon Küppers wrote: I am no expert, but this question is out of the scope of this thread.. For downloading, gut applies compression anyway. I respect the people having slow Internet lines.. However as shown a few posts backwards, the whole footprints and symbol library is

Re: [Kicad-developers] Datasheet confusion

On 12/10/17 15:12, Kristoffer Ödmark wrote: Sorry for double messages but one solution could be to use the Library stored documentation to autofill the FIELD variable IF it is empty. And then base all the functionality on the field variable? I could probably fix this if it seems an okay

Re: [Kicad-developers] GitHub Plugin (my nemesis)

On 23/09/17 20:51, Thomas Kindler wrote: The other suggestions were quite surprising to me -- Github API, downloading individual subdirectories as .zip, abusing subversion (gasp), gitslave (last updated 2012), etc. would be a big hurdle and WTF for new KiCAD users. Sorry for the late response.

Re: [Kicad-developers] Stable release 4.0.7 status.

On 24/08/17 21:03, Nick ^ wrote: I have now added the Librarians team as write for those four repos. Please tag appropiately. I can tag them if HEAD is good enough. Thanks. I pushed the tags. ___ Mailing list:

Re: [Kicad-developers] Stable release 4.0.7 status.

shooting for Friday or Saturday. On 8/17/2017 8:45 AM, Rene Pöschl wrote: On 16/08/17 01:35, Wayne Stambaugh wrote: AFAIK we intend to use the 4.0.6 tag for libraries, docs, and i18n. The libraries in particular have changed significantly and I think it's a bad idea to break users schematics

Re: [Kicad-developers] PCBNew / Footprint editor - "Special strings"

On 18/10/17 12:50, Thomas Langås wrote: On Wed, Oct 18, 2017 at 12:04 PM, Gaurav Juvekar wrote: Summary: - Does KiCad support having an F.Assembly and B.Assembly layer? - Does KiCad support "special strings" like Altium's .Designator ? I think F.Fab and B.Fab is what

Re: [Kicad-developers] Migrating old designs best practice

On 24/11/17 04:47, hauptmech wrote: I can confirm unconnected wires. It may be worth noting that I did not preserve the -cache.lib file when I archived the design. I also had an issue with an old asymmetric diode footprint having its anode and cathode reversed when I used it in a new design. If

Re: [Kicad-developers] Migrating old designs best practice

On 24/11/17 12:38, hauptmech wrote: On 24 Nov 2017 10:52 pm, "Rene Pöschl" <poesc...@gmail.com> wrote: On 24/11/17 04:47, hauptmech wrote: I can confirm unconnected wires. It may be worth noting that I did not preserve the -cache.lib file when I archived the design. I a

[Kicad-developers] Is there a timeframe till the stable release will be announced

We librarians would need to know how long we have until our library reorganization needs to be finished. (The footprint lib reorganization is nearly done. Now we are working on the symbol libs.) ___ Mailing list:

Re: [Kicad-developers] Wording change

I think Greg is referencing this forum conversation: https://forum.kicad.info/t/pcbnew-sketch-mode-what-is-it/8429 There it was reported that the word sketch is used in the display options dialog for pcb_new. On 19/11/17 00:30, Nick Østergaard wrote: Where is the word "Sketch" used now?

Re: [Kicad-developers] [PATCH] LIB_TABLE tweaks

On 16/11/17 17:41, Kevin Cozens wrote: On a side note, you might see a trailing / for the KISYS3DMOD environment variable. That is there by default when you first run KiCad. I would remove that extra character for consistency. So far I have not noticed any negative effects when the path for

[Kicad-developers] What are the smallest values for pad paste and mask clearances? Why can't polygon pads not use negative mask clearance?

We (the librarians) discovered that our workflow (or is it a workaround for missing features) of defining special paste or mask areas does not work as intended. We use paste or mask only pads (no copper, only past or mask selected, no pin number assigned) to specify mask/paste areas if we can

[Kicad-developers] Fwd: Re: What are the smallest values for pad paste and mask clearances? Why can't polygon pads not use negative mask clearance?

t the tolerances are too small for the board manufacturer. The best case scenario is the boards will be rejected by the manufacturer's DRC or in the worst case the boards will not reflect what the user had intended and possibly fail. On 04/27/2018 03:16 PM, Rene Pöschl wrote: We (the librarians

Re: [Kicad-developers] Fwd: Re: What are the smallest values for pad paste and mask clearances? Why can't polygon pads not use negative mask clearance?

Maybe a bit of further clarification will help. We are talking about at least two different things here. First issue is what i guess most of you have in mind. The thing about mask clearance. Here the normal way is of course to enter the restrictions of your board house globally into kicad. But

Re: [Kicad-developers] Fwd: Re: What are the smallest values for pad paste and mask clearances? Why can't polygon pads not use negative mask clearance?

On 28/04/18 14:26, jp charras wrote: you also must set the solder paste ratio clearance clearance to a very small value (for instance 0.1 %) really? so if i set only the solderpaste clearance the global solderpaste ratio still overwrites my settings? That would be really strange

[Kicad-developers] Was there a change in how the footprint name is stored inside the footprint files?

It seems the footprint editor now includes the library name in the footprint name (first line of the footprint file) Has this changed on purpose or is this a bug? ___ Mailing list: https://launchpad.net/~kicad-developers Post to :

Re: [Kicad-developers] 5.0 RC2 / release status

/2018 11:53 AM, Rene Pöschl wrote: On 18/05/18 16:44, Wayne Stambaugh wrote: If any of our doc and library devs are on this mailing list, please forward this information so we aren't making major changes to the docs and libraries at the last minute. We have one important pull request open that i

Re: [Kicad-developers] 5.0 RC2 / release status

On 18/05/18 16:44, Wayne Stambaugh wrote: If any of our doc and library devs are on this mailing list, please forward this information so we aren't making major changes to the docs and libraries at the last minute. We have one important pull request open that i will fix up my self tomorrow

[Kicad-developers] As promised a version 4 backport of the version 5.0.0-rc2 libraries has been created

Hi all, We (the librarians) created a kicad 4.0.x backport of the version 5 libraries. This backport contains a reduced set of footprints that are compatible with kicad 4. We also backported the symbol libs (without loss as the current libs do not use any v5 features) Only limitation

Re: [Kicad-developers] Upgrading from V4 to V5 resources?

Another pitfall seems to be that users do not expect that they need to update their fp-lib-table after installing kicad 5. Either they need to update the fp-lib-table to get the footprint library to the state of v5 or they would need to manually install the version 4 symbol and 3d model libs

Re: [Kicad-developers] rc3

What a coincidence. I will also be out of town for the next one and a half weeks. As i can not guarantee that i will have internet access during this time it might be necessary that somebody else tags the final kicad 5 library release. (I should be back at June the 10th late at night CET.) So

Re: [Kicad-developers] rc3

I just added the rc3 tag to the library. (A bit later than promised. Hope this is still ok.) On 24/06/18 03:12, Rene Pöschl wrote: I can add the rc3 tag to the library repos sometime Sunday afternoon. (central European time) A few minor corrections would still be nice to get into v5 but we do

Re: [Kicad-developers] rc3

I can add the rc3 tag to the library repos sometime Sunday afternoon. (central European time) A few minor corrections would still be nice to get into v5 but we do not have any deal-breaker that would merit postponing v5 from our side. On 23/06/18 17:15, Wayne Stambaugh wrote: Let's try to get

[Kicad-developers] How to help users handle updating from version 4 to version 5 with regards to fp-lib-table handling?

Hello, I know we are in feature freeze. It seems a lot of people struggle with the transition from kicad 4 to kicad 5. One of the things that could help a lot would be some way of forcing a reset of the user config directory contents to the default. (cold also help later on if for some

Re: [Kicad-developers] rc3

earned them! :) Wayne, if you could please announce on the list when you tag rc3, that would be awesome. Thanks! Adam On Fri, Jun 29, 2018 at 7:27 PM Rene Pöschl wrote: What a coincidence. I will also be out of town for the next one and a half weeks. As i can not guarantee that i will have

Re: [Kicad-developers] A reminder on Git commit comments

mple, look at this commit in the kicad-symbols repo: commit 4ada78e26774c841ce8ec33e8b221d04fed1f4c7 Author: Rene Pöschl <r.poes...@student.tugraz.at> Date:   Fri Apr 20 11:14:47 2018 +0200     Remove Connector_Specialized files. Great. I can /see/ that these files are being

Re: [Kicad-developers] A reminder on Git commit comments

; in the KiCad repos. These comments are useless. For an example, look at this commit in the kicad-symbols repo: commit 4ada78e26774c841ce8ec33e8b221d04fed1f4c7 Author: Rene Pöschl <r.poes...@student.tugraz.at> Date: Fri Apr 20 11:14:47 2018 +0200 Remove Connector_Sp

Re: [Kicad-developers] [RFC]: New non copper pad paste and mask clearances behavior

This sounds like a reasonable solution for kicad 5 to me. Thanks for taking care of it. On 02/05/18 14:58, jp charras wrote: Hi All, Dick Hollenbeck ( who wrote a lot of code for Kicad) proposed to use global mask margin values only for pad at least on a copper layer. (I am thinking this is

Re: [Kicad-developers] Fwd: Re: What are the smallest values for pad paste and mask clearances? Why can't polygon pads not use negative mask clearance?

On 28/04/18 09:28, jp charras wrote: For custom shaped pads, building a solder mask shape with a negative margin can create issues (unpredictable shape for non convex polygons). So it is not allowed. One can set a negative margin in the footprint itself. This negative margin is then used

Re: [Kicad-developers] A reminder on Git commit comments

On 03/05/18 08:31, Carsten Schoenert wrote: Hello Rene, Am 02.05.2018 um 14:57 schrieb Rene Pöschl: Most of our contributors have no previous experience with git. So we really can not expect them to understand anything beyond the github workflow. (They are experts in electronics. Not IT) I

Re: [Kicad-developers] Symbol library editor functionality removed

On 01/01/18 00:40, Andy Peters wrote: Apropos of the recent discussion about problems with the ‘/‘ character in symbol names (https://lists.launchpad.net/kicad-developers/msg31705.html), I went to rename three problematic symbols in my library. I’m on the 24 Dec 2017 nightly on macOS. (This

Re: [Kicad-developers] No op-amps in symbol library?

Single op amps differ too much. It is not really possible to create generic symbols for these. See: https://github.com/KiCad/kicad-library/pull/1114 Specialized symbols are in the linear lib. (In the lib for v5 they will eventually be found in Amplifier_Operational. These have not yet been moved

Re: [Kicad-developers] Libedit and Modedit Icons

On 09/01/18 16:50, Wayne Stambaugh wrote: I'm with Jose on the arrows. If we are going to use them, please don't make the all different colors. I don't see how a blue left arrow versus a magenta right arrow conveys any meaning to the user. I like the idea of coloring them differently. For

Re: [Kicad-developers] Some thoughts on symbol remapping

On 10/01/18 11:46, Matthijs Kooijman wrote: A related question: How are the changes in library layout intended to be handled, when combined with the remapping dialog? AFAIU the migration to the new kicad-symbols repository also involves renaming a lot of libraries (e.g. Connectors.lib ->

Re: [Kicad-developers] Some thoughts on symbol remapping

On 10/01/18 19:54, Matthijs Kooijman wrote: Hi Wayne, If the remapping algorithm cannot find the exact library match which is currently being used (and should be in the project library list or the cache) to provide the symbol, then there is no way to determine the correct library and therefore

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 15/01/18 17:53, Carsten Schoenert wrote: Am 15.01.2018 um 12:09 schrieb Rene Pöschl: ... 1. Is there some release time strategy planned? Are there any release dates planned for the newly created repositories and what are the planes for releasing updates of these. The only discussion i know

Re: [Kicad-developers] Future plans on the KiCad library releases?

. I don't think the date idea suggested is going to be reliable. On 1/15/2018 6:09 AM, Rene Pöschl wrote: On 15/01/18 11:16, Carsten Schoenert wrote: Hi, as the packaging for Debian will change as well for the next KiCad release I've some questions pointed to the contributors and admins

Re: [Kicad-developers] What is the difference between library file format version 2.4 and 2.3

as long as you do not use these features. Regards, Orson On 01/18/2018 11:11 PM, Rene Pöschl wrote: ".lib" files created or edited with a recent nightly build set the header information to version 2.4. What is the difference to the lib version used in kicad stable (version 2.3). I ca

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 17/01/18 10:03, Carsten Schoenert wrote: Some more information about the current plans and doings in the library team would be a good thing! And please not only through the KiCad user forum. Please use also the KiCad website and/or the new GitHub site for the libraries you have created. Not

Re: [Kicad-developers] [PATCH] Don't draw invisible pins in component chooser

On 15/01/18 10:00, Maciej Sumiński wrote: Perhaps we should have an ERC rule that warns about invisible pins being connected to a wire, any thoughts? Invisible pins are used for three distinct applications. The first one is to remove clutter by hiding pins that should not be connected. ERC

Re: [Kicad-developers] Future plans on the KiCad library releases?

On 15/01/18 11:16, Carsten Schoenert wrote: Hi, as the packaging for Debian will change as well for the next KiCad release I've some questions pointed to the contributors and admins of the libraries to be able to prepare the needed package transitions as also mentioned by Jean-Samuel. 1. Is

Re: [Kicad-developers] UI changes for 5.0?

On 09/02/18 01:28, Wayne Stambaugh wrote: Assuming this can be completed in a reasonable amount of time and it is consistent then I'm fine with this going into v5. This is just cosmetic and isn't going to break anything. I've got a few more patches to review and some work of my own to finish

Re: [Kicad-developers] [PATCH/RFC] Footprint editor menu bar

On 19/02/18 12:14, Jeff Young wrote: The Open / List All button is much faster on all libraries than it used to be, and it’s a bit of a step-child to Search by Keyword and Select by Browser anyway. So, I’m going to propose that we add a Library selection widget to New Footprint..., Export

Re: [Kicad-developers] [PATCH/RFC] Footprint editor menu bar

On 19/02/18 13:16, Jeff Young wrote: Hi Rene, Comments in-line: On 19 Feb 2018, at 12:07, Rene Pöschl <poesc...@gmail.com> wrote: On 19/02/18 12:14, Jeff Young wrote: The Open / List All button is much faster on all libraries than it used to be, and it’s a bit of a step-child to

Re: [Kicad-developers] Packaging question

On 25/02/18 23:29, Wayne Stambaugh wrote: Stephen, I would say that you should pull from HEAD of each library. This will probably be acceptable up to the stable release. At this point we will have to tag each repo. Are any of our library devs planning on doing any major reorganization of the

Re: [Kicad-developers] [PATCH] RFC: toolbar button support for action plugins

One can however archive a repo. (We did that with all the old library repos.) I am not sure if the automatic synchronization with the lauchpad code would still work for archived repos. On 23/08/18 20:31, José Ignacio wrote: Pull requests cannot be disabled on Github On Thu, Aug 23, 2018 at

Re: [Kicad-developers] 5.0.1 release

Is it planned to include a new version of the libraries as well? Right now we ensure that the library is relatively stable so i think the improvements made since the v5 release can easily be included. (We do not allow major changes that would break backward compatibility. My plan is to use this

Re: [Kicad-developers] 5.0.1 release

er designs to a minimum. Users can always download the latest libraries if they prefer the bleeding edge. On 8/28/2018 12:18 PM, Rene Pöschl wrote: Is it planned to include a new version of the libraries as well? Right now we ensure that the library is relatively stable so i think the improvements made si

Re: [Kicad-developers] 5.0.1 release

wrote: On 8/28/2018 12:48 PM, Rene Pöschl wrote: Right now we have no changes made that would break projects. (That is what i meant with "backwards compatibility" I know it is not quite the right term) Also i thought the cache lib plus rescue dialog should take care of minor changes

Re: [Kicad-developers] Stable 5 release.

The library repos should now all be tagged. (Github had some server problems so it all took quite some time. I hope nothing got damaged because of that.) On 19/07/18 10:49, Nick Østergaard wrote: This sounds good. Thank you. Den tor. 19. jul. 2018 kl. 10.43 skrev Rene Pöschl : On 18/07/18 19

Re: [Kicad-developers] Stable 5 release.

On 18/07/18 18:09, Carsten Schoenert wrote: Hi, Am 18.07.18 um 16:23 schrieb Nick Østergaard: I probably didn't mention this clearly. It is also good for me if everything is tagged on friday, I guess that is mostly about the libs, as I will probably tag i18n and doc myself. I'd like to see at

Re: [Kicad-developers] KiCad 5 release announcement update

I just noticed you sometimes use opengl/cairo and sometimes modern to reference the "modern toolset". On 22/07/18 18:44, Wayne Stambaugh wrote: I just pushed the updated version of the v5 release announcement[1]. Please let me know if you find any missing features. Cheers, Wayne [1]:

Re: [Kicad-developers] Windows Builds

On 23/07/18 05:27, Mark Roszko wrote: Is it because the installer exe is huge? That's because the footprint libraries are now part of the installers and they are absolutely massive. (4GB uncompressed) The whole repo (including git history) only has ~90MB If any libs are to blame then it will

Re: [Kicad-developers] Stable 5 release.

On 18/07/18 19:59, Carsten Schoenert wrote: Am 18.07.18 um 19:55 schrieb Rene Pöschl: I'm traveling the whole Saturday and Sunday to Debian DebCamp and DebConf in Taiwan and working on packaging kicad-packages3d on a laptop is PITA. So I'd like to this at home on a more powerful machine at home

Re: [Kicad-developers] kicad version and install location

I get the feeling there is a bit more panic than need be. One of the reasons is that the v4 installer on windows did set operating system variables (environment variables) which can create problems when updating. So it might be a good idea for the v5 installer to clean up this mess. (or at

Re: [Kicad-developers] kicad version and install location

Another idea would be to provide a package with version 4 libs. That way users can work with the new v5 features but do not need to worry about updating libraries. On 14/07/18 09:29, Rene Pöschl wrote: I get the feeling there is a bit more panic than need be. One of the reasons

Re: [Kicad-developers] kicad version and install location

This only helps users who never had system environment variables set. They overwrite the settings coming from the config folders. (So all default windows installation are not helped with this.) On 16/07/18 16:16, Nick Østergaard wrote: Why does this need to be so complicated? I think we

Re: [Kicad-developers] Questions on 6.0 eeschema file format

My guess would be maintainability. Having some way of sharing parts of different symbols with each other makes it way easier to manage large libs. (Nobody would be forced to use these features but they can make live easier for library maintainers. We could then for example provide a single

Re: [Kicad-developers] The version string in the master branch

Why not just use the date at which the nightly was compiled? So something like dev-snapshot--mm-dd_g23849572 This is sortable and it should confuse nobody. On 24/07/18 23:58, Eeli Kaikkonen wrote: ti 24. heinäk. 2018 klo 22.59 Wayne Stambaugh (stambau...@gmail.com

Re: [Kicad-developers] 5.0.1 release

this happens with enough frequency then the sum of all changes could be too much.) On 28/08/18 19:16, Wayne Stambaugh wrote: > On 8/28/2018 12:48 PM, Rene Pöschl wrote: >> Right now we have no changes made that would break projects. (That is >&

Re: [Kicad-developers] Round trace bends

Hi, right now there is a discussion ongoing on the forum about that. Might have some useful information for you in there: https://forum.kicad.info/t/status-on-curved-smooth-corners-in-traces/12287 On 31/08/18 09:14, Martin Laabs wrote: Hi, is there is any development for chamfer trace edges

Re: [Kicad-developers] [RFC] New pad primitive shape: Chamfered roundrectangle

Hi, From reading the patch it seems this is for cases where you have exactly one corner to chamfer. Which is a nice addition for qfn footprints. It would however be a bit more flexible if every corner is toggleable independently (so one could make pads with 1,2,3 or even 4 corners

Re: [Kicad-developers] rc3

Strange i made the tag via the github web interface. 2018-07-04 17:45 GMT+01:00 Nick Østergaard : > Hello Rene > > It looks like you didn't push the tag on templates, but I will just tag it > then. > > Nick > > Den søn. 1. jul. 2018 kl. 00.34 skrev Rene Pöschl : > >

Re: [Kicad-developers] Stable 5 release.

for anyone trying to create simulations. I preferred the old symbols but it's not something I feel strongly about but given that these changes caused this issue we may need to rethink this decision or provide alternative symbols for spice simulation. Cheers, Wayne On 7/12/2018 5:36 AM, Rene Pöschl

Re: [Kicad-developers] Stable 5 release.

The libs should be ready to go. We might still fix some minor things till the release but we do not have any showstopper topics open. On 11/07/18 20:49, Wayne Stambaugh wrote: Are there any critical bugs remaining to be fixed for the stable 5 release? I didn't see any thing outstanding but I

Re: [Kicad-developers] Stable 5 release.

On 12/07/18 16:20, jp charras wrote: Le 12/07/2018 à 16:04, Rene Pöschl a écrit : Sadly the old symbols are completely unusable in many modern circuits which use more then one power supply for different parts of the circuit. Hidden power pins are not the way to go! The fix for this bug must

Re: [Kicad-developers] Stable version 5 tagged.

Now i am confused. Yesterday (or a bit before) you wrote something about the 20th of july. I will look into tagging the library sometime tomorrow CET. (Too tired right now to check if everything is ok.) On 13/07/18 16:15, Wayne Stambaugh wrote: Queue up the Handel's "Hallelujah Chorus", the

Re: [Kicad-developers] KiCad 5 and the Github footprint wizard?

On 07/03/18 17:09, Thomas Pointhuber wrote: Hi, at least in the nightly it is still possible to add GitHub libraries using "Append with Wizard". Will this change? Because when someone uses this feature, it only references to the old legacy repositories, without a clue about that. Regards,

[Kicad-developers] Why do current nightlies report that they are kicad 5.0.0-rc2?

Hello It seems at least some packages of current nightlies report themselves as version 5.0.0-rc2. (The arch package seems to be one of them.) Is it on purpose that every nightly between tagging rc1 and tagging rc2 is reported as rc2? (I assumed only the one commit tagged would be called

Re: [Kicad-developers] Resistor 2512 footprint [Kicad 4.07]

There are completely new footprints for such devices. (In the v5 lib) I think the resistor lib should even be compatible with kicad 4 (it has no part with complex pads in it). At least the footprint in question is compatible. They are now script generated [1]. The dimensions for the pads are

Re: [Kicad-developers] rc2

On 03/04/18 19:59, Kevin Cozens wrote: I am seeing a problem with CvPcb where it fails to show me any DIP package options when I select a 7400 IC on a board. I need to file a report about the problem. What version of the lib have you installed? Are the footprint and symbol libs from the same

Re: [Kicad-developers] What are the requirements for the courtyard layer polygon?

On 17/04/18 13:28, jp charras wrote: Le 17/04/2018 à 13:15, Rene Pöschl a écrit : If i understand it correctly, kicad 5 will offer a check for courtyard violations. Does this check come with requirements with regards to the courtyard layer? In particular: Does the polygon that describes

[Kicad-developers] What are the requirements for the courtyard layer polygon?

If i understand it correctly, kicad 5 will offer a check for courtyard violations. Does this check come with requirements with regards to the courtyard layer? In particular: Does the polygon that describes the courtyard need to be closed? If not how much tolerance is allowed? Are arcs and

Re: [Kicad-developers] What are the requirements for the courtyard layer polygon?

On 18/04/18 12:59, jp charras wrote: Le 17/04/2018 à 13:54, Rene Pöschl a écrit : On 17/04/18 13:28, jp charras wrote: Le 17/04/2018 à 13:15, Rene Pöschl a écrit : If i understand it correctly, kicad 5 will offer a check for courtyard violations. Does this check come with requirements

[Kicad-developers] Lib maintainers request help for reviewing installation script changes

Dear developers, we lib maintainers might be good at checking symbols and footprints against datasheets, the KLC and industry standards but we are a bit lost with the requirements of installation scripts. Could one of you take a look at the changes in the following pull requests? -

Re: [Kicad-developers] Zone keepouts within modules

On 19/03/18 13:02, Simon Santesteban wrote: Hi everyone, I am a new developer in kicad community. I have been working on adding zones to modules, so I would like to share this work. Find attached a patch to have this functionality. Regards, Simon

Re: [Kicad-developers] MacOS Packaging Question

On 03/03/18 23:32, Seth Hillbrand wrote: ​In the current nightly MacOS builds, we package the applications, symbols and 3d models but no footprints. Is this an oversight? -S​ This might be because in kicad 4 the footprints where downloaded on demand via the github plugin. With the new

Re: [Kicad-developers] PPA: KiCad 5.0

On 26/02/18 10:53, Jean-Samuel Reynaud wrote: Dear All, Following KiCad 5.0 tagging, I had create a dedicated PPA for next release (5.0). For the moment, only RC1 of kicad is built. When other repositories will be tagger (i18n, docs and all libs), I will also provide them on this PPA. It's

Re: [Kicad-developers] 5.0.1 status

Regarding libs. I would need to run the script testing for incompatible changes with the current master. (I can do this as soon as i am home today. So in a few hours.) I already ran it at the end of August the changes that occurred until then are documented in [1] As soon as i update that

Re: [Kicad-developers] Some of our symbols currently still have invisible power pins. We want to fix this but want to give you guys a chance for input first.

to get rid of the old ones anyway not to carry them forever, won't we? I'm wondering whether we can for option 1 if we evaluate what the behaviour would be regarding ERC, symbol rescue, etc. Thanks, Diego On Tue, Nov 6, 2018 at 9:42 PM Rene Pöschl <mailto:poesc...@gmail.com>>

[Kicad-developers] Some of our symbols currently still have invisible power pins. We want to fix this but want to give you guys a chance for input first.

Hi all, Sadly we did not come around to fix all symbols before the v5 release. We now seem to have a volunteer who would be prepared to fix these symbols. There is a catch though. Whatever we do to fix this it will break designs that use the old symbols right now. So we have a few

Re: [Kicad-developers] Some of our symbols currently still have invisible power pins. We want to fix this but want to give you guys a chance for input first.

On 07/11/18 17:39, Kevin Cozens wrote:ons I was thinking that option 3 might be the best How will not hiding pins affect IC's with multiple parts (e.g. a 7400)? Will each part have the power and ground pins? Like we did with the 4xxx series parts. There will be a further unit added that only

Re: [Kicad-developers] 5.0.1 status

Libraries are tagged. On 09/10/18 00:24, Wayne Stambaugh wrote: Rene, Looks good to me. Tag it as soon as you are ready. Thanks, Wayne On 10/08/2018 04:45 PM, Rene Pöschl wrote: Hi all, Updated list can now be found in comment https://github.com/KiCad/kicad-symbols/issues/856

Re: [Kicad-developers] 5.0.1 status

.) On 08/10/18 20:52, Wayne Stambaugh wrote: Hi Rene, I didn't see anything the the list you linked that I would consider a show stopper. I wait until you post the results of you test script against the latest changes. Thanks, Wayne On 10/8/2018 11:35 AM, Rene Pöschl wrote: Regarding libs

Re: [Kicad-developers] Remind me why we have both filled polygons and non-copper zones

Zones and polygons behave a bit differently when it comes to rounded corners. For zones the minwidth setting controls the round radius, for polygons it is the line width. This means polygons with rounded corners are always larger than drawn by the radius size (half line width). But zones are

Re: [Kicad-developers] Cost of different courtyard elements for the closed outline and DRC algorithms

On 01/01/19 23:53, John Beard wrote: @Rene: can you give some examples of "extensive" arc use on the courtyard layers that you are thinking of? Cheers, John The two pull requests i linked should give you an idea of what i right now consider as most extensive use. Maybe also some battery

[Kicad-developers] Cost of different courtyard elements for the closed outline and DRC algorithms

Hi, Right now we have a few contributions for the library that use arcs quite extensively on the courtyard layer. I would therefore like a bit of input. Are arc generally more expensive than lines? Is there a difference if the arc is a multiple of 90 degree compared to any other angle.

Re: [Kicad-developers] [RFC] Symbol library file format

Something else that i remembered now. Would it be a good idea to prepare for alternative function handling for pins? Meaning an alternative pin name connected to an alternative type (or a number of these) That would allow better symbols for micro controllers. I do not expect this to be

Re: [Kicad-developers] [RFC] Symbol library file format

On 04/01/19 15:10, Wayne Stambaugh wrote: Is there a way to mark a unit as "power unit" (I think you mentioned sometime back that this might be required to properly make simulation for multi unit symbols possible while still allowing the power unit to be separate. A power unit would also be a

Re: [Kicad-developers] [RFC] Symbol library file format

I have a few questions regarding multi part (or multi unit) symbols. (I do not really see a clear indication for these features in your document.) Is there a definition for having only some units exchangeable? Is there a way to define a unit as "must be placed" or "optional"? Is there a way to

Re: [Kicad-developers] What is the difference between the use of 3d model search path entries and normal path variables (environment variables)?

on behalf of Rene Pöschl Sent: 11 January 2019 17:25 To: KiCad Developers Subject: [Kicad-developers] What is the difference between the use of 3d model search path entries and normal path variables (environment variables)? Hi, I noticed that the configure path tool in the footprint editor

Re: [Kicad-developers] 5.0.2 stable release.

How does a package get karma? Can the community perhaps help out in some way? On 04/12/18 19:57, Steven A. Falco wrote: My build of kicad-5.0.2-1.fc29 has completed in the Fedora buildsystem, and I've submitted it for testing. Thus, the build should show up in the updates-testing repo as

Re: [Kicad-developers] 5.0.2 stable release.

The libs are now tagged. On 03/12/18 13:49, Wayne Stambaugh wrote: I saw that the translation and doc repos were tagged for 5.0.2. Where do we stand on the library repos? On 11/26/2018 6:49 PM, Evan Shultz wrote: I should have also mentioned that the outstanding items milestoned for 5.0.2

Re: [Kicad-developers] 5.0.2 stable release.

I am a bit out of the loop sadly as i had quite a busy month behind me (new job plus some old responsibilities) I created an issue over at the symbol repo. [1] Both to ask the other librarians and for a place to report design breaking changes. (A few symbols have been changed since 5.0.1 it

[Kicad-developers] Has the handling of the datasheet field changed again?

Is it possible that the datasheet field has been moved to the lib file in the current nightly builds? That would break our testscripts and create unnecessary noise on github. I thought the solution (for v5) has been that the field of the lib file is filled with the one from the dcm file if it

Re: [Kicad-developers] Has the handling of the datasheet field changed again?

On 21/11/2018 18:38, Jeff Young wrote: Version 5.0.x (and version 4.0.x) gave us the option to store the datasheets for both aliases and main symbols in the dcm file. Right; that hasn’t changed. What’s changed (or should have changed) is that the above is the *only* option. So is it not OK

Re: [Kicad-developers] Has the handling of the datasheet field changed again?

On 21/11/2018 17:41, Jeff Young wrote: @Wayne, This is a limitation of the current symbol file format but the root datasheet field should be empty and the datasheet url should be stored in the document file along with the description and keywords. This way it's consistent with all of the

  1   2   >