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

On 06/07/2019 21:10, Ian McInerney wrote: > Tom, > > Not to pile on the questions, but does the linux stack trace support > exist in the entire 3.0.x line, or how far back does it go? Currently, > the minimum version searched by cmake is 3.0.0, and some major linux > distros only have 3.0.2 (Debia

Re: [Kicad-developers] Strange program version numbering in KiCad

On 7/8/19 10:36 PM, Kevin Cozens wrote: On 2019-07-08 5:10 p.m., Dino Ghilardi wrote: think about the linux kernel versioning number scheme: even subversion number means stable release. Odd subversion number means experimental/development branch. The kernel used to follow the odd/even numberin

Re: [Kicad-developers] Strange program version numbering in KiCad

On 2019-07-08 5:10 p.m., Dino Ghilardi wrote: think about the linux kernel versioning number scheme: even subversion number means stable release. Odd subversion number means experimental/development branch. The kernel used to follow the odd/even numbering scheme but they stopped doing that dur

Re: [Kicad-developers] Strange program version numbering in KiCad

On 2019-07-08 4:47 p.m., Nick ??stergaard wrote: How is a number like 99 being any better than the latest release tag? The release tag doesn't appear in the title bar of the running program. -- Cheers! Kevin. http://www.ve3syb.ca/ | "Nerds make the shiny things that https://www

Re: [Kicad-developers] Strange program version numbering in KiCad

ti 9. heinäk. 2019 klo 0.10 Dino Ghilardi (dino.ghila...@ieee.org) kirjoitti: > As an alternative to the .99 numbering (that should work well until 5.98 > stable version is reached (! :-) ) ) > It was already decided that there won't be even 5.2, let alone 5.98. Whatever the next stable will incl

Re: [Kicad-developers] Strange program version numbering in KiCad

ma 8. heinäk. 2019 klo 23.47 Nick Østergaard (oe.n...@gmail.com) kirjoitti: > How is a number like 99 being any better than the latest release tag? > > Did you read the original post, about the current problem? What is the "latest release tag"? 5.1.0 or 5.1.2? Number like 5.99 is unambiguous (and

Re: [Kicad-developers] Strange program version numbering in KiCad

As an alternative to the .99 numbering (that should work well until 5.98 stable version is reached (! :-) ) ) also think about the linux kernel versioning number scheme: even subversion number means stable release. Odd subversion number means experimental/development branch. At every release of th

Re: [Kicad-developers] Strange program version numbering in KiCad

My brain can visually parse 5.99. I have to actually read the current tags and think about them before I can figure out what they represent. > On 8 Jul 2019, at 21:47, Nick Østergaard wrote: > > How is a number like 99 being any better than the latest release tag? > > On Mon, 8 Jul 2019 at 22

Re: [Kicad-developers] Strange program version numbering in KiCad

How is a number like 99 being any better than the latest release tag? On Mon, 8 Jul 2019 at 22:43, Eeli Kaikkonen wrote: > > > > ma 8. heinäk. 2019 klo 21.23 Wayne Stambaugh (stambau...@gmail.com) kirjoitti: >> >> Honestly, I don't have a strong preference >> one way or another. If someone can c

Re: [Kicad-developers] Strange program version numbering in KiCad

ma 8. heinäk. 2019 klo 21.23 Wayne Stambaugh (stambau...@gmail.com) kirjoitti: > Honestly, I don't have a strong preference > one way or another. If someone can come up with a system that's > workable for everyone, that's fine by me. I don't have an issue with > using something like 5.99.0. > I

Re: [Kicad-developers] Thermal spoke count

Maybe there could be "slow" and "fast" mode for spoke (or in general zone) calculation. Fast for routing, slow for last pass. On Mon, Jul 8, 2019 at 10:58 AM Jeff Young wrote: > Keep in mind that the total width of all the spokes (assuming they’re all > the same length) doesn’t control the curre

Re: [Kicad-developers] Zone min-width isn't

