kicad-developers team mailing list archive
Mailing list archive
Re: eeschema NUMBER_OF_FIELDS
jean-pierre charras - INPG <jean-pierre.charras@...>
Fri, 03 Oct 2008 15:47:46 +0200
Thunderbird 188.8.131.52 (Windows/20080914)
Dick Hollenbeck a écrit :
jean-pierre charras - INPG wrote:
> Dick Hollenbeck a écrit :
>> jean-pierre charras wrote:
>>> Dick Hollenbeck a écrit :
>>>> What about using wxGrid for part of this dialog?
>>>> Any objections?
>>> No objections.
>>> Note: fields names are already editable in eeschema.
>> Except for the first one or two field names. I will research it and
>> duplicate current behavior.
> 4 fields names are not editable because they are reserved (REF, VALUE,
> FOOTPRINT and subsheet).
> Subsheet is not in use (and may be never used).
That is humorous. I think the field is named "Sheet" not Subsheet.
I have been using it as a place to store the name of a PDF datasheet for
the part. I have a BOM extractor I wrote in Java which creates a
CSV. The CSV can get loaded into a spreadsheet and contains the
datasheet *.PDF name as one of the columns. I never could figure out
what "Sheet" meant, so I came up with my own meaning I guess. :-)
What if we renamed to field to "Datasheet" and left it fixed?
Components already have a datasheet field.
All components ("root" components and aliases) have 3 doc fields:
- doc (this is a comment to help the user)
- keys works (to find them in libraries by keywords)
- doc file: this is like an url because it can be a filename or an
internet link (if starting by http:)
But because the field "Sheet" is not used, one can use it for a better
Maître de conférences
Directeur d'études 2ieme année.
Génie Electrique et Informatique Industrielle 2
Institut Universitaire de Technologie 1 de Grenoble
BP 67, 38402 St Martin d'Heres Cedex
Grenoble Image Parole Signal Automatique (GIPSA - INPG)
46, Avenue Félix Viallet
38031 Grenoble Cedex