← Back to team overview

kicad-developers team mailing list archive

Re: [RFC PATCH] Single-click board update, take 2.

 

On 29.01.2016 16:49, Chris Pavlina wrote:
> Oh, it's definitely a dirty hack - but it's a dirty hack that is somewhat
> necessary, and used to be possible, and now it's not, so... regression, dude!
> :)
> 
> Yeah, yeah, I'm a spacebar heater, I know... :D
> 
> https://xkcd.com/1172/
> 
No, you're not :) I perfectly agree with your reasoning and I'll add an
option to disable component removal.

> I'd argue that while using a footprint as a via is a dirty hack, the simple
> concept of allowing footprints on the PCB that aren't on the schematic is
> *not*. Lots of people want to be able to place things like mounting holes
> without having to put them in the schematic. (Whether or not that's best
> practice is beside the point, it's very common.)

Most tools I've used require that the components on the schematic fully
match the PCB, but they also allow drawing mounting holes as 'free'
pads. This is another limitation of pcbnew - in Eagle/Altium you can
just draw an arbitrary pad straight on the PCB. In Kicad, it requires a
footprint (and so the sch/pcb inconsistency).

Cheers,
Tom


> 
> On Fri, Jan 29, 2016 at 04:47:38PM +0100, Tomasz Wlostowski wrote:
>> On 29.01.2016 16:23, Chris Pavlina wrote:
>>> Okay, after testing this, I actually have two "bug reports", one that I
>>> consider fairly important, and one that's minor.
>>>
>>> Important one: IMO there *needs* to be an option to only add or update
>>> components, not remove. Here's the list of suggested changes for a board where
>>> I manually added via stitching using a via "footprint" and the array tool:
>>>
>>> https://misc.c4757p.com/nooooooo.png
>>>
>>> I don't want to remove those!! It's not a 'standard' use case, perhaps, but
>>> it's still a regression, as I was previously able to make it keep those.
>>
>> Hi Chris,
>>
>> I wouldn't call it a regression. Stitching vias with single-pad
>> components is just a dirty hack we'll have to live with until we get a
>> new connection propagation algorithm. Until then, I agree we should have
>> an option preventing component removal.
>>
>>>
>>> Minor one: don't say "Netlist update successful!" in the list of _proposed_
>>> changes, it's a bit confusing as it seems to imply the changes have actually
>>> been made.
>>
>> Good catch!
>>
>> Tom
>>



Follow ups

References