-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, Jun 08, 2007 at 11:36:47AM +0100, Peter Clifton wrote: > 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.
Ah, thanks for the link. Yes I noticed those while I was debugging, but I really need something more permanent - or at least more guaranteed. I need these two properties: - The ID must be unique over the whole design - perhaps over the universe. object.name is probably close enough here. - The ID must be permanent - must survive edits to the schematic. object.name fails here; it's assigned at runtime, not read in from the file. I'm going to need this COMPLEX "permalink" to be able to record which "symbolic" op-amp COMPLEX fits into which concrete op-amp package, so that you can have one *symbol* representing all the zillions of op-amp parts. And I will need to save these links into the file, hence the need for permanence. (Must survive hand-editing of schematics too.) - -- /"\ ASCII Ribbon Campaign - against html email \ / - against microsoft office attachments X - against text above fullquote below / \ - against lines longer than 79 characters -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGaZDpwyMv24BBd/gRAguEAJ9vy0fk0c92W3bYqvzso2+b6eIdMwCggpZ/ 0R9p3h1B7N0f8hxn7WDlO9I= =xs4n -----END PGP SIGNATURE----- _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
