On Fri, 2007-06-08 at 11:59 +0200, Bernd Jendrissek wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > A while ago I was trying something to attack the 1000-opamp-footprints > problem (aka the transistor problem) and it looked promising. But it > would have really helped me if the libgeda file format had a way to > uniquely identify a COMPLEX - more than just a refdes, which can easily > be duplicated in the current slotting mechanism. I'm thinking along the > lines of some sort of uuid=056e81a8-4c07-42e1-a64e-9d815d433368 style > attribute: something that, in C, can be converted into a pointer to a > COMPLEX. > > In about two weeks I'd like to add this to libgeda, when I will be free > from any "all your copyrights are belong to us" employment contract > clause. In the meantime I'd like to know of any objections, Super > Important recommendations, etc. > > I was thinking of just ripping some code from CVS where it generates > commitid attributes, but I'm open to any better ideas. I'm not sure if > I like the idea of just *numbering* all the COMPLEX'es in a schematic > file, since then I'd have to worry about keeping independent number > spaces from stomping on each other.
I believe there is already a name / number attached to each object. I'm not sure if you want a unique ID across all time, for all schematics or not, but that would require a large ID to make that likely. Take a look at http://www.brorson.com/gEDA/gEDA_Structures_20050108.pdf And how the object.name fields are produced, they "might" be what you want. Regards, -- Peter Clifton Electrical Engineering Division, Engineering Department, University of Cambridge, 9, JJ Thomson Avenue, Cambridge CB3 0FA Tel: +44 (0)7729 980173 - (No signal in the lab!) _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
