Re: [Kicad-developers] [RFC] Remove bus joining behavior from KiCad after 5.0 release

I have confirmed that there are no technical challenges with the migration plan proposed by Orson. I made some quick test code that automatically performs the migration silently (i.e. by choosing a label randomly from the available ones to keep) Before I go too far down this path (i.e. making a nic

Re: [Kicad-developers] Odd board

The hole is displayed and I can select/move it. On Mon, Apr 16, 2018 at 9:39 PM, Michael McCormack wrote: > Which version of not seeing the problem - > >1. The hole is displayed >2. The hole gets dropped for the PCB file > > just curious > > Mike > > On Mon, Apr 16, 2018 at 9:30 PM, Jon

Re: [Kicad-developers] Odd board

Which version of not seeing the problem - 1. The hole is displayed 2. The hole gets dropped for the PCB file just curious Mike On Mon, Apr 16, 2018 at 9:30 PM, Jon Evans wrote: > I tested on Ubuntu and Windows 10 using 5.0rc2 and don't see the problem, > so I guess it has been fixed som

Re: [Kicad-developers] Odd board

I tested on Ubuntu and Windows 10 using 5.0rc2 and don't see the problem, so I guess it has been fixed somewhere along the way. On Mon, Apr 16, 2018 at 8:12 PM, Michael McCormack wrote: > OK, here is the boar file, if you need anything else, please let me know. > > On Mon, Apr 16, 2018 at 6:09 P

[Kicad-developers] DISTCC/CCACHE

For those of you who use these tools, I've added a couple of optional cmake flags to integrate them more easily. -DUSE_DISTCC=ON/OFF -DUSE_CCACHE=ON/OFF You can use either or both or neither flags. These default to off, so this should not affect you unless you use these tools. If you do use the

[Kicad-developers] "3D viewer: fixes about hotkeys and menubar."

Hi JP, since your last commit: https://github.com/KiCad/kicad-source-mirror/commit/8fcdc4f6c3fb7c10b4088de11d15d95c4345f9d3 this file also needs to be fixed by adding the GR_KB_SHIFT + https://github.com/KiCad/kicad-source-mirror/blob/9932ff32ae9b2d01a2a7d3ca4db0a6b971e5a0e6/3d-viewer/3d_cache/di

Re: [Kicad-developers] Odd board

Looks like a different bug (2.9mm drill is smaller than 3.2mm pad). I can’t reproduce it on 5.0rc2 Mac. Not sure if that’s because it’s fixed in 5.0, or it only shows up on Windows, or it’s something specific to Michael’s setup. > On 16 Apr 2018, at 22:44, Michael McCormack wrote: > > This i

Re: [Kicad-developers] Odd board

This is the module snipped from the board file: (module Ori:MountingHole_3.2mm_M3_ISO14580 (layer F.Cu) (tedit 59C8FBCE) (tstamp 5AC4E91C) (at 138.25 141.050001) (descr "Mounting Hole 3.2mm, no annular, M3, ISO14580") (tags "mounting hole 3.2mm no annular m3 iso14580") (path /583

Re: [Kicad-developers] Odd board

That sounds like a bug (if there is invalid data like that, we should deal with it in a better way) It sounds like it might be easy to make a trivial test case to attach to a bug report without using your employer's board as-is (maybe by removing everything manually from the kicad_pcb file except f

Re: [Kicad-developers] Odd board

Hi Michael, Is this in 4.0.*? Is the hole the same size as the pad? If so it’s a known bug that is fixed in 5.0. If not then we’d love to get a cut-down version of the board. Cheers, Jeff. > On 16 Apr 2018, at 22:08, Nick Østergaard wrote: > > Is it not possible for you to obfuscate the b

Re: [Kicad-developers] Odd board

Is it not possible for you to obfuscate the board to illustrate the problem? Just delete 99% of the stuff on it to just show a board edge and the hole? 2018-04-16 22:35 GMT+02:00 Michael McCormack : > This might not be quite the right place to post this, but, I've found > something that is a slig

[Kicad-developers] Odd board

This might not be quite the right place to post this, but, I've found something that is a slightly problematic with Kicad and board file. I have a PCB that has a NPH hole located off the board, I can't see it or select it inside PCBNew, however, it gets a hole in the gerbers and I can find it in t

Re: [Kicad-developers] Support for inner layer pads in modules

Hi Darrell- Please see https://bugs.launchpad.net/kicad/+bug/1466962 Pads on inner layers is a good idea but it needs a full implementation. This would include (at a minimum) adding the pads to arbitrary layers (not just In2_Cu), new netnames layers, GAL layers and zone filling connection/keepout

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Please let me know how much effort is involved on your part and we can make a decision from there. Thanks, Wayne On 4/16/2018 1:18 PM, Jeff Young wrote: > Can I? Certainly. > > Without tearing my hair out? Much more questionable. ;) > > I’ll look into it…. > >> On 16 Apr 2018, at 18:10, Way

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Can I? Certainly. Without tearing my hair out? Much more questionable. ;) I’ll look into it…. > On 16 Apr 2018, at 18:10, Wayne Stambaugh wrote: > > Is there any way you could do this without dragging in all of the other > changes? If we cannot fix the current table editor, I'm OK with > up

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Is there any way you could do this without dragging in all of the other changes? If we cannot fix the current table editor, I'm OK with updating to the wxGrid based design but I would prefer to keep the changes to just the table editor. On 4/16/2018 6:02 AM, Jeff Young wrote: > Given the spate of

[Kicad-developers] Support for inner layer pads in modules

Inner layer pads are useful for microwave filters implemented as Kicad modules, allowing tracks to connect to them. I've made a quick and dirty change to support the board I'm currently designing: --- a/pcbnew/class_pad.cpp +++ b/pcbnew/class_pad.cpp @@ -1248,6 +1248,11 @@ void D_PAD::ViewGetLaye

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Hi Martin, We’re currently talking about the “BOM editor” rather than the “Fields editor”. (Click the spreadsheet icon in the eeschema’s top toolbar to get the “BOM editor”. That being said, I have also wxGrid-ized the Fields editor, which can be seen here: https://git.launchpad.net/~jeyjey/

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

There is also: https://bugs.launchpad.net/kicad/+bug/1729373 and some of these also apply to the global fields editor: https://bugs.launchpad.net/kicad/+bug/1764053 My 6.0 commit can be found here:

Re: [Kicad-developers] Fwd: Right to use KiCad name / logo

On 4/16/2018 9:35 AM, Gustavo Bruno wrote: > 2018-04-11 10:46 GMT-03:00 Wayne Stambaugh : >> On 4/11/2018 9:23 AM, Strontium wrote: >>> Who pays for that, and who holds it is another question. But if it >>> happens, we should clearly define what's allowed and what's not. For >>> example, if you

Re: [Kicad-developers] [RFC] Remove bus joining behavior from KiCad after 5.0 release

I think the logic you describe wouldn't be too bad to implement. I already have logic that collects all of the labels attached to a bus subgraph (an set of visually-connected bus wires) I could just split the bus name from the vector numbers, figure out what the size of the output vector should be,

Re: [Kicad-developers] Serious Lib cache issue, and fix in commit 2974a2c10

On 4/16/2018 9:25 AM, Maciej Sumiński wrote: > Hi Wayne, > > I see, but I wonder if there is any benefit in making the colon > exception just for rescue/cache libraries? I suppose it makes them > special in the sense they cannot be used as regular libraries due to > illegal character in symbol nam

Re: [Kicad-developers] [RFC] Remove bus joining behavior from KiCad after 5.0 release

On 4/16/2018 9:39 AM, Maciej Sumiński wrote: > I agree this a slightly confusing feature, which requires reading the > user manual to discover. I vote for removal, but we need a clever > migration plan to do so. I'm OK with removing this as well but we definitely need a migration plan. Users netl

Re: [Kicad-developers] [RFC] Remove bus joining behavior from KiCad after 5.0 release

I agree this a slightly confusing feature, which requires reading the user manual to discover. I vote for removal, but we need a clever migration plan to do so. I am not sure how easy would it be to implement it, but how about the following automatic fix: - determine the superset of connected buse

Re: [Kicad-developers] Serious Lib cache issue, and fix in commit 2974a2c10

Hi Wayne, I see, but I wonder if there is any benefit in making the colon exception just for rescue/cache libraries? I suppose it makes them special in the sense they cannot be used as regular libraries due to illegal character in symbol names. As I said, I am not familiar with caching/rescue cod

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Hi Jeff, Are you referring to lp:#1761378 [1] and lp:#1763223 [2] or there are more bugs? If you have the commits already published somewhere, would you give links to them? It is easier to evaluate an approach while looking at related code. Cheers, Orson 1. https://bugs.launchpad.net/kicad/+bug/

Re: [Kicad-developers] Serious Lib cache issue, and fix in commit 2974a2c10

Hey Orson, The colons are required to prevent symbol name clashes in the cache library. I had to prefix the library nickname to the symbol name to prevent symbols from being overwritten when they exist in more than on library. In other words, cache library symbol names look just like LIB_IDs usi

Re: [Kicad-developers] Serious Lib cache issue, and fix in commit 2974a2c10

Hi Jean-Pierre, I understand the patch and thank you for the fix, but apparently I do not have enough knowledge about caching in eeschema to comment on the approach. Frankly, I was a bit surprised to find out that colons are permitted in symbol names stored in a cache library. Regards, Orson On

[Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Given the spate of bug reports recently on the global fields editor (the spreadsheet icon in eeschema), I’m thinking perhaps I should back-port my 6.0 rewrite which moves it to wxGrid. The implementation itself seems pretty sound, but does drag one other change list along with it (for dialog co

[Kicad-developers] Serious Lib cache issue, and fix in commit 2974a2c10

Hi Wayne and Orson, Could you have a look into the fix I committed in rev 2974a2c10. Before this fix, the library cache was broken (all symbol names incorrectly saved). This is specific to the cache, but really annoying... Please, see comments in commit 2974a2c10. But I am not sure this is the

Re: [Kicad-developers] Fwd: Right to use KiCad name / logo

On 2018-04-16 07:33, Mark Roszko wrote: >> "No national law applies" could be either difficult or beneficial for KiCad >> in the case of an infringement. > > That doesn't prevent CERN's right as an entity to assert trademark claims in > any country where they registered as an entity and claimed