Thread Previous • Date Previous • Date Next • Thread Next |
On 12/10/17 15:12, Kristoffer Ödmark wrote:
Sorry for double messages but one solution could be to use the Library stored documentation to autofill the FIELD variable IF it is empty. And then base all the functionality on the field variable? I could probably fix this if it seems an okay solution to everyone? This would basically be making the field variable overriding the properties information. But still not break anything from the libs. Or should this just be left as is until the new symbool format is implemented? On 10/12/2017 03:00 PM, Kristoffer Ödmark wrote:Hey! I noticed today that there are two places to store the datasheet information, one is in the Mandatory Field "Datasheet", and one is in the porperty of the part in the lib. These have different functionality in the schematic editor and in the library part editor. I think these should somehow be merged or one of them removed. As it is now, it is a bit confusing with the "Open Documentation" context menu, and the "Show Datasheet" button in the properties editor. For me, mergin every functionality into the field variable seems like the most robust way, since most other tools are using these field variables and that is the most accesible way, and since the Datasheet field is mandatory anyway, but can still be empty.
The field variable is the same for all aliases. That's why the kicad library convention does not allow it's use.We only use the datasheet property that is stored in the dcm file. (This property can differ for every alias.)
Thread Previous • Date Previous • Date Next • Thread Next |