Re: [Kicad-developers] Pcbnew zoom to fit behavior changed

Hi Andrew, Yes it was basically reverted (keeping a few fixes) based on feedback and conversations. Too many people preferred the old behavior. -Jon On Fri, Jun 14, 2019 at 6:20 PM Andrew Lutsenko wrote: > It appears this was undone? Zoom-to-fit ignores the worksheet again. > Curious for the

Re: [Kicad-developers] Pcbnew zoom to fit behavior changed

It appears this was undone? Zoom-to-fit ignores the worksheet again. Curious for the reasoning behind that decision. On Mon, May 27, 2019 at 4:22 PM Andrew Lutsenko wrote: > Thanks Jon, now this makes sense. > With ability to disable worksheet in items panel to revert to old behavior > I am

Re: [Kicad-developers] Upgrade warnings

+1 > On 14 Jun 2019, at 18:15, Wayne Stambaugh wrote: > > +1 > > On 6/14/19 12:21 PM, Seth Hillbrand wrote: >> Hi Devs- >> >> I just noticed that we are displaying a warning (Attached) when opening >> v5 files with the new fill algorithm. >> >> I like the idea of warning users that features

Re: [Kicad-developers] [Patch] cvpcb Usability Improvements

Hey Ian, On 5/31/19 6:13 PM, Ian McInerney wrote: > Attached is a patchset that includes some upgrades to the usability of > cvpcb, namely the following: > > * Include a line below the footprint description giving the URI of the > source library. This allows people to see where the library is

Re: [Kicad-developers] CMake minimum version

On 6/14/19 2:27 PM, Seth Hillbrand wrote: On 2019-06-14 14:12, jp charras wrote: Le 14/06/2019 à 19:49, Jon Evans a écrit : +1 Speaking of that page on the website, I think we can remove Ubuntu 16.04 and 17.10 from the table now that they are unsupported. Be careful: Ubuntu 16.04 LTS is

Re: [Kicad-developers] CMake minimum version

On 2019-06-14 14:27, Seth Hillbrand wrote: On 2019-06-14 14:12, jp charras wrote: Le 14/06/2019 à 19:49, Jon Evans a écrit : +1 Speaking of that page on the website, I think we can remove Ubuntu 16.04 and 17.10 from the table now that they are unsupported. Be careful: Ubuntu 16.04 LTS is

Re: [Kicad-developers] CMake minimum version

Le 14/06/2019 à 20:26, Wayne Stambaugh a écrit : > JP, > > On 6/14/19 2:12 PM, jp charras wrote: >> Le 14/06/2019 à 19:49, Jon Evans a écrit : >>> +1 >>> Speaking of that page on the website, I think we can remove Ubuntu 16.04 >>> and 17.10 from the table now that they are unsupported. >>> >> >>

Re: [Kicad-developers] CMake minimum version

On 2019-06-14 14:12, jp charras wrote: Le 14/06/2019 à 19:49, Jon Evans a écrit : +1 Speaking of that page on the website, I think we can remove Ubuntu 16.04 and 17.10 from the table now that they are unsupported. Be careful: Ubuntu 16.04 LTS is supported until 2021. Only Ubuntu 14.04 LTS

Re: [Kicad-developers] CMake minimum version

JP, On 6/14/19 2:12 PM, jp charras wrote: > Le 14/06/2019 à 19:49, Jon Evans a écrit : >> +1 >> Speaking of that page on the website, I think we can remove Ubuntu 16.04 >> and 17.10 from the table now that they are unsupported. >> > > Be careful: > Ubuntu 16.04 LTS is supported until 2021. >

[Kicad-developers] [Patch] bitmap2component: Support for multiple input units.

Hi I have made a patch to bitmap2component so that it supports entering dimensions in mm, inches, mils, and DPI. It is now also possible to lock the aspectratio to the ratio of the input bitmap. When the aspect ratio is locked and one dimension is changed, the other one is automatically

Re: [Kicad-developers] CMake minimum version

Le 14/06/2019 à 19:49, Jon Evans a écrit : > +1 > Speaking of that page on the website, I think we can remove Ubuntu 16.04 > and 17.10 from the table now that they are unsupported. > Be careful: Ubuntu 16.04 LTS is supported until 2021. Only Ubuntu 14.04 LTS release support is now end of life

Re: [Kicad-developers] CMake minimum version

+1 Speaking of that page on the website, I think we can remove Ubuntu 16.04 and 17.10 from the table now that they are unsupported. On Fri, Jun 14, 2019 at 1:44 PM Wayne Stambaugh wrote: > I'm fine with this. > > On 6/13/19 4:38 PM, Seth Hillbrand wrote: > > Hi All- > > > > Right now, our

