To add N/C pins, add a property to the part witht the key NC and the value(s) of the pins that are NC separated by coma and no spaces.

Quick reference

S-a	Open the Place Pass spreadsheet
S-c	Open the Components spreadsheet
S-d	Open The design window
S-e	Open the Route Pass spreadsheet
S-f	Open the Footprints spreadsheet
S-g	Open the Route Spacing spreadsheet
S-h	Open the Density Graph window (Layout Plus only)
S-i	Open the Statistics spreadsheet (Layout Plus only)
S-k	Open the Packages spreadsheets
S-l	Open the Color spreadsheet
S-m	Open the Error Markers spreadsheet
S-n	Open the Nets spreadsheet
S-o	Open the Obstacles spreadsheet
S-p	Open the Apertures spreadsheet
S-q	Open the Query window
S-r	Open the Drills spreadsheet
S-s	Open the Post Process spreadsheet
S-t	Open the Padstacks spreadsheet
S-u	Open the Route Layer spreadsheet
S-w	Open the Route Sweep spreadsheet
S-x	Open the Text spreadsheet
S-y	Open the Layers spreadsheet

<color #ff7f27>There seems to be some different behaviours on connections, depending on what types of cennectors that are present. In some unknown cases, two power connectors with the same name in the same desing are not connected to the same net. It seems to have something to do with hierarcical connectors with the same name being present but connected to something else. Maybe it is the graphical connection of the hierarcical connector that takes precedence over named power nets? </color>

<color #ffc90e>Todo: Check priority on the resulting net names. If several different net names are graphically connected with wires, which net name/alias/power-net name decides the resulting net name when exported to Layout?</color>

Connection matrix for connections with the same name.

Same page

Same schematic

Same project

Only parts from the root-schematic is exported to Layout. For ohter parts to be exported, they have to be included as hierarchical blocks in a schematic that has the root schematic as its ancestor.

The same name for hierarchical block instances can be used in different schematics without colliding.

Names are case insensitive regarding function. However, some functions seem to be confused by the case. For example, when having same but different cased names for hierarchical connnectors they appear as different connectors on the block, but are connected together anyway.

A hierarchical block always lead to the oldest page in that schematic when descending the block.

Thermal reliefs are not generated on pads that are smaller than the thermal relief width. That is, pads that have one dimension that is smaller than the "Options→Thermal Relief Settings..→Spoke width" will be consumed by a copper pour.