Interestingly enough, it turns out that I had a file named .eeschema in my home directory that must have been left over from running eeschema in standalone with a pre-symbol table version. Running in standalone mode, this file gets loaded as the Eeschema configuration. My file (attached) had a bunch of old library links.
It got loaded from "LoadAllLibraries" that gets called (Project::SchLibs()) after we place a part to load the cache library.
@Wayne- We could force this to ignore the config file libs unless we are remapping but this would probably cause issues if users skipped the remapping step. Maybe we set a project variable "m_loadOldLibs" but I dislike the idea of polluting the class. More elegant would probably be splitting the loading of legacy tables into a separate function to be specifically called by remap. Do you have thoughts/preference on this?
BTW, on windows this is probably "%USERPROFILE%\eeschema.ini"
Interestingly enough, it turns out that I had a file named .eeschema in my home directory that must have been left over from running eeschema in standalone with a pre-symbol table version. Running in standalone mode, this file gets loaded as the Eeschema configuration. My file (attached) had a bunch of old library links.
It got loaded from "LoadAllLibraries" that gets called (Project: :SchLibs( )) after we place a part to load the cache library.
@Wayne- We could force this to ignore the config file libs unless we are remapping but this would probably cause issues if users skipped the remapping step. Maybe we set a project variable "m_loadOldLibs" but I dislike the idea of polluting the class. More elegant would probably be splitting the loading of legacy tables into a separate function to be specifically called by remap. Do you have thoughts/preference on this?
BTW, on windows this is probably "%USERPROFILE% \eeschema. ini"