As of commit 0015574a The text variable ${SHEETNAME} now always represents just the name of the sheet (e.g. “Sheet 2”), whereas before if the variable was used in the drawing sheet (i.e. the title block), it would display the path of the current sheet (e.g. “/Sheet 1/Sheet 2/”).
A new text variable ${SHEETPATH} has been introduced which will be replaced by the path of the current sheet (e.g. “/Sheet 1/Sheet 2/”).
A note: users with custom drawing sheets will have to manually edit the drawing sheet definition if they want to continue using the sheet path.
Includes better support for Router and DRC for tracks entering and leaving net-tie pads, and for copper graphic items shorting pads not listed in a group.
Interactive pdf outputs from the Schematic Editor, covering:
Hyperlinks (both external and “to page” links)
Sheet symbols become hyperlinks to the page in the pdf that they represent
Intersheet refs have a pop-up that allows to go to the pages where the global label is present (this likely will only work in full featured pdf readers, like Acrobat)
Example below navigating a pdf generated with the Schematic Editor, opened in Acrobat DC:
Again thanks to @JeffYoung for getting the intersheet refs popup working (as well as other fixes).
You can now choose to display a field’s name in addition to its value on the schematic sheet
You can now disallow autoplacement for particular fields, which can be useful when you want to have certain fields always show up in a certain place relative to the symbol graphics, but others to be autoplaced.
KiCad now supports database libraries, which use an external SQL database to store information about components. There is some preliminary documentation for those who are interested in testing it.
If you aren’t sure you need a database library, you probably don’t! (at least, not right now). This is an advanced feature intended for specific use cases at the moment. The primary audience for this feature is companies and organizations who already use a database for part management and wish to integrate their existing database with KiCad. We are also interested to see what other types of users do with this feature, and may explore having more features built in to KiCad regarding data management in the future. In the near term though, part data management will be done through external tools.
Attempt Finish Routing. Tries to automatically complete routing to the nearest ratsnest end. If it doesn’t succeed, will stop at the failure point to continue routing manually.
Attempt to Finish Selection (fake Autoroute): Will iteratively attempt to automatically route all selected routable items to their nearest ratsnest end. Will stop at any failure point for manual finish, then continue auto routing as much as possible.
Edit: Here’s a slightly more complicated example showing a filter + amplifier layout automatically routing:
