Implement more (and custom?) annotation schemes
Bug #1827503 reported by
Michael Kavanagh
This bug affects 18 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
New
|
Unknown
|
Bug Description
Allow annotations without a number:
https:/
Support for sheet.component reference numbering
https:/
Would like a new automatic annotation option in eeschema
https:/
eeschema: wish: schematic with many sheets: more adjustable annotation
https:/
eeschema: store value of "use first free number after" in every schematic sheet
https:/
tags: | added: eeschema feature.request |
description: | updated |
Changed in kicad: | |
importance: | Wishlist → Unknown |
status: | Expired → New |
To post a comment you must log in.
In lieu of having the particular annotation scheme I wanted within eeschema itself, I ended up writing a standalone program in Python that read the .sch files and applied my annotation scheme to them. I did that out of personal necessity, but it occurs to me that it might be a more-appropriate approach than trying to implement a bunch of different annotation schemes directly within eeschema that were each of use to only a few people.
The way it could work is that the program itself would be completely generic except that there would be a single function in it that supplied an annotation for a given component, on the basis of inputs like a sheet number, a base reference designator, and so on, and that the user could replace the contents of this function to create whatever annotation rule he/she happened to like.
Just a thought.