© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I suppose I should actually have given a link to my own Python program in my last post. Although it works for me, I'm sure it's probably completely worthless to anybody else, and doesn't even have the user-replaceable function in it that I proposed, but it might give some focus regarding my suggestion for a standalone annotating program.
My own program assumes the eeschema has _already_ annotated the design (although it doesn't care what rule eeschema used when it did so) and it corrects those annotations according to its own ideas.
(The basic idea of my specific program is that sheet names in the parent drawing are things like "1", "2", "3", and so on, while the components in child blocks all have fields with the name "baseRefd" and values like "R1", "C3", "Q12", etc., and that the particular rule for forming the annotations in the child hierarchical blocks is to prefix the sheet name to the baseRefd to get reference designators like "1R1", "2C3", and so on. And there are a few special cases that alter the numbering somewhat.)
https:/