Hierarchy operations (...)

• Down Schematic Go down into a symbol, opening up any underlying schematics. Basically this will open up an underlying schematic of the selected component if it exists in the source library search path. See the Resource File section on how to define this path.

  There are currently two ways of specifying that a symbol has an underlying schematic or schematics:

  1. The underlying schematic must have the same name as the symbol but have a .sch extension and must follow the _# suffix naming convention. See the Files section below on this convention.

  2. Attach an attribute to the symbol called source=filename.sch filename.sch is not a path to the symbol, but rather the basename (last file in the path specifier) of the symbol path. The underlying schematic will still be searched in the source-library path. You can specify multiple source= attributes. The underlying schematics will be opened in the order that the source= attribute is found.
  If there multiple underlying schematics, they will be loaded. Movement between the schematic pages is restricted (to the same level of the same set of underlying schematics) unless the rc keyword enforce-hierarchy is modified to allow for a freer hierarchy traversal mode. See the Resource File section for more info.

  It is also recommend that you maintain unique names for the various levels (when using the source= attribute) to avoid possible confusion. The hierarchy mechanisms are fairly new so expect some odd behavior (and please report it)

• Down Symbol This option will open up the symbol of the selected component.

  Once the symbol is open, the user can edit it and save it.

  At this time, the toplevel schematic will not see the symbol change unless the toplevel schematic is reloaded or File/Revert is executed. This will be fixed eventually.

• Up This option will move up the hierarchy (if there are pages above the currently displayed page).

• Documentation Open any documentation available for the selected symbol/component.

  The job is handed over to "gschemdoc", which makes a best-effort attempt of finding relevant documentation.

  The documention would normally be in PDF, HTML, text or image format, but gschemdoc tries to be as transparent as possible on this account.

  First and foremost, the attribute "documentation=" is assumed to point to the documentation. This attribute should either be the filename (basename) of the document, or it should be a complete URL.

  If it is a filename, and the file is found locally (in /usr/share/gEDA/documentation or otherwise), the relevant viewer will be initiated. Otherwise, a Google search for the document will be initiated.

  If there is no documentation attribute, the attributes "device" and possibly "value" will be consulted in much the same way as for "documentation". File searches will be made in forms of filenames like "device-value.pdf" and "device.pdf".

  Failing that, the file name for the symbol itself will be used as basis for the search.