kicad-developers team mailing list archive

[Jason Whiteman <whitemanjason@xxxxxxxxx>]

Maybe my workflow in using Kicad is does not match the expectations of use
- but I avoid back-annotation from CvPCB because I generally populate
"footprint" with what should be regarded as "package" (0402, etc) and keep
this "wrong" usage throughout.  Back annotation from CvPCB (manual -
previous method) would overwrite my package designations on the schematic.
 I've thought about updating my library to include package properties (and
other properties I've "made up" such as INSTALL for part stuffing, etc).
 And perhaps Kicad has evolved since I started internally using it
"incorrectly" -- but, if not, it may be worthwhile to define some standards
and push these to the stock library/modules.

I point this out because perhaps how I fell into using Kicad is shared --
and perhaps there is something that can be modified in the software to
enforce or at least nurture the correct/expected usage (from the software's
perspective).

At any rate - back/forward annotation (primarily between PCBnew and
EESchema) are on my TODO list to reduce the click count -- something you're
accomplishing for CvPCB.  These are cases where I think enabling more
automation is a good thing as long as there's a lever to turn the
automation off.

Regards,
Jason



On Mon, Jul 7, 2014 at 12:41 AM, Lorenzo Marcantonio <
l.marcantonio@xxxxxxxxxxxx> wrote:

> On Mon, Jul 07, 2014 at 09:34:46AM +0200, jp charras wrote:
> > This is not really a bug, but a limitation of complex hierarchies.
> > But is it really a limitation ?
> > When your are using complex hierarchies you are doing that because you
> > want your changes (schematic modification, change a component value, or
> > a footprint name ...) made only once but reproduced 6 times on your
> board.
>
> It would be somewhat silly to accept a different 'package' for each
> submodule.  A different value could be remotely useful (for filter banks
> or such kind of module), but IMHO it would be better to copy the whole
> schematic page (i.e. not using a complex hier.). Seems a reasonable
> limitation to me.
>
> It could be useful if at least a warning could be given ("be careful
> that your subsheet have a problem") but I'd would do nothing more than
> that.
>
>
> --
> Lorenzo Marcantonio
> Logos Srl
>
> _______________________________________________
> 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
>