This makes a lot more sense. I agree that the spoke width should be allowed to be the same as the minimum copper width. It just cannot be less. On 7/8/19 3:30 PM, Jeff Young wrote: > Ahh, now I understand where I wasn’t clear. Yes, Seth is correct: I’m trying > to allow them to have the same v

Re: [Kicad-developers] Strange program version numbering in KiCad

I find the current scheme confusing. I like the 5.99 idea…. Cheers, Jeff. > On 8 Jul 2019, at 20:03, Wayne Stambaugh wrote: > > On 7/8/19 2:58 PM, Kevin Cozens wrote: >> On 2019-07-08 2:38 p.m., Nick ??stergaard wrote: >>> @Kevin, And the version is not just the tag and number of commits, but

Re: [Kicad-developers] Zone min-width isn't

Ahh, now I understand where I wasn’t clear. Yes, Seth is correct: I’m trying to allow them to have the same value, not to be the same property. > On 8 Jul 2019, at 20:04, Seth Hillbrand wrote: > > Hi Wayne- > > I don't think Jeff is suggesting that the parameters be combined, just that > we

Re: [Kicad-developers] Zone min-width isn't

Hi Wayne- I don't think Jeff is suggesting that the parameters be combined, just that we should allow the spokes to be the same width as the minimum width. Jeff, is that correct? -Seth On 2019-07-08 09:40, Jeff Young wrote: We enforce minimum width by deflating the zone by 1/2-min-width, s

Re: [Kicad-developers] Strange program version numbering in KiCad

On 7/8/19 2:58 PM, Kevin Cozens wrote: > On 2019-07-08 2:38 p.m., Nick ??stergaard wrote: >> @Kevin, And the version is not just the tag and number of commits, but >> also the sha1. > > That is true when reporting bugs. I don't care about the sha1 when I > want to make sure I am running the right

Re: [Kicad-developers] Strange program version numbering in KiCad

On 2019-07-08 2:38 p.m., Nick ??stergaard wrote: @Kevin, And the version is not just the tag and number of commits, but also the sha1. That is true when reporting bugs. I don't care about the sha1 when I want to make sure I am running the right version of KiCad. That is particularly important

Re: [Kicad-developers] Strange program version numbering in KiCad

@Wayne I think the current one is fine. @Kevin, And the version is not just the tag and number of commits, but also the sha1. On Mon, 8 Jul 2019 at 20:23, Wayne Stambaugh wrote: > > It used to be 6.0.0-dev but apparently this caused package version > issues so it was dropped in favor of the curr

Re: [Kicad-developers] Strange program version numbering in KiCad

It used to be 6.0.0-dev but apparently this caused package version issues so it was dropped in favor of the current version tagging scheme. There has already been at least one confused bug reporter about the current versioning scheme. Honestly, I don't have a strong preference one way or another.

[Kicad-developers] Strange program version numbering in KiCad

Greetings, all. I just ran across something odd with the version number shown by the KiCad program(s). I compiled and installed git master. When I ran it the version number reported is 5.1.0.1195. As I also compile and run the 5.1 version I thought I had a mix up when I did the compile. When

Re: [Kicad-developers] Thermal spoke count

Keep in mind that the total width of all the spokes (assuming they’re all the same length) doesn’t control the current they’ll carry, only how hot they will get for a given current. Most boards are designed with a huge margin of error here. It’s correct that would could do all the calculations

Re: [Kicad-developers] How often do we want to auto-fill zones?

When I’m focusing on one thing it’s distracting when the screen is updating elsewhere. > On 8 Jul 2019, at 14:01, Eeli Kaikkonen wrote: > > > > la 6. heinäk. 2019 klo 15.17 Jeff Young (j...@rokeby.ie > ) kirjoitti: > Refilling on each move (even when fills are fast) i

[Kicad-developers] 5.1.3 string freeze

The last critical bug has been fixed so we are now officially in string freeze for 5.1.3. Please do not push any string changes until 5.1.3 is tagged. Hopefully it wont take too long to update the translations (if they are not updated already). Once the translations are up to date, please let me

