On 3/23/2015 1:16 PM, Chris Pavlina wrote: > On Mon, Mar 23, 2015 at 01:07:33PM -0400, Wayne Stambaugh wrote: >> On 3/23/2015 12:12 PM, Chris Pavlina wrote: >>> I like your idea - I proposed it myself, but it was not well received ;) >>> [[snip]] >> >> Please see the discussion here on why this will not work. >> >> https://bugs.launchpad.net/kicad/+bug/1435338 >> >> I see no point in replacing one bug with another bug that doesn't fix >> the underlying problem. > > Haha, just kidding, I know :) > >> Rather than just copy the cache file, rename all of the footprints in >> the copied library with a prefix or suffix, i.e. 74LS00 in the cache >> becomes 74LS00_SCH in the new library. Then rename all the components >> in the schematic accordingly if the user chooses the new library option. >> This way there will be little chance of conflicting component names and >> the library search order is less likely to be an issue. This gives you >> the best of both worlds. You keep your existing components in the >> schematic and you can still use the updated components from the your >> libraries if you so choose. Obviously this still wont fix the library >> search ordering issue but it would be a more robust solution. > > Actually, I quite like this idea.
I know it's more work but it solves the component name clash issues and the user will still be able to use their normal libraries. > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp