> If the answer is: modify the http lib or the std lib, then I think that's a gap. If the answer is: make your project local symbol, but it can't inherit from the httplib, then I think that's a gap.
Not quite either of the above. 1) Copy the part into a shared global library (not a project library) that is linked to your HTTP lib 2) Modify the HTTP lib One idea with using a HTTP or database library is to get *reproducible* results on multiple different computers. You can't do that by saying you want to allow arbitrary changes to the pin layout of the symbol without touching the library. If you insist on changing the pin layout of your symbols per-project, the way to do it that doesn't result in broken library links is to just put multiple symbols into your library. On Wed, Jul 15, 2026 at 5:34 PM Dave F <[email protected]> wrote: > For example, I place a part from the http lib. It references the standard > library symbol which looks like this: > > [image: library.png] > But my schematic needs this: > > [image: custom.png] > > How can I keep a live link to all of the httplib parameters, and still use > my altered symbol in my project library, without modifying anything in the > kicad symbol lib, or the http lib? If the current Kicad can do this, then > I honestly could not find it, but I have looked. If the answer is: modify > the http lib or the std lib, then I think that's a gap. If the answer is: > make your project local symbol, but it can't inherit from the httplib, then > I think that's a gap. > > On Wednesday, July 15, 2026 at 4:03:03 PM UTC-5 [email protected] wrote: > >> >> On Wed, Jul 15, 2026 at 1:39 PM Dave F <[email protected]> wrote: >> >>> >>> - There is no clean way to support two different schematics that use >>> arrange the pins of, say, a microcontroller differently. Any method you >>> choose with the current design loses the ability to update either >>> component, schematic, or library at some level. >>> >>> >> This is not a true statement. Library symbols can support multiple body >> styles. Pins are indexed by unit and body style, so you can have different >> body styles with different pin groupings in your library and your layout >> can choose one or the other. >> >> I think that the upshot you are hearing here is that your proposed change >> is not fully researched and unlikely to be accepted in the KiCad code base >> as-is. >> >> I would recommend researching how you might use the existing >> functionality to meet your needs first and then, if there is a gap, >> focusing on a smaller, targeted use case to close that gap. >> >> Seth >> >> >> Seth Hillbrand >> *Lead Developer* >> +1-530-302-5483 <(530)%20302-5483> >> Long Beach, CA >> www.kipro-pcb.com [email protected] >> >> -- You received this message because you are subscribed to the Google Groups "KiCad Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/kicad.org/d/msgid/devlist/CA%2BqGbCAGFG5XCqzRoifDu1feeRWCnkbdOE3BYcoMOM2LSBsOhg%40mail.gmail.com.