Re: [Kicad-developers] CMake minimum version

I'm fine with this. On 6/13/19 4:38 PM, Seth Hillbrand wrote: > Hi All- > > Right now, our minimum cmake version is 2.8.12.  I'd like to bump this > up to 3.0.2.  This will assist in cleaning up a number of workarounds in > our build system.  3.0.2 or greater appears to be available for all >

Re: [Kicad-developers] Ratsnest options

On 6/14/19 7:21 AM, Jeff Young wrote: > Hi Seth, > > See below: > >> On 14 Jun 2019, at 00:22, Seth Hillbrand > > wrote: >> >> On 2019-06-13 10:26, Jeff Young wrote: >>> So I’ll be the contrary one. >>> First, I do agree with getting the number of access points down.

Re: [Kicad-developers] Upgrade warnings

+1 On 6/14/19 12:21 PM, Seth Hillbrand wrote: > Hi Devs- > > I just noticed that we are displaying a warning (Attached) when opening > v5 files with the new fill algorithm. > > I like the idea of warning users that features have changed that will > affect their boards.  However, I'd like to put

[Kicad-developers] Upgrade warnings

Hi Devs- I just noticed that we are displaying a warning (Attached) when opening v5 files with the new fill algorithm. I like the idea of warning users that features have changed that will affect their boards. However, I'd like to put this into a more sustainable format. There are a

Re: [Kicad-developers] Immediate actions

On 6/14/19 10:10 AM, Jeff Young wrote: > Hi Wayne, > >> On 14 Jun 2019, at 14:42, Wayne Stambaugh wrote: >> >> On 6/14/19 7:59 AM, Jeff Young wrote: >>> My plan had been to support both two-step (first selects tool; second draws >>> object) and immediate (always draws) actions, and let the user

Re: [Kicad-developers] Immediate actions

Jeff,In your case of moving a part, it would be better to select move tool, move one or more parts, then dismiss to return to routing. In complex boards, routing a trace often involve moving more than one part. Just my two cents after using cad tools for 30 years. Jean-Paul N1JPL  Sent from

Re: [Kicad-developers] Immediate actions

Hi Wayne, > On 14 Jun 2019, at 14:42, Wayne Stambaugh wrote: > > On 6/14/19 7:59 AM, Jeff Young wrote: >> My plan had been to support both two-step (first selects tool; second draws >> object) and immediate (always draws) actions, and let the user assign the >> hotkey to the one they prefer.

Re: [Kicad-developers] Immediate actions

That was my thought: sort of a push-tool/pop-tool. > On 14 Jun 2019, at 14:36, Seth Hillbrand wrote: > > On 2019-06-14 07:59, Jeff Young wrote: >> My plan had been to support both two-step (first selects tool; second >> draws object) and immediate (always draws) actions, and let the user >>

Re: [Kicad-developers] Immediate actions

On 6/14/19 7:59 AM, Jeff Young wrote: > My plan had been to support both two-step (first selects tool; second draws > object) and immediate (always draws) actions, and let the user assign the > hotkey to the one they prefer. > > But I’m discovering a bunch of things that are unsettling about

Re: [Kicad-developers] Immediate actions

On 2019-06-14 07:59, Jeff Young wrote: My plan had been to support both two-step (first selects tool; second draws object) and immediate (always draws) actions, and let the user assign the hotkey to the one they prefer. But I’m discovering a bunch of things that are unsettling about it. It hard

[Kicad-developers] Immediate actions

My plan had been to support both two-step (first selects tool; second draws object) and immediate (always draws) actions, and let the user assign the hotkey to the one they prefer. But I’m discovering a bunch of things that are unsettling about it. It hard to discover if we chose the default

Re: [Kicad-developers] Ratsnest options

Hi Seth, See below: > On 14 Jun 2019, at 00:22, Seth Hillbrand wrote: > > On 2019-06-13 10:26, Jeff Young wrote: >> So I’ll be the contrary one. >> First, I do agree with getting the number of access points down. >> However, I find myself turning the ratsnest on and off a lot. And the >>

Re: [Kicad-developers] Janitor broken...

Hi Ian, I apologize for that. Janitor had some problems that I fixed yesterday, but in the process it started marking the released bugs as committed. I think most of them are already reverted to 'released', but I will double check now. Cheers, Orson On 6/14/19 12:16 AM, Ian McInerney wrote: >

Re: [Kicad-developers] Ratsnest options

On 14.06.2019 2:06, Reece R. Pollack wrote: Jon, May I suggest making the net and net class listings two different tabs? I'd rather not have to scroll past a few hundred nets to get to the net class listing. Or two scroll areas on the same tab, though I think separate tabs would be better.