Comment 2 for bug 1660196
Revision history for this message
| Wayne Stambaugh (stambaughw) wrote Re: [Bug 1660196] Re: Wish: different FP filters for aliased symbols | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
On 1/30/2017 9:01 AM, Chris Pavlina wrote:
> Allowing aliases to have their own values for other fields would also be
> nice. I have, for instance, an MPN (manufacturer's part number) field on
> most of my parts. One of these parts is ADP151AUJZ-v.v, which is a fixed
> voltage regulator that comes in multiple voltages. Aliases include
> ADP151AUJZ-1.2, ADP151AUJZ-3.3, etc. I've been forced to leave a {vout}
> placeholder in the MPN field to be edited by the user. It would be very
> nice if each alias could include the full MPN for that part!
>
> This all being said - there are some library management changes in the
> upcoming sch/lib file format that may already include this, but I don't
> remember. Wayne, any comments?
>
Yes, there is support for properties in the new library file format
which can be used to create "fully defined" symbols that inherit from a
base symbol. It's slightly different than the current alias scheme that
we currently use but much more versatile. Although this will most
likely change somewhat before the spec is finalize.