--- In [email protected], Dmitri Belimov <[EMAIL PROTECTED]> wrote:
> > There are "fields" with which you can assign properties to components. > > You can change the field name from it's default value "Field1" etc, > > and assign a value. You can edit these values on specific instances of > > components in a schematic, or you can edit them in alibrary to get a > > default value. > > Yes, I know. But I can`t export renamed name of field. I can`t add more field than default value. > I want add some field like Field9, Field10... > Using the csv export program you get columns exported by name rather than number, and it does not matter what order they are in. Also you are limited to 8 different fields **per item**, you can use as many different names as you like.....there is a fuller explanation in the program file. > > > 2. Export any fields to BOM list - value and name. Now I can`t > > export field sheet, and name of renamed fields. > > > > > > > Look in the files section of this group, I have written a program > > which export a BOM as a CSV for importing into spreadsheets, > > databases etc. It sorts and groups columns according to Field names > > rather than numbers, so it does not matter which order or subset of > > field names you use. This allows up to 8 fields from an infinite > > palette to be added to the standard fields of each component > > That`s good. I`ll look later. But make this in the KiCAD more better. Yes. The limitations on attributes is well noted in this group. Generally speaking I think we came to the conclusion that the best option would be an unlimited grid list for name/attribute pairs. But we are not developers ;-) I wrote the export program as a stopgap, I have no doubt something will be integrated in time (maybe I would do it if I understood how to compile KiCAD ;-) Personaly, if I ever got involved in KiCAD development, I would scrap the files and store projects in an SQLite file...so much easier to make global changes and get any kind of report. In the meantime however, I am (very) thankfull for what (others) have allready done :-) > > > > Eeshema/Usability > > > > > > 1. Make possible swith to properties of other component from > > properties of current component. Combo list. For > > > make easily edit properties a lot of components. Checkbox for change > > focus in viewly area to editing component. > > > > > > > I build my own library as I go along, one symbol per component with > > all properties pre set. > > I must define for each component: Market name, number in store, price, vendor, manufacturer part name, > replacement with same field. For socket need other part. I spend much time for > switch between propertie of components. > I think you should definitly have a look at the CSV exporter ;-)
