← Back to team overview

kicad-developers team mailing list archive

Re: Settable clearances

 

This happened last stable release.  Users wait to the last minute and
then make a request for a new feature.  If this would have been proposed
six months ago, it probably would be part of the v5 release.  The
feature itself is a good idea but it will have to be deferred to some
later version.  We really need to stay focused on the v5 release.  It's
too easy to give into every whim and just keep pushing back v5.  This
happened somewhat in v4 and it took a long time to get from feature
freeze to release so I'm trying to prevent that from happening again.
We are never going to win this fight.  There will always be people who
think we should push back a stable release for some new feature.

Wayne

On 3/5/2018 8:59 AM, Jon Evans wrote:
> I can certainly help check it.  I think Wayne would have to make a call
> as to whether or not it's too big a change to introduce now.
> 
> -Jon
> 
> On Mon, Mar 5, 2018 at 7:59 AM, hauptmech <hauptmech@xxxxxxxxx
> <mailto:hauptmech@xxxxxxxxx>> wrote:
> 
>     While testing version 5 I realized that clearances are still not
>     settable (like track width or via size) and my life is going to be
>     miserable if I have to continue with my current work flow which is
>     to change the default netclass clearance to the desired clearance
>     constantly as I lay down different tracks which require different
>     clearances even though they are part of the some net.
> 
>     There is a previous thread detailing why netclass is not sufficient
>     for all use cases. Search for netclass in the subject.
> 
>     Anyway, I wrote most of a patch today (it's 1am in my timezone now)
>     and expect to finish it tomorrow. I believe I have a solution which
>     will be useful for those that need it and mostly invisible to those
>     that don't. 
> 
>     The question is whether there is a core developer willing to check,
>     sign off, and help sell it for inclusion in 5. (I'm stuck using
>     whatever the current stable version of kicad is when I'm working)
> 
>     This is a huge pain point for me and I'm willing to negotiate a
>     small bounty if that helps.
> 
> 
> 
>     _______________________________________________
>     Mailing list: https://launchpad.net/~kicad-developers
>     <https://launchpad.net/~kicad-developers>
>     Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>     <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>     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@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
> 


Follow ups

References