Re: [Kicad-developers] Thermal spoke count

ma 8. heinäk. 2019 klo 19.04 Evan Shultz (evan.shu...@gmail.com) kirjoitti: > Because of varying pad shapes, sometimes "+" spokes are best and other > times "x" may be preferred. So having a choice of those options, even > though both have the same number of thermal spokes, may be desirable. I > b

Re: [Kicad-developers] Thermal spoke count

Hi Evan, > On 8 Jul 2019, at 17:04, Evan Shultz wrote: > > Apologies in advance for what will probably be a long message... > > Would 8-way spokes be possible to implement "quickly" (in the algorithmic > sense, not the time to implement sense)? (I don't know if the shortcut you've > (Jeff) de

Re: [Kicad-developers] Thermal spoke count

Apologies in advance for what will probably be a long message... Would 8-way spokes be possible to implement "quickly" (in the algorithmic sense, not the time to implement sense)? (I don't know if the shortcut you've (Jeff) devised works for a paired set of 4 thermal spokes.) 8-way thermals can be

Re: [Kicad-developers] Zone min-width isn't

We enforce minimum width by deflating the zone by 1/2-min-width, simplifying the polygons, and then re-inflating by the same amount. If the spokes are the same width as the minimum, they will disappear. > On 8 Jul 2019, at 13:57, Wayne Stambaugh wrote: > > Isn't the thermal spoke width a diff

Re: [Kicad-developers] How often do we want to auto-fill zones?

la 6. heinäk. 2019 klo 15.17 Jeff Young (j...@rokeby.ie) kirjoitti: > Refilling on each move (even when fills are fast) is pretty noisy. > What do you mean by "noisy"? Eeli Kaikkonen ___ Mailing list: https://launchpad.net/~kicad-developers Post to

Re: [Kicad-developers] Thermal spoke count

On 2019-07-08 08:15, Jeff Young wrote: To support it we’d need to add count (and probably initial angle) to the zone properties dialog, the footprint’s local clearance and spacing seciton and the pad’s local clearance and spacing section. So it would complicate the GUI (although the second and t

Re: [Kicad-developers] Zone min-width isn't

Isn't the thermal spoke width a different setting than the minimum width? I'm under the impression that these two zone properties control completely different aspects of the zone fill and have no impact on the other. On 7/7/2019 5:01 PM, Seth Hillbrand wrote: > We've done this a few times already

[Kicad-developers] Thermal spoke count

The new zone filling algorithm can support additional spoke counts, though they’ll be much slower than 4 (as we can’t cheat some of the math by relying on cartesian coordinates). To support it we’d need to add count (and probably initial angle) to the zone properties dialog, the footprint’s loc

Re: [Kicad-developers] Last commit not compiling.

Please see https://bugs.launchpad.net/kicad/+bug/1835408/comments/3 I think this is the same issue. Do a clean build. On Mon, 8 Jul 2019 at 14:01, Dino Ghilardi wrote: > > commit 4852c91b423abf1e3e745f9d17ad56c92d5445b8 > > does not compile for me on Linux, even re-generating config files with >

[Kicad-developers] Last commit not compiling.

commit 4852c91b423abf1e3e745f9d17ad56c92d5445b8 does not compile for me on Linux, even re-generating config files with cmake. Does anybody else have the same issue? The missing definitions seems to be in pcb_lexer.h, but this is not included in pcb-parser.cpp. Should it? When "make -j7" f

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

Hi Alex, I don’t like the top-side/bottom-side checkboxes (because I want to see both numbers at once), but I do like the other three. I think we need to move to a list or grid presentation, though. One of the other features we’ve talked about is user-defined attributes, so there might be mor

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

Hi!, I added stuff for footprints THT,SMD,virtual properties and now it's calculate area. But for me dialog is not very straight forward now. Can you please advice, what better to do? I attached 2 pics. I think, maybe right way is to add few checkboxes which will change dialog data as soon as yo