kicad-developers team mailing list archive

[jean-pierre charras <jp.charras@xxxxxxxxxx>]

Le 11/05/2012 14:44, Dick Hollenbeck a écrit :
> On 05/10/2012 02:34 PM, jean-pierre charras wrote:
> > Le 10/05/2012 18:21, Moses McKnight a écrit :
> > ...
> > > In the new designs, when you add a symbol, does it have a tag telling which library it came from? Currently if two libraries have
> > > a part with the same name, the part will be pulled from the library that is listed first in the list. If the part on the schematic
> > > had a tag for the library it came from, things would be a lot more flexible.
> > >
> > > Thanks,
> > > Moses
> > This is false, in fact things would be a lot less flexible.
>
> We are all entitled to our opinions.  I think the current design is broken, and the
> ambiguity of which "partname" is chosen, is a bigger problem than any you mention below:

Well, my answer was very unclear,
because in fact not relative to the future library handling (SWEET),
but rather to the current kicad code, with some enhancements relative to the components identification.

I was thinking Moses was interested by modifying the components identification in the current Kicad version
(New designs can be understood like the current Kicad version with enhancements,
not necessary the future SWEET version).

From the first "Kicad preference questions" mail,
there is a lot of new questions, some topics have changed
and we are far from first "Kicad preference questions"

Currently, it is no easy to add the library identification without breaking some things.

The next (should we say new?) Kicad design is made to do a more powerful (by far) component identification.
Therefore, and obviously, it will fix some issues that cannot easily fixed now just by some current code enhancements.

> > This problem has already generated a lot of mails.
> > Many guys are saying: I want to choose the library the component come from.
> > (i.e. have a tag for the library it came from).
> > But nobody think: what happens if I move my component from a library to an other
> > (i.e. when the tagged component does not exists anymore in the tagged lib)
> >
> > However this is a common case and should be supported,
> > because a schematic project is a living thing over the years, not just a thing made only once.
> >
> > Fix it is certainly not trivial and cannot be fixed "just by adding a tag".
> > This needs a carefully designed (and complex) code.



--
Jean-Pierre CHARRAS