Hey Nick, KICAD_SYS_SYMBOL_DIR is much more readable than KISYSSYM. I was actually thinking about changing KISYSMOD to KICAD_SYS_FOOTPRINT_DIR for the sake of consistency in spite of the obvious grumbling it will cause. I just haven't gotten around to getting other user's opinions yet. At some point before the stable 5 release, I will change one of the two variable names so they are consistent.
Cheers, Wayne On 12/11/2016 3:27 PM, Nick Østergaard wrote: > Hi Wayne > > I just noticed, https://github.com/KiCad/kicad-library/pull/805 > > I see that you expect KICAD_SYS_SYMBOL_DIR instead of KISYSSYM. I > think the latter is better for the sake of consistency. > > 2016-12-10 16:39 GMT+01:00 Wayne Stambaugh <[email protected]>: >> I just pushed the commit for loading the symbol library table. The >> first time you run Eeschema with the changes, you will be prompted about >> loading the default symbol library table. This is the same mechanism >> that is implemented in the footprint library table code so it will be >> familiar. Unless you have a fairly recent copy of the kicad library >> repo from github, an empty symbol library table will be created in your >> kicad config folder. You will need to copy the full version of >> sym-lib-table from the kicad library repo to your kicad config folder if >> this is the case. Please note that the symbol library table is not >> being used yet. This is just loads the the table. If all goes well, >> the symbol library table will be fully implemented before the holiday break. >> >> Cheers, >> >> Wayne >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : [email protected] >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
