docs/wiki/geda-gschem_ug.fr.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html>
   4 <head>
   5   <title></title>
   6   <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
   7   <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
   8   <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
   9
  10   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  11 </head>
  12 <body>
  13
  14
  15 <h1 class="sectionedit860"><a name="guide_de_l_utilisateur_gschem_geda" id="guide_de_l_utilisateur_gschem_geda">Guide de l&#039;utilisateur gschem gEDA</a></h1>
  16 <div class="level1">
  17
  18 <p>
  19 by: Ales Hvezda / September 21st, 2003
  20 </p>
  21
  22 <p>
  23 The latest version of this document may be found at: <a href="http://geda.seul.org/wiki/geda:gschem_ug" class="urlextern" title="http://geda.seul.org/wiki/geda:gschem_ug"  rel="nofollow">http://geda.seul.org/wiki/geda:gschem_ug</a>
  24 </p>
  25
  26 <p>
  27 This document is released under the <a href="geda-gfdl.html" class="wikilink1" title="geda-gfdl.html">GNU Free Documentation License (GFDL)</a>.
  28 </p>
  29
  30 <p>
  31
  32 Please report any errors/inconsistencies in this document by commenting in the Discussion area at the bottom of the associated page.
  33 </p>
  34
  35 </div>
  36 <!-- EDIT860 SECTION "Guide de l'utilisateur gschem gEDA" [1-409] -->
  37 <h1 class="sectionedit861"><a name="about_this_document" id="about_this_document">About this document ...</a></h1>
  38 <div class="level1">
  39
  40 <p>
  41 gEDA gschem Users Guide
  42 </p>
  43
  44 <p>
  45 This document was generated using the LaTeX2HTML translator Version 2002-2-1 (1.70)
  46 </p>
  47
  48 <p>
  49 Copyright © 1993, 1994, 1995, 1996, Nikos Drakos, Computer Based Learning Unit, University of Leeds.
  50 Copyright © 1997, 1998, 1999, Ross Moore, Mathematics Department, Macquarie University, Sydney.
  51 </p>
  52
  53 <p>
  54 The command line arguments were:
  55 latex2html -local_icons gschem
  56 </p>
  57
  58 <p>
  59 The translation was initiated by Ales Hvezda on 2005-08-20
  60 </p>
  61
  62 </div>
  63 <!-- EDIT861 SECTION "About this document ..." [410-882] -->
  64 <h1 class="sectionedit862"><a name="introduction" id="introduction">Introduction</a></h1>
  65 <div class="level1">
  66
  67 <p>
  68 This document describes the installation, configuration, and operation of the <strong>gschem</strong> application.<br/>
  69
  70 This document does not describe the process of generating schematics. For this, refer to the various tutorials on using the gEDA Tool Suite:
  71 </p>
  72 <ul>
  73 <li class="level1"><div class="li"> <a href="geda-gschem_warmup.html" class="wikilink1" title="geda-gschem_warmup.html">Bill Wilson&#039;s gschem warmup</a></div>
  74 </li>
  75 <li class="level1"><div class="li"> Bill Wilson&#039;s <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">gschem and pcb tutorial</a></div>
  76 </li>
  77 <li class="level1"><div class="li"> “Optical Proximity Sensor for Robots (Part 1), Simple PCB Design with the gEDA Suite”, by Stuart Brorson (March 2006 Circuit Cellar article)</div>
  78 </li>
  79 <li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf" class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"  rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
  80 </li>
  81 <li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html" class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"  rel="nofollow">&quot;Circuit simulation using gEDA and SPICE -- HOWTO&quot; by Stuart Brorson</a></div>
  82 </li>
  83 <li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/magazine/176toc.htm" class="urlextern" title="http://www.circuitcellar.com/magazine/176toc.htm"  rel="nofollow">&quot;gEDA Design Suite for Linux&quot; by Stuart Brorson, Ales Hvezda, &amp; Dan McMahill (03 Mar 2005 Circuite Cellar article)</a></div>
  84 </li>
  85 <li class="level1"><div class="li"> <a href="http://www.linuxjournal.com/article/8438" class="urlextern" title="http://www.linuxjournal.com/article/8438"  rel="nofollow">&quot;Circuit Design on Your Linux Box Using gEDA&quot; by Stuart Brorson (29 November 2005 Linux Journal article)</a></div>
  86 </li>
  87 <li class="level1"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
  88 </li>
  89 <li class="level1"><div class="li"> And, of course, <a href="http://www.google.com/search?hl=en&amp;lr=&amp;q=gEDA+%22schematic+capture%22+tutorial&amp;btnG=Search" class="urlextern" title="http://www.google.com/search?hl=en&amp;lr=&amp;q=gEDA+%22schematic+capture%22+tutorial&amp;btnG=Search"  rel="nofollow">Google is your friend</a>.</div>
  90 </li>
  91 </ul>
  92
  93 <p>
  94
  95 Ce document suppose que vous comprenez les bases de la capture de schéma. Par exemple: vous comprenez ce qu’un composant représente et que les liaisons et les bus interconnectent ces composants pour former un schéma, etc… For a basic understanding of the various work-flows available in the gEDA Tool Suite, please read the above tutorials. For more detailed understanding of specific tool issues, please refer to <a href="docs-20060124-gschem_ug-how_to_ask_questions.html" class="wikilink2" title="docs-20060124-gschem_ug-how_to_ask_questions.html">How To Ask Questions</a> and to the <a href="docs-20060124-gschem_ug-resources.html" class="wikilink2" title="docs-20060124-gschem_ug-resources.html">Resources</a>.
  96 </p>
  97
  98 </div>
  99 <!-- EDIT862 SECTION "Introduction" [883-2837] -->
 100 <h1 class="sectionedit863"><a name="overview" id="overview">Overview</a></h1>
 101 <div class="level1">
 102
 103 <p>
 104 <strong>gschem</strong> is the schematic capture program in the gEDA Tool Suite. Its purpose is to facilitate the graphical input of:
 105 </p>
 106 <ul>
 107 <li class="level1"><div class="li"> circuit schematics</div>
 108 </li>
 109 <li class="level1"><div class="li"> component symbols</div>
 110 </li>
 111 <li class="level1"><div class="li"> block diagrams</div>
 112 </li>
 113 </ul>
 114
 115 <p>
 116
 117 Once <strong>gschem</strong> has been used to enter the symbols/schematics for your design, several gEDA Tool Suite “utility” programs are used to extract information for other purposes:
 118 </p>
 119 <ul>
 120 <li class="level1"><div class="li"> <strong>gattrib</strong> – <strong>gattrib</strong> is a gEDA Tool Suite productivity aid. <strong>gattrib</strong> reads a [hierarchical set of] gschem schematic files and creates a spreadsheet showing all components in rows, with the associated component attributes listed in the columns. It allows the user to add, modify, or delete component attributes outside of <strong>gschem</strong>, and then save the .sch files.</div>
 121 </li>
 122 <li class="level1"><div class="li"> <strong>gnetlist</strong> – A tool that converts a [hierarchical set of] schematic files into an equivalent netlist (a textual representation of a schematic) in various formats. Various gnetlist back-ends are used to create:</div>
 123 <ul>
 124 <li class="level2"><div class="li"> Bill of Materials (BOM) files.</div>
 125 </li>
 126 <li class="level2"><div class="li"> Design Rule Checks (DRCs).</div>
 127 </li>
 128 <li class="level2"><div class="li"> Netlist files for use as input to various printed circuit board layout programs (e.g., Allegro, PADS, <strong>pcb</strong> (part of the gEDA Tool Suite), Protell, Tango, RACAL-REDAC, etc.).</div>
 129 </li>
 130 <li class="level2"><div class="li"> Files for input to SPICE simulation programs.</div>
 131 </li>
 132 <li class="level2"><div class="li"> VHDL code.</div>
 133 </li>
 134 <li class="level2"><div class="li"> Verilog code.</div>
 135 </li>
 136 <li class="level2"><div class="li"> etc.</div>
 137 </li>
 138 </ul>
 139 </li>
 140 <li class="level1"><div class="li"> <strong>grenum</strong> – <strong>grenum</strong> is a gEDA Tool Suite productivity aid that will renumber the reference designators (i.e., refdes) in a [hierarchical set of] schematic files.</div>
 141 </li>
 142 <li class="level1"><div class="li"> <strong>gsch2pcb</strong> – The prefered method to create a netlist for the <strong>pcb</strong> printed circuit board layout tool (part of the gEDA Tool Suite).</div>
 143 </li>
 144 <li class="level1"><div class="li"> <strong>gspiceui</strong> – GNU Spice <acronym title="Graphical User Interface">GUI</acronym> (i.e., <strong>gspiceui</strong>) provides a <acronym title="Graphical User Interface">GUI</acronym> for freely available Spice electronic cicuit simulation engines (e.g., <strong>gnucap</strong> and <strong>ngspice</strong>). It uses <strong>gnetlist</strong> (to convert schematic files to net list files) and <strong>gwave</strong> (to display simulation results). gSchem is the preferred schematic capture tool.</div>
 145 </li>
 146 <li class="level1"><div class="li"> <strong>gsymcheck</strong> – A checker for symbols created with gEDA Tool Suite (e.g., <strong>gschem</strong>, <strong>tragesym</strong>, etc.).</div>
 147 </li>
 148 <li class="level1"><div class="li"> <strong>pcb</strong> – A tool for the layout of printed circuit boards.</div>
 149 </li>
 150 <li class="level1"><div class="li"> <strong>refdes_renum</strong> – Reads a [hierarchical set of] <strong>gschem</strong> schematic files and renumbers all reference designators. The reference designators are numbered starting with 1 and the old schematic file is replaced by the modified schematic file.</div>
 151 </li>
 152 <li class="level1"><div class="li"> <strong>tragesym</strong> – A python script that creates geda symbols from structured textfiles. The symbols usually need to be “cleaned up” in gschem.</div>
 153 </li>
 154 </ul>
 155 <div class="table sectionedit864"><table class="inline">
 156         <tr class="row0">
 157                 <td class="col0"> <a href="media/geda/gschem_workflow_01.jpg" class="media" target="_blank" title="geda:gschem_workflow_01.jpg"><img src="media/geda/gschem_workflow_01.jpg" class="media" alt="" /></a> </td>
 158         </tr>
 159 </table></div>
 160 <!-- EDIT864 TABLE [5381-5417] -->
 161 </div>
 162 <!-- EDIT863 SECTION "Overview" [2838-5418] -->
 163 <h1 class="sectionedit865"><a name="resources" id="resources">Resources</a></h1>
 164 <div class="level1">
 165
 166 <p>
 167 The following on-line resources are useful for designers using <strong>gschem</strong>:
 168 </p>
 169 <ul>
 170 <li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html" class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"  rel="nofollow">Bill Wilson&#039;s gschem warmup tutorial</a> – If you are new to the gEDA tools, read this before you read Bill&#039;s “Bill Wilson&#039;s gsch2pcb tutorial”.</div>
 171 </li>
 172 <li class="level1"><div class="li"> <a href="geda-gsch2pcb_tutorial.html" class="wikilink1" title="geda-gsch2pcb_tutorial.html">Bill Wilson&#039;s gschem and pcb tutorial</a> – If you are new to the gEDA tools, this tutorial will bring you up to speed quickly.</div>
 173 </li>
 174 <li class="level1"><div class="li"> <a href="http://www.circuitcellar.com/" class="urlextern" title="http://www.circuitcellar.com/"  rel="nofollow">Circuit Cellar Magazine</a> – Practical, hands-on applications and solutions for embedded designers:</div>
 175 <ul>
 176 <li class="level2"><div class="li"> gEDA Design Suite for Linux, by Stuart Brorson, Ales Hvezda, &amp; Dan McMahill, Circuit Cellar magazine, March 2005 (Issue 176), p. 12</div>
 177 </li>
 178 <li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 1): Simple PCB Design with the gEDA Suite, by Stuart Brorson, Circuit Cellar magazine, March 2006 (Issue 188), p. 48</div>
 179 </li>
 180 <li class="level2"><div class="li"> Optical Proximity Sensor for Robots (Part 2): Open-Source PCB Layout Editor, by Stuart Borson, Circuit Cellar magazine, April 2006 (Issue 189), p. 40</div>
 181 </li>
 182 </ul>
 183 </li>
 184 <li class="level1"><div class="li"> <a href="http://www.geda.seul.org/index.html" class="urlextern" title="http://www.geda.seul.org/index.html"  rel="nofollow">gEDA Project home page</a> – The homepage for the gEDA Tools Suite. A rather mature site, includes (but not limited to):</div>
 185 <ul>
 186 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/news/index.html" class="urlextern" title="http://www.geda.seul.org/news/index.html"  rel="nofollow">News</a> – from 2002</div>
 187 </li>
 188 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/screenshots/index.html" class="urlextern" title="http://www.geda.seul.org/screenshots/index.html"  rel="nofollow">Screenshots</a> – <strong>gschem</strong> in action</div>
 189 </li>
 190 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/tools/index.html" class="urlextern" title="http://www.geda.seul.org/tools/index.html"  rel="nofollow">Tools</a> – links to project homepages</div>
 191 </li>
 192 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/download.html" class="urlextern" title="http://www.geda.seul.org/download.html"  rel="nofollow">Download</a> – <acronym title="International Organization for Standardization">ISO</acronym> images, binaries, and sources</div>
 193 </li>
 194 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/mailinglist/index.html" class="urlextern" title="http://www.geda.seul.org/mailinglist/index.html"  rel="nofollow">Lists</a> – e-mail list subscription and archives</div>
 195 </li>
 196 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/docs/index.html" class="urlextern" title="http://www.geda.seul.org/docs/index.html"  rel="nofollow">Docs</a> – current gEDA/gaf documentation (not gEDA Tools Suite documentation), wiki, slide presentations</div>
 197 </li>
 198 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/developer.html" class="urlextern" title="http://www.geda.seul.org/developer.html"  rel="nofollow">Devel</a> – nonymous <acronym title="Concurrent Versions System">CVS</acronym> access</div>
 199 </li>
 200 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/search.html" class="urlextern" title="http://www.geda.seul.org/search.html"  rel="nofollow">Search</a> – by Google</div>
 201 </li>
 202 <li class="level2"><div class="li"> <a href="http://www.geda.seul.org/links.html" class="urlextern" title="http://www.geda.seul.org/links.html"  rel="nofollow">Links</a> – links associated with gEDA, projects developed using gEDA Tools Suite, gEDA-related press</div>
 203 </li>
 204 </ul>
 205 </li>
 206 <li class="level1"><div class="li"> <a href="http://bugs.launchpad.net/geda" class="urlextern" title="http://bugs.launchpad.net/geda"  rel="nofollow">gEDA Bug Tracker</a> – On launchpad</div>
 207 </li>
 208 <li class="level1"><div class="li"> <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda" class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda"  rel="nofollow">gEDA Project&#039;s Wiki</a> – All things related to the gEDA Tools Suite.</div>
 209 </li>
 210 <li class="level1"><div class="li"> <a href="http://www.gedasymbols.org" class="urlextern" title="http://www.gedasymbols.org"  rel="nofollow">gedasymbols.org</a> – On-line repository of user-developed symbols for <strong>gschem</strong>, SPICE models, and footprints for <strong>pcb</strong>.</div>
 211 </li>
 212 <li class="level1"><div class="li"> John C. Luciani&#039;s proposed <a href="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf" class="urlextern" title="http://www.luciani.org/geda/pcb/footprint-name-spec.pdf"  rel="nofollow">Land Pattern Naming Convention</a> – Footprint naming conventions document, used by him, and often used by those submitting to the <a href="http://www.gedasymbols.org" class="urlextern" title="http://www.gedasymbols.org"  rel="nofollow">gedasymbols.org</a> symbols/footprint repository.</div>
 213 </li>
 214 <li class="level1"><div class="li"> John C. Luciani&#039;s <a href="file:///shared/HomePages/dhart/index.html" class="urlextern" title="file:///shared/HomePages/dhart/index.html"  rel="nofollow">PCB Footprints Library</a> – A rather inclusive collection of non-<acronym title="GNU General Public License">GPL</acronym> licensed footprints and the scripts used to create them.</div>
 215 </li>
 216 <li class="level1"><div class="li"> <a href="http://www.opencollector.org/" class="urlextern" title="http://www.opencollector.org/"  rel="nofollow">OpenCollector</a> carries listings and news for free EDA software and circuit designs. Open Collector supports gEDA.</div>
 217 </li>
 218 <li class="level1"><div class="li"> <a href="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf" class="urlextern" title="http://alternatezone.com/electronics/files/PCBDesignTutorialRevA.pdf"  rel="nofollow">PCB Design Tutorial; RevA</a> – Document describing the process of taking a schematic to a pcb. Excellent for the beginner.</div>
 219 </li>
 220 <li class="level1"><div class="li"> <a href="http://pcblibraries.com/" class="urlextern" title="http://pcblibraries.com/"  rel="nofollow">PCB Libraries website</a> – Advocates of the IPC standard Land Pattern (a.k.a., footprint) Naming Conventions and Land Pattern Calculators. A useful site if you have the money to subscribe to the services.</div>
 221 <ul>
 222 <li class="level2"><div class="li"> The free (windows-based) <a href="http://landpatterns.ipc.org/default.asp" class="urlextern" title="http://landpatterns.ipc.org/default.asp"  rel="nofollow">IPC-7351 Land Pattern Viewer</a> is a very useful tool for viewing the latest IPC footprints.</div>
 223 </li>
 224 <li class="level2"><div class="li"> <a href="http://www.pcblibraries.com/resources/LibDoc.asp" class="urlextern" title="http://www.pcblibraries.com/resources/LibDoc.asp"  rel="nofollow">CAD Data Files to be used with PCB Libraries&#039; IPC-7351A LP Programs</a> – please note the license restrictions.</div>
 225 </li>
 226 </ul>
 227 </li>
 228 <li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf" class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"  rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a> – The Cambridge University Engineering Department&#039;s tutorial for using gEDA.</div>
 229 </li>
 230 <li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/" class="urlextern" title="http://www.brorson.com/gEDA/"  rel="nofollow">Stuart Brorson&#039;s gEDA tools and tips</a> – gEDA related tools and information.</div>
 231 </li>
 232 </ul>
 233
 234 </div>
 235 <!-- EDIT865 SECTION "Resources" [5419-9647] -->
 236 <h1 class="sectionedit866"><a name="how_to_ask_questions" id="how_to_ask_questions">How To Ask Questions</a></h1>
 237 <div class="level1">
 238
 239 <p>
 240 <strong>gschem</strong> is an OpenSource, community driven, development. As such, the emphasis has been on developing the gEDA Tools Suite, not on developing commercial-level documentation and support. Much of the burden on learning how to use the gEDA Tools Suite applications is placed on the user, who must understand the basics of electronics, Electronics Design Automation (EDA), and the terminology used in schematic capture, circuit simulation, and printed circuit board design.<br/>
 241
 242 As a typical OpenSource development, the gEDA Tools Suite development community provides timely and insightful response to user inquiries, but please perform the following steps before bothering the developers (they need to focus on making gEDA Tools Suite applications better, and you can actually learn to answer your own questions and become independent of the developers):
 243 </p>
 244 <ol>
 245 <li class="level1"><div class="li"> Read Rick Moen&#039;s <a href="http://www.catb.org/~esr/faqs/smart-questions.html" class="urlextern" title="http://www.catb.org/~esr/faqs/smart-questions.html"  rel="nofollow">How To Ask Questions The Smart Way</a>, about how to ask for help. This is a must read for everybody.</div>
 246 </li>
 247 <li class="level1"><div class="li"> Read this document. I know, it&#039;s a lot to expect engineers to actually read a user&#039;s guide. The latest version of this document is maintained on the gEDA web-site at <span class="hilited">TBD</span>. The information should be here. If it isn&#039;t, comment to the fact in one of the on-line document&#039;s “Discussion” areas (at the bottom of each wiki-page). Helpful comments are clear, to the point, and may even contain the wording that should be inserted into the document.</div>
 248 </li>
 249 <li class="level1"><div class="li"> Read the <a href="http://geda.seul.org/dokuwiki/doku.php?id=geda:faq-gschem" class="urlextern" title="http://geda.seul.org/dokuwiki/doku.php?id=geda:faq-gschem"  rel="nofollow">gschem Frequently Asked Questions (FAQ)</a> wiki-page. This on-line document is updated often to reflect user and developer experiences with <strong>gschem</strong>.</div>
 250 </li>
 251 <li class="level1"><div class="li"> Read the <a href="http://www.geda.seul.org/docs/current/index.html" class="urlextern" title="http://www.geda.seul.org/docs/current/index.html"  rel="nofollow">gEDA/gaf Documentation</a>. This information was installed on your computer if the gEDA Tools Suite was installed from the gEDA Tools Suite CD-ROM.</div>
 252 </li>
 253 <li class="level1"><div class="li"> <a href="http://www.google.com" class="urlextern" title="http://www.google.com"  rel="nofollow">Google</a> is your friend. People that have asked questions that obviously didn’t do any simple Google search will not be treated well when asking for help. This is particularly true if your problem is not unique to the gEDA Tools Suite applications.</div>
 254 </li>
 255 <li class="level1"><div class="li"> Ask for a pointer to the right direction. It is considered good “net etiquette” to ask for a pointer to information, so that you can learn where such information can be found, rather than have someone search the information for you.</div>
 256 </li>
 257 <li class="level1"><div class="li"> If you are software literate, look at the source code to see what it is doing.</div>
 258 </li>
 259 <li class="level1"><div class="li"> Subscribe to the gEDA e-mail lists (i.e., you can only post to the e-mail lists if you are a subscriber). Then:</div>
 260 <ol>
 261 <li class="level2"><div class="li"> Start reading recent messages in the <a href="http://archives.seul.org/geda/user/" class="urlextern" title="http://archives.seul.org/geda/user/"  rel="nofollow">geda-user e-mail list archives</a>. Get a feel for the list&#039;s ettiquite so that you learn how to properly ask questions.</div>
 262 </li>
 263 <li class="level2"><div class="li"> Search the archives for issues similar to yours. You may find the question has been asked of the developers and users before, and answered.</div>
 264 </li>
 265 <li class="level2"><div class="li"> In the event that you can find no information concerning your problem, submit a concise description of the problem and a request for the type of help you are requesting.</div>
 266 </li>
 267 </ol>
 268 </li>
 269 </ol>
 270
 271 </div>
 272 <!-- EDIT866 SECTION "How To Ask Questions" [9648-12829] -->
 273 <h1 class="sectionedit867"><a name="installing_gschem" id="installing_gschem">Installing gschem</a></h1>
 274 <div class="level1">
 275
 276 <p>
 277 As a mature OpenSource project, the gEDA Tools Suite and its components have been installed on many Linux distributions. The following are by no means the only methods of installing the gEDA Tools Suite and/or its components.
 278 </p>
 279
 280 </div>
 281 <!-- EDIT867 SECTION "Installing gschem" [12830-13088] -->
 282 <h2 class="sectionedit868"><a name="latest_stable" id="latest_stable">Latest Stable</a></h2>
 283 <div class="level2">
 284
 285 <p>
 286 <strong>gschem</strong> is a component of the gEDA/gaf set of tools which tend to integrate together in the development and maintenance of schematics and symbols. The term “gaf” stands for “<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riends”).
 287 The gEDA/gaf applications are actually rather stable, and receive significant testing prior to release.<br/>
 288
 289 There are multiple methods of installing <strong>gschem</strong>. The appropriate method depends on your distribution. See the following for some examples.
 290 </p>
 291
 292 </div>
 293 <!-- EDIT868 SECTION "Latest Stable" [13089-13573] -->
 294 <h3 class="sectionedit869"><a name="geda_tools_suite_cd-rom" id="geda_tools_suite_cd-rom">&quot;gEDA Tools Suite&quot; CD-ROM</a></h3>
 295 <div class="level3">
 296
 297 <p>
 298 The recommended method is installation from the “gEDA Tools Suite” CD-ROM, gratefully prepared by Stuart Brorson. The latest version of this CD-ROM is available on-line for free download as an <acronym title="International Organization for Standardization">ISO</acronym> image from the <a href="http://www.geda.seul.org/download.html" class="urlextern" title="http://www.geda.seul.org/download.html"  rel="nofollow">gEDA Downloads</a> web-page. Simply burn this <acronym title="International Organization for Standardization">ISO</acronym> image to a CD-ROM using your favorite CD burning software (e.g., K3b, …). Insert the CD-ROM, and if your computer supports autodetection of the CD-ROM, the built-in installation wizzard will launch. This wizzard will first check if your computer has some required software (informing you if you don&#039;t and optionally installing these if you want), then build all of the “gEDA Tool Suite” applications (including <strong>gschem</strong>) from source. The whole process can take 2 hours on a slower computer.
 299 </p>
 300
 301 <p>
 302 If the installation wizzard did not launch, enter as follows to install the gEDA Tool Suite for access by all users on this computer (i.e., when prompted for the installation directory, enter something like: “/usr/local/gEDA-20060124”):
 303 <pre STYLE="background : LightGreen;
 304 margin-left : 2em"><font size="+0"><strong>sudo sh /media/cdrecorder/installer –log –verbose</strong></font></pre>
 305 </p>
 306
 307 <p>
 308 The above command requires superuser permissions configured for the user invoking the command. If you do not have the proper permissions to execute this command, ask your administrator to install the gEDA Tool Suite for you.
 309 </p>
 310
 311 <p>
 312 If the installation wizzard did not launch, enter as follows to install the gEDA Tool Suite for access by just the user doing the installation(i.e., when prompted for the installation directory, accept the default ”/home/{login id}/geda-install”):
 313 <pre STYLE="background : LightGreen;
 314 margin-left : 2em"><font size="+0"><strong>sh /media/cdrecorder/installer –log –verbose</strong></font></pre>
 315 </p>
 316
 317 </div>
 318 <!-- EDIT869 SECTION "gEDA Tools Suite CD-ROM" [13574-15260] -->
 319 <h3 class="sectionedit870"><a name="debian_distributions" id="debian_distributions">Debian distributions</a></h3>
 320 <div class="level3">
 321
 322 <p>
 323 For Debian distributions, you may wish to download the <a href="http://www.geda.seul.org/download.html" class="urlextern" title="http://www.geda.seul.org/download.html"  rel="nofollow">latest DEB binaries</a> prepared by Hamish Moffatt. These are not always current with the latest “gEDA Tools Suite” <acronym title="International Organization for Standardization">ISO</acronym> image above, and do not include many of the other tools available on the “gEDA Tools Suite” <acronym title="International Organization for Standardization">ISO</acronym> image.
 324 </p>
 325
 326 </div>
 327 <!-- EDIT870 SECTION "Debian distributions" [15261-15609] -->
 328 <h3 class="sectionedit871"><a name="red_hat_distributions" id="red_hat_distributions">Red Hat distributions</a></h3>
 329 <div class="level3">
 330
 331 <p>
 332 For Red Hat distributions (and possibly others) you may wish to download the latest RPM binaries]] prepared by Wojciech Kazubski.
 333 </p>
 334
 335 </div>
 336 <!-- EDIT871 SECTION "Red Hat distributions" [15610-15772] -->
 337 <h3 class="sectionedit872"><a name="mac_osx_distributions" id="mac_osx_distributions">Mac OSX distributions</a></h3>
 338 <div class="level3">
 339
 340 <p>
 341 For Mac OSX distributions you may wish to download the <a href="http://www.geda.seul.org/download.html" class="urlextern" title="http://www.geda.seul.org/download.html"  rel="nofollow">latest Fink binaries</a> prepared by Charles Lepple.
 342 </p>
 343
 344 </div>
 345 <!-- EDIT872 SECTION "Mac OSX distributions" [15773-15952] -->
 346 <h2 class="sectionedit873"><a name="cvs_unstable_testing" id="cvs_unstable_testing">CVS Unstable/Testing</a></h2>
 347 <div class="level2">
 348
 349 <p>
 350 For those already familiar with the gEDA/gaf applications on the “gEDA Tools Suite” CD-ROM, access to the <acronym title="Concurrent Versions System">CVS</acronym> repository is available. This is the latest developer source-code version of the application.<br/>
 351
 352 Installation from <acronym title="Concurrent Versions System">CVS</acronym> is appropriate for those:
 353 </p>
 354 <ul>
 355 <li class="level1"><div class="li"> Seeking a solution to a specific problem that was submitted to the development team, to test the “fix” so that the developers can be informed that the “fix” works.</div>
 356 </li>
 357 <li class="level1"><div class="li"> With significant working knowledge of the “gEDA Tools Suite” and industry expertise, wishing to test the latest version of the application(s) prior to the next release. This usually requires access to several existing designs known to work in the current stable release of the “gEDA Tools Suite” <acronym title="International Organization for Standardization">ISO</acronym> image, so that comparisons can be made and issues brought to the attention of the developer/user community (via the e-mail lists).</div>
 358 </li>
 359 </ul>
 360
 361 </div>
 362 <!-- EDIT873 SECTION "CVS Unstable/Testing" [15953-16843] -->
 363 <h1 class="sectionedit874"><a name="configuring_gschem" id="configuring_gschem">Configuring gschem</a></h1>
 364 <div class="level1">
 365
 366 <p>
 367 Assume that you have installed the gEDA Tools Suite from CD-ROM (the most common installation method), and that you are ready to configure <strong>gschem</strong> to your personal likes. When installing, you were prompted for the path where the gEDA executables would be placed. The default was the <strong>/home/{login id}/geda-install</strong> directory, where {login id} is the username you logged into your account with, but you may have changed this to another directory on the computer. This directory is referred to below as the <strong>{binary-install-path}</strong> because this is where the gEDA binary executables are placed. If you forgot where the binaries were installed, simply issue the following command to find where <strong>gschem</strong> is installed (in this case the {binary-install-path} is <strong>/usr/local/gEDA-20060124</strong>):
 368 <pre STYLE="background : LightGreen;
 369 margin-left : 2em"><font size="+0">% which gschem
 370 /usr/local/gEDA-20060124/bin/gschem
 371 %</font></pre>
 372 </p>
 373
 374 <p>
 375 The gEDA Tools Suite applications follow normal Unix/Linux conventions for placement of configuration files; there are usually system-wide, user-wide, and project-specific configuration settings. The system-wide settings are placed in a sub-directory of the {binary-install-path}. The user-wide settings are placed in the user&#039;s home directory, also known as the login directory (referred to in Unix/Linux parlance as the <strong>$HOME</strong> directory). The project-specific settings are placed in a project-specific directory.<br/>
 376
 377 </p>
 378
 379 <p>
 380 Now that we know the above, we can configure <strong>gschem</strong>.<br/>
 381
 382 <strong>gschem</strong> is highly configurable. All configuration is handled through the following resource files (written using the GNU Guile programming language, an interpreter for Scheme, a version of Lisp):
 383 </p>
 384 <ul>
 385 <li class="level1"><div class="li"> <strong>system-gschemrc</strong>: The system-wide initialization file for <strong>gschem</strong>. Installed in the {binary-install-path}/share/gEDA/system-gschemrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/gschemrc file and/or &#039;pwd&#039;/gschemrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf  executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="docs-20060124-gschem_ug-installing_gschem.html" class="wikilink2" title="docs-20060124-gschem_ug-installing_gschem.html">Installing gschem</a> for more details.</div>
 386 </li>
 387 <li class="level1"><div class="li"> <strong>$HOME/gschemrc</strong>: The per-user initialization file for <strong>gschem</strong>. Created by the user in the user&#039;s home directory. Settings placed in this file will override settings in the system-gschemrc file. Users should put settings in this file they want to apply to all of their sessions, such as (to change the default black background color scheme to a light background color scheme):</div>
 388 </li>
 389 </ul>
 390
 391 <p>
 392 <pre STYLE="background : LightGreen;
 393 margin-left : 2em"><font size="+0">; Load up a color scheme
 394 (load (string-append gedadatarc &quot;/gschem-lightbg&quot;)) ; light background</font></pre>
 395 </p>
 396 <ul>
 397 <li class="level1"><div class="li"> <strong>&#039;pwd&#039;/gschemrc</strong>: The per-project initialization file for <strong>gschem</strong>. Created by the user in the user&#039;s project directory. Settings placed in this file will override settings in both the system-gschemrc file and the $HOME/gschemrc file. Users should put settings in this file they want to apply to this particular project, such as (to autonumber reference designators when components are placed on the schematic):</div>
 398 </li>
 399 </ul>
 400
 401 <p>
 402 <pre STYLE="background : LightGreen;
 403 margin-left : 2em"><font size="+0">; Comment in this scheme code if you want automatic numbering when
 404 ; placing new component and copying components
 405 ;
 406 (load (string-append gedadata &quot;/scheme/auto-uref.scm&quot;))
 407 (add-hook! add-component-hook auto-uref)</font></pre>
 408 </p>
 409 <ul>
 410 <li class="level1"><div class="li"> <strong>system-gafrc</strong>: The system-wide initialization file for gEDA/gaf applications (includes <strong>gschem</strong>, <strong>gnetlist</strong>). Installed in the {binary-install-path}/share/gEDA/system-gafrc file, it is required for <strong>gschem</strong> to run. Users should not modify this file, but should override the settings in this file by creating their own $HOME/gafrc file and/or &#039;pwd&#039;/gafrc file and putting the new settings in those files. The {binary-install-path} directory is where your gEDA/gaf  executables were installed, including <strong>gschem</strong>. Depends on your install method. Refer to <a href="docs-20060124-gschem_ug-installing_gschem.html" class="wikilink2" title="docs-20060124-gschem_ug-installing_gschem.html">Installing gschem</a> for more details.</div>
 411 </li>
 412 <li class="level1"><div class="li"> <strong>$HOME/gafrc</strong>: The per-user initialization file for gEDA/gaf applications. Created by the user in the user&#039;s home directory. Settings placed in this file will override settings in the system-gafrc file. Users should put settings in this file they want to apply to all of their sessions. </div>
 413 </li>
 414 <li class="level1"><div class="li"> <strong>&#039;pwd&#039;/gafrc</strong>: The per-project initialization file for the gEDA/gaf applications. Created by the user in the user&#039;s project directory. Settings placed in this file will override settings in both the system-gafrc file and the $HOME/gafrc file. Users should put settings in this file they want to apply to this particular project. Settings such as the <strong>component-library</strong> or <strong>source-library</strong> keywords go into this file.</div>
 415 </li>
 416 <li class="level1"><div class="li"> <strong>gschem-gtkrc</strong>: Installed in the {binary-install-path}/share/gEDA/gschem-gtkrc file. Used to define the font for all gtk+ widgets in <strong>gschem</strong>.</div>
 417 </li>
 418 </ul>
 419
 420 <p>
 421
 422 A few comments about changing the files:
 423 </p>
 424 <ul>
 425 <li class="level1"><div class="li"> Don&#039;t break any guile syntax rules. Doing so will cause the scheme interpreter (guile) to stop interpreting.</div>
 426 </li>
 427 <li class="level1"><div class="li"> To add a setting to the $HOME/gschemrc file (or to the &#039;pwd&#039;/gschemrc file), copy the setting&#039;s text from the {binary-install-directory}/share/gEDA/system-gschemrc file to the $HOME/gschemrc file (or the &#039;pwd&#039;/gschemrc file) and make the setting change there.</div>
 428 </li>
 429 <li class="level1"><div class="li"> To add a setting to the $HOME/gafrc file (or the &#039;pwd&#039;/gafrc file), copy the relevant setting&#039;s text from the {binary-install-directory}/share/gEDA/system-gafrc file to the $HOME/gafrc file (or the &#039;pwd&#039;/gafrc file) and make the setting change there.</div>
 430 </li>
 431 <li class="level1"><div class="li"> Keywords/defaults always override what came before, with the exception of cumulative keywords (like component-library).</div>
 432 </li>
 433 </ul>
 434
 435 </div>
 436 <!-- EDIT874 SECTION "Configuring gschem" [16844-22564] -->
 437 <h2 class="sectionedit875"><a name="gschemrc" id="gschemrc">gschemrc</a></h2>
 438 <div class="level2">
 439
 440 <p>
 441 The {binary-install-path}/share/gEDA/system-gschemrc file is well commented. Read this file for more details on the settings available.<br/>
 442
 443 Some of the settings appropriate for override (by placing in either the user&#039;s $HOME/gschemrc file or the project&#039;s &#039;pwd&#039;/gschemrc file) are:
 444 </p>
 445
 446 </div>
 447 <!-- EDIT875 SECTION "gschemrc" [22565-22866] -->
 448 <h2 class="sectionedit876"><a name="gafrc" id="gafrc">gafrc</a></h2>
 449 <div class="level2">
 450
 451 <p>
 452 The {binary-install-path}/share/gEDA/system-gafrc file is well commented. Read this file for more details on the settings available.<br/>
 453
 454 Some of the settings appropriate for override (by placing in either the user&#039;s $HOME/gafrc file or the project&#039;s &#039;pwd&#039;/gafrc file) are:
 455 </p>
 456
 457 </div>
 458 <!-- EDIT876 SECTION "gafrc" [22867-23156] -->
 459 <h1 class="sectionedit877"><a name="lancer_gschem" id="lancer_gschem">Lancer gschem</a></h1>
 460 <div class="level1">
 461
 462 </div>
 463 <!-- EDIT877 SECTION "Lancer gschem" [23157-23185] -->
 464 <h2 class="sectionedit878"><a name="confirming_gschem_is_installed" id="confirming_gschem_is_installed">Confirming gschem is installed</a></h2>
 465 <div class="level2">
 466
 467 <p>
 468 You should determine if <strong>gschem</strong> has been correctly installed on your Linux computer.<br/>
 469
 470 Log into your Linux account, and launch your favorite interactive shell. The different Linux distributions will usually offer more than one interactive shell such as xterm, gnome-term, konsole, etc.<br/>
 471
 472 You will see a shell prompt, which will depend on your Linux distribution and on your selection of interactive shell. It is common practice in Linux documentation to refer to the user&#039;s interactive login shell prompt as “<strong>%</strong>”, and to refer to the superuser&#039;s (i.e., user “root”) interactive login shell prompt as “<strong>#</strong>”.<br/>
 473
 474 At the shell prompt, enter the following commands to determine if <strong>gschem</strong> is installed:
 475 </p>
 476
 477 <p>
 478 <pre STYLE="background : LightGreen;
 479 margin-left : 2em"><font size="+0">% <strong>echo $PATH</strong>
 480 <strong>/usr/local/gEDA-20060124/bin</strong>:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin:/home/<strong>gEDA</strong>/bin
 481 % <strong>which gschem</strong>
 482 /usr/local/gEDA-20060124/bin/gschem
 483 % <strong>ldd /usr/local/gEDA-20060124/bin/gschem</strong>
 484     linux-gate.so.1 =&gt;  (0x00345000)
 485     libgeda.so.25 =&gt; /usr/local/gEDA-20060124/lib/libgeda.so.25 (0x00d7d000)
 486     libguile.so.12 =&gt; /usr/lib/libguile.so.12 (0x00588000)
 487     libguile-ltdl.so.1 =&gt; /usr/lib/libguile-ltdl.so.1 (0x00b62000)
 488     libqthreads.so.12 =&gt; /usr/lib/libqthreads.so.12 (0x009f7000)
 489     libpthread.so.0 =&gt; /lib/libpthread.so.0 (0x006d4000)
 490     libcrypt.so.1 =&gt; /lib/libcrypt.so.1 (0x03266000)
 491     libgdk-x11-2.0.so.0 =&gt; /usr/lib/libgdk-x11-2.0.so.0 (0x00c10000)
 492     libgdk_pixbuf-2.0.so.0 =&gt; /usr/lib/libgdk_pixbuf-2.0.so.0 (0x006ac000)
 493     libm.so.6 =&gt; /lib/libm.so.6 (0x008df000)
 494     libpangoxft-1.0.so.0 =&gt; /usr/lib/libpangoxft-1.0.so.0 (0x003e7000)
 495     libpangox-1.0.so.0 =&gt; /usr/lib/libpangox-1.0.so.0 (0x00a57000)
 496     libpango-1.0.so.0 =&gt; /usr/lib/libpango-1.0.so.0 (0x00bd8000)
 497     libgobject-2.0.so.0 =&gt; /usr/lib/libgobject-2.0.so.0 (0x00a01000)
 498     libgmodule-2.0.so.0 =&gt; /usr/lib/libgmodule-2.0.so.0 (0x009fb000)
 499     libdl.so.2 =&gt; /lib/libdl.so.2 (0x00906000)
 500     libglib-2.0.so.0 =&gt; /usr/lib/libglib-2.0.so.0 (0x0448e000)
 501     libgtk-x11-2.0.so.0 =&gt; /usr/lib/libgtk-x11-2.0.so.0 (0x06a81000)
 502     libatk-1.0.so.0 =&gt; /usr/lib/libatk-1.0.so.0 (0x00c96000)
 503     libSM.so.6 =&gt; /usr/X11R6/lib/libSM.so.6 (0x00d4f000)
 504     libICE.so.6 =&gt; /usr/X11R6/lib/libICE.so.6 (0x00d33000)
 505     libX11.so.6 =&gt; /usr/X11R6/lib/libX11.so.6 (0x00921000)
 506     libc.so.6 =&gt; /lib/libc.so.6 (0x007b4000)
 507     /lib/ld-linux.so.2 (0x00796000)
 508     libXrandr.so.2 =&gt; /usr/X11R6/lib/libXrandr.so.2 (0x00bac000)
 509     libXi.so.6 =&gt; /usr/X11R6/lib/libXi.so.6 (0x00cca000)
 510     libXinerama.so.1 =&gt; /usr/X11R6/lib/libXinerama.so.1 (0x00bb2000)
 511     libXft.so.2 =&gt; /usr/X11R6/lib/libXft.so.2 (0x00ad1000)
 512     libfreetype.so.6 =&gt; /usr/lib/libfreetype.so.6 (0x00af8000)
 513     libfontconfig.so.1 =&gt; /usr/lib/libfontconfig.so.1 (0x00111000)
 514     libXfixes.so.3 =&gt; /usr/X11R6/lib/libXfixes.so.3 (0x00d0d000)
 515     libXcursor.so.1 =&gt; /usr/X11R6/lib/libXcursor.so.1 (0x00bcc000)
 516     libXrender.so.1 =&gt; /usr/X11R6/lib/libXrender.so.1 (0x00ba2000)
 517     libXext.so.6 =&gt; /usr/X11R6/lib/libXext.so.6 (0x00a82000)
 518     libpangoft2-1.0.so.0 =&gt; /usr/lib/libpangoft2-1.0.so.0 (0x05362000)
 519     libexpat.so.0 =&gt; /usr/lib/libexpat.so.0 (0x0068b000)
 520     libz.so.1 =&gt; /usr/lib/libz.so.1 (0x0090c000)</font></pre>
 521 </p>
 522
 523 <p>
 524 The <strong>echo $PATH</strong> command displays the user&#039;s current setting for the <strong>PATH</strong> environment variable. In the above example for a Fedora Core 4 installation, user <strong>gEDA</strong> executed the command and determined that the <strong>PATH</strong> included the /usr/local/gEDA-20060124/bin directory (this will differ depending on where you put the gEDA Tools Suite executables). If you installed from the gEDA Tools Suite CD-ROM (the most common method of installing the gEDA tools), as the last step of the installation wizzard you were prompted to:
 525 </p>
 526 <ol>
 527 <li class="level1"><div class="li"> Set your $PATH environment variable to {the directory in which the install wizzard installed gEDA&#039;s executables}</div>
 528 </li>
 529 <li class="level1"><div class="li"> Set your $LD_LIBRARY_PATH environment variable to {the directory in which the install wizzard installed gEDA&#039;s libraries}</div>
 530 </li>
 531 </ol>
 532
 533 <p>
 534
 535 The <strong>which</strong> command displays the full path of a command&#039;s executable, searching for the command on the user&#039;s list of directories, as defined in the <strong>PATH</strong> environment variable. In this case, it will return the full path to the <strong>gschem</strong> executable if it is on the user&#039;s <strong>PATH</strong>. If this command does not return the full path to the <strong>gschem</strong> executable, make sure your <strong>PATH</strong> environment variable has been properly set.
 536 </p>
 537
 538 <p>
 539 The <strong>ldd</strong> command displays shared libraries required by a program. All of the requested libraries must be found for <strong>gschem</strong> to run. Don&#039;t be intimidated by the long list of libraries, this is common for mature Linux applications. If we had not received this output (or something very similar), we would have to check on our setting for the <strong>LD_LIBRARY_PATH</strong> environment variable.
 540 </p>
 541
 542 <p>
 543 And of course, there is always attempting to just run <strong>gschem</strong> as follows:
 544 <pre STYLE="background : LightGreen;
 545 margin-left : 2em"><font size="+0">%  <strong>gschem -h</strong>
 546 Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
 547   -q            Quiet mode
 548   -v            Verbose mode on
 549   -r filename   Rc filename
 550   -s filename   Script (guile) filename
 551   -o filename   Output filename (for printing)
 552   -p            Automatically place the window
 553   -t            Print stroke information
 554   -h            Help; this message</font></pre>
 555 </p>
 556
 557 <p>
 558 where we displayed the <strong>gschem</strong> help.
 559 </p>
 560
 561 <p>
 562 If these commands do not return the expected results, then most likely the gEDA tools are not installed properly. Please see the appropriate INSTALL docs (which came with the gEDA distribution) for more info on installing the gEDA tools. If you installed from the gEDA Tools Suite CD-ROM, read the INSTALL document on the CD-ROM first.<br/>
 563
 564 </p>
 565
 566 </div>
 567 <!-- EDIT878 SECTION "Confirming gschem is installed" [23186-28891] -->
 568 <h2 class="sectionedit879"><a name="the_shell_prompt" id="the_shell_prompt">The Shell Prompt</a></h2>
 569 <div class="level2">
 570 <div class="table sectionedit880"><table class="inline">
 571         <tr class="row0">
 572                 <td class="col0"> <a href="media/geda/terminal_screenshot_001.jpg" class="media" target="_blank" title="geda:terminal_screenshot_001.jpg"><img src="media/geda/terminal_screenshot_001.jpg" class="media" alt="" /></a> </td>
 573         </tr>
 574         <tr class="row1">
 575                 <td class="col0"> Figure 1 – gnome-terminal </td>
 576         </tr>
 577 </table></div>
 578 <!-- EDIT880 TABLE [28921-28993] -->
 579 <p>
 580
 581 You launch <strong>gschem</strong> from your favorite shell prompt (in this case, gnome-terminal on Fedora Core 4).<br/>
 582
 583 There are several command-line switches:
 584 </p>
 585 <ul>
 586 <li class="level1"><div class="li"> <strong>-q</strong> – Quiet mode<br/>
 587 Turns on “quiet mode”. Output (i.e., stdout and stderr) is not generated to the shell. Useful if calling <strong>gschem</strong> from a script (e.g., bash, sh, csh, etc.) to perform batch operations such as printing a large number of schematics or symbols.</div>
 588 </li>
 589 <li class="level1"><div class="li"> <strong>-v</strong> – Verbose mode ON<br/>
 590 Generate verbose information. Not used very much in <strong>gschem</strong>.</div>
 591 </li>
 592 <li class="level1"><div class="li"> <strong>-r filename</strong> – Process additional configuration settings from <strong>filename</strong><br/>
 593 <strong>filename</strong> is a file containing settings of the form found in either system-gschemrc or system-gafrc<br/>
 594 In addition to the following files, <strong>gschem</strong> will process <strong>filename</strong> for additional configuration settings:<br/>
 595   * {binary-install-path}/share/gEDA/system-gschemrc<br/>
 596   * $HOME/gschemrc<br/>
 597   * &#039;pwd&#039;/gschemrc<br/>
 598   * {binary-install-path}/share/gEDA/system-gafrc<br/>
 599  * $HOME/gafrc<br/>
 600   * &#039;pwd&#039;/gafrc</div>
 601 </li>
 602 <li class="level1"><div class="li"> <strong>-s filename</strong> – Process <strong>filename</strong> as a guile script<br/>
 603 The name of a script file (written in guile) for <strong>gschem</strong> to process.<br/>
 604 Refer to <a href="docs-20060124-gschem_ug-app_b.html" class="wikilink2" title="docs-20060124-gschem_ug-app_b.html">Appendix B -- Printing Schematics and Symbols</a> and <a href="docs-20060124-gschem_ug-app_c.html" class="wikilink2" title="docs-20060124-gschem_ug-app_c.html">Appendix C -- Writing guile Scripts</a> for more details.<br/>
 605 For example, in your $HOME/geda-sources/gedagaf/{gEDA Tools Suite version}/scripts/ directory is the <strong>print.scm</strong> file, a template script file directing <strong>gschem</strong> to generate a PostScript file of a schematic appropriate for printing. This <strong>print.scm</strong> file works as is, but you may want to customize it for your own needs. To print the schematic_1.sch schematic to the schematic_1.ps PostScript file from within a bash script, you would enter: <code>gschem  -q -p -o schematic_1.ps -s print.scm schematic_1.sch</code><br/>
 606 Then, simply use your favorite printing solution to print the file, such as: <code>lp schematic_1.ps</code><br/>
 607 to a PostScript printer.</div>
 608 </li>
 609 <li class="level1"><div class="li"> <strong>-o filename</strong> – Output <strong>filename</strong> (e.g., for printing)<br/>
 610 Specify the output filename. For example, as used to specify the Postscript filename in the example above.</div>
 611 </li>
 612 <li class="level1"><div class="li"> <strong>-p</strong> – Automatically place the window<br/>
 613 Don&#039;t wait for the windowmanager to place the window.<br/>
 614 When a new window is opened, some window managers display the bounding box of the window and wait for the user to place the window manually. The ”-p” option avoids that, letting the window manager decide where to put the new window.</div>
 615 </li>
 616 <li class="level1"><div class="li"> <strong>-t</strong> – Print stroke information<br/>
 617 </div>
 618 </li>
 619 <li class="level1"><div class="li"> <strong>-h</strong> – Help<br/>
 620 Generate a short usage printout.</div>
 621 </li>
 622 </ul>
 623
 624 <p>
 625
 626 Running <strong>gschem</strong> is straightforward once you have installed it on your GNU/Linux system.<br/>
 627
 628 Although <strong>gschem</strong> is a <acronym title="Graphical User Interface">GUI</acronym> application, <strong>gschem</strong> is meant to be launched from the command-line, as it takes command-line arguements (see Figure 1 above).<br/>
 629
 630 To open an empty schematic, run: <code><strong>% gschem</strong></code><br/>
 631
 632 </p>
 633
 634 <p>
 635 To open a specific schematic, run: <code><strong>% gschem schematic_name.sch</strong></code><br/>
 636
 637 </p>
 638
 639 <p>
 640 To open a list of schematics, run: <code><strong>% gschem schematic_1.sch schematic_2.sch, schematic_3.sch …</strong></code><br/>
 641 or use wildcards to specify multiple filenames: <code><strong>% gschem schematic_*.sch</strong></code>
 642 </p>
 643
 644 <p>
 645 As operations are performed in the <strong>gschem</strong> <a href="docs-20060124-gschem_ug-the_main_window.html" class="wikilink2" title="docs-20060124-gschem_ug-the_main_window.html">Main Window</a> the <strong>gschem</strong> <a href="docs-20060124-gschem_ug-the_status_window.html" class="wikilink2" title="docs-20060124-gschem_ug-the_status_window.html">Status Window</a> continues to output information, and the shell prompt&#039;s window continues to output information, consisting of:
 646 </p>
 647 <ul>
 648 <li class="level1"><div class="li"> …</div>
 649 </li>
 650 </ul>
 651
 652 </div>
 653 <!-- EDIT879 SECTION "The Shell Prompt" [28892-32426] -->
 654 <h2 class="sectionedit881"><a name="backups" id="backups">Backups</a></h2>
 655 <div class="level2">
 656
 657 <p>
 658 There are two basic mechanisms in <strong>gschem</strong> for backing up schematics and symbols, classic Linux backups and incremental backups.
 659 </p>
 660
 661 </div>
 662 <!-- EDIT881 SECTION "Backups" [32427-32578] -->
 663 <h3 class="sectionedit882"><a name="classic_linux_backups" id="classic_linux_backups">Classic Linux backups</a></h3>
 664 <div class="level3">
 665
 666 <p>
 667 While creating and/or editing schematic file(s) or symbol file(s), snapshots are triggered by the <strong>autosave</strong> interval setting in the {binary-install-path}/share/gEDA/system-gschemrc file (see <a href="#relevant_configuration_settings" title=":geda:gschem_ug.fr.txt &crarr;" class="wikilink1">Relevant configuration settings</a> below). If the file has not been manually saved, and the interval expires (current default 2 minutes), the snapshot is saved the next time a change is made in the <strong>gschem</strong> main window (to either a schematic or to a symbol). The interval timer starts again as soon as the snapshot file(s) have been written, and once the timer expires the next change to the main window will trigger the snapshot to be written.<br/>
 668
 669 This snapshot includes all work up to, but not including, the last operation performed in the <strong>gschem</strong> main window. This is to allow for easier recovery from a crash that may have been caused by the last operation.<br/>
 670
 671 When <strong>gschem</strong> exits normally, the snapshot file(s) are deleted. So, if <strong>gschem</strong> were to crash, or not terminate normally for some reason (e.g., power failure, soda → keyboard, etc.), the shapshot file(s) would be found the next time <strong>gschem</strong> opened the file(s). <strong>gschem</strong> will display the following warning message when it finds a snapshot file associated with the schematic file(s) or symbol file(s) it opens:
 672 <pre STYLE="background : LightGreen;
 673 margin-left : 2em"><font size="+0">WARNING: Found and autosave backup file:
 674   {full path to autosave file}
 675
 676 The backup copy is newer than the schematic, so it seems you
 677 should load it instead of the original fil.
 678 Gschem usually makes backup copies automatically, and this
 679 situation happens when it crashed or it was forced to exit
 680 abruptely.
 681
 682 If you load the original file, the backup file will be overwritten in
 683 the next autosave timeout and it will be lost.
 684
 685 Do you want to load the backup file?</font></pre>
 686 </p>
 687
 688 <p>
 689 The snapshots are saved to a file whose filename is constructed from the original filename (schematic or symbol) as follows:
 690 </p>
 691 <ul>
 692 <li class="level1"><div class="li"> add a ”#” to the beginning of the original filename</div>
 693 </li>
 694 <li class="level1"><div class="li"> add a ”#” to the end</div>
 695 </li>
 696 </ul>
 697
 698 <p>
 699
 700 so that:
 701 </p>
 702 <ul>
 703 <li class="level1"><div class="li"> “schematic_1.sch” becomes ”#schematic_1.sch#”</div>
 704 </li>
 705 <li class="level1"><div class="li"> “symbol.sym” becomes ”#symbol.sym#”</div>
 706 </li>
 707 </ul>
 708
 709 <p>
 710
 711 And yes, the ”#” at the front and back of the filename are part of the filename.<br/>
 712
 713 </p>
 714
 715 <p>
 716 When the user does finally manually save the file, the original file (i.e., the file that was opened) is renamed to ”{filename~}” and the latest snapshot file (i.e., ”#{filename}#”) gets copied as ”{filename}”. Note that this new ”{filename}” file may not contain the latest information as displayed on the <strong>gschem</strong> main window, as the <strong>autosave</strong> interval timer may not have expired since the last change to the schematic/symbol.<br/>
 717
 718 When the user finally decides to close <strong>gschem</strong>, the latest snapshot file (i.e., ”#{filename}#”) is saved to the original file (i.e., ”{filename}”.<br/>
 719
 720 When you exit <strong>gschem</strong> and are prompted to save any unsaved schematic file(s) or symbol file(s), this constitutes a manual save.
 721 </p>
 722
 723 </div>
 724 <!-- EDIT882 SECTION "Classic Linux backups" [32579-35485] -->
 725 <h3 class="sectionedit883"><a name="incremental_backups" id="incremental_backups">Incremental backups</a></h3>
 726 <div class="level3">
 727
 728 </div>
 729 <!-- EDIT883 SECTION "Incremental backups" [35486-35519] -->
 730 <h3 class="sectionedit884"><a name="relevant_configuration_settings" id="relevant_configuration_settings">Relevant configuration settings</a></h3>
 731 <div class="level3">
 732
 733 <p>
 734 There are the following configuration settings in the {binary-install-path}/share/gEDA/system-gschemrc file that effect backups:
 735 </p>
 736 <ul>
 737 <li class="level1"><div class="li"> <strong>undo-control</strong> : Controls if the undo feature is enabled or not.</div>
 738 </li>
 739 <li class="level1"><div class="li"> <strong>undo-levels</strong> : Determines the number of levels of undo. Basically this number decides how many backup schematics are saved.</div>
 740 </li>
 741 <li class="level1"><div class="li"> <strong>undo-type</strong> : Controls which kind of undo is used, disk or memory. The default is to use the disk as the storage medium (i.e., after every action the undo information is stored to a new file on disk). The disk mechanism is nice because you get that many backups of the schematic, written to disk as backups, so you should never lose a schematic due to a crash.</div>
 742 </li>
 743 <li class="level1"><div class="li"> <strong>autosave</strong> : Controls if a backup copy is made every “interval” seconds. Note that a backup copy is only made when you make some change to the schematic, and there were more than “interval” seconds from the last autosave. Autosaving will not be allowed if the “interval” setting is set to zero.</div>
 744 </li>
 745 </ul>
 746
 747 </div>
 748 <!-- EDIT884 SECTION "Relevant configuration settings" [35520-36561] -->
 749 <h2 class="sectionedit885"><a name="on-line_documentation" id="on-line_documentation">On-line documentation</a></h2>
 750 <div class="level2">
 751
 752 <p>
 753 For a listing of the various command line flags run “<strong>gschem -h</strong>”:
 754 <pre STYLE="background : LightGreen;
 755 margin-left : 2em"><font size="+0">% <strong>gschem -h</strong>
 756 Usage: gschem [OPTIONS] schematic_filename1 ... schematic_filenameN
 757   -q            Quiet mode
 758   -v            Verbose mode on
 759   -r filename   Rc filename
 760   -s filename   Script (guile) filename
 761   -o filename   Output filename (for printing)
 762   -p            Automatically place the window
 763   -t            Print stroke information
 764   -h            Help; this message</font></pre>
 765 </p>
 766
 767 <p>
 768 For a detailed explanation of the command line flags look at the <strong>gschem</strong> man page:
 769 <pre STYLE="background : LightGreen;
 770 margin-left : 2em"><font size="+0">% <strong>man gschem</strong>
 771 gschem(1)                          20031231                          gschem(1)
 772
 773
 774
 775 NAME
 776        gschem - gEDA/gaf Schematic Capture
 777
 778 SYNOPSIS
 779        gschem  [-q]  [-v] [-t] [-r rcfilename] [-s scriptfilename] [-o output-
 780        filename] [-p] [schematic1 ... schematicN]
 781
 782 DESCRIPTION
 783        gschem is the schematic capture program which is part gEDA  (GPL  Elec-
 784        tronic  Design Automation) toolset.  This program is used to draw elec-
 785        tronic schematics.  Schematics consist of standard symbols  (which  are
 786        either  part of a standard library or created by the user) which repre-
 787        sent the various gates  and  components.   These  components  are  then
 788        interconnected  by  nets  (wires).   Schematics  may  be  printed  to a
 789        PostScript file for printing or further conversion to other output for-
 790        mats.
 791
 792        gschem is also the symbol creation editor.  All the standard methods of
 793        creating schematics are used in the creation of symbols.  There  are  a
 794        few  special  rules when creating symbols, so please refer to the (non-
 795        existant as of now) symbol creation document.
 796
 797        Please read the official documentation (very minimal at this point)  on
 798        how  to use gschem, since this man page just describes the command line
 799        arguments and a few examples on how to run gschem.
 800
 801
 802 OPTIONS
 803        gschem accepts the following options:
 804
 805        -q      Quiet mode on.  This mode  turns  off  all  warnings/notes/mes-
 806                sages. (optional)
 807
 808        -v      Verbose  mode on.  This mode gives as much feedback to the user
 809                as possible. (optional)
 810
 811        -t      Print out more information when using mouse strokes.  With this
 812                command  line  flag  and the middle button configured for mouse
 813                strokes, gschem will output the stroke sequence numbers as  the
 814                user executes strokes.  These numbers can be used to define new
 815                strokes in the system-gschemrc file.
 816
 817        -r filename
 818                Specify a rc filename.  Normally gschem searches for  the  sys-
 819                tem-gschemrc, then ~/.gEDA/gschemrc, and finally for a gschemrc
 820                in the current directory.  This  options  allows  the  user  to
 821                specify an additional rc file which is read after all the other
 822                rc files are read. (optional)
 823
 824        -s filename
 825                Specify a guile script to be executed at startup. (optional)
 826
 827        -o filename
 828                Specify a filename for postscript output.   This  command  line
 829                argument  is useful when running gschem from a shell script and
 830                with a guile script.  The filename can be changed  through  the
 831                print dialog box.
 832
 833        -p      Automatically  place  the  window, especially useful if running
 834                gschem from the command line and generating output.
 835
 836        schematic1 [... schematicN]
 837                Schematic file to be loaded.  Specifing  a  schematic  file  is
 838                optional.   If  multiple schematic files are specified they are
 839                read in sequentially and put on seperate pages.  It  is  impor-
 840                tant that the schematic(s) follow all the options (ie last).
 841
 842
 843 EXAMPLES
 844        These  examples  assume that you have a schematic called stack_1.sch in
 845        the current directory
 846
 847        To run gschem and then interact with the program:
 848
 849             ./gschem
 850
 851        To run gschem in interactive mode but load a sample schematic:
 852
 853             ./gschem adders_1.sch
 854
 855        To run gschem and load up all schematics in the current subdirectory:
 856
 857             ./gschem *.sch
 858
 859
 860 ENVIRONMENT
 861        No environment variables are used.
 862
 863
 864 AUTHOR
 865        Ales Hvezda and many others
 866
 867
 868 SEE ALSO
 869        gnetlist(1), gsymcheck(1)
 870
 871 COPYRIGHT
 872        Copyright ©  1999-2004 Ales Hvezda
 873
 874        This document can be freely redistributed according to the terms of the
 875        GNU General Public License version 2.0
 876
 877
 878
 879
 880 Version                       December 31st, 2003                    gschem(1)</font></pre>
 881 </p>
 882
 883 </div>
 884 <!-- EDIT885 SECTION "On-line documentation" [36562-41031] -->
 885 <h1 class="sectionedit886"><a name="electrical_connectivity" id="electrical_connectivity">Electrical Connectivity</a></h1>
 886 <div class="level1">
 887
 888 <p>
 889 As you draw schematics you need be aware of what is considered to be electrically connected by the gEDA programs.<br/>
 890
 891 Nets which are visually connected to other nets are electrically connected. This connection may be endpoint to endpoint or endpoint to midpoint. When a single endpoint to endpoint (net or pin endpoint) connection is drawn, the visual dangling net cue disappears. When an endpoint ends in the middle of another net (or multiple endpoints coming together at a single point) then a circular filled connectivity cue is drawn. You cannot connect a net to the middle of a pin. Nets can only be connected to the endpoints of pins. You cannot connect to a net if that net is not orthogonal (horizontal or vertical). The visual cues are the primary way of telling if nets/pins are connected.<br/>
 892
 893 Bus are similar to nets with the exception that you cannot connect a net to the endpoint of a bus (only to the middle). If you do try to connect a net to the end of a bus you will see a big red X at the invalid endpoint connection. Buses are still very new so there are still many quirks.<br/>
 894
 895 You can label nets by using the <code>label=</code> attribute. Do not attach more than one <code>label=</code> to a net. You only need to attach the <code>label=</code> attribute to one net segment. Different nets (i.e. multiple net segments which aren’t connected together) which have the same attribute <code>label=</code> attached to them are also considered electrically connected. You will not get any indication of this connection by <strong>gschem</strong>, but the netlister (<strong>gnetlist</strong>) considers nets with the same <code>label=</code> attribute electrically connected. The naming convention for buses has not been formalized yet.
 896 </p>
 897
 898 </div>
 899 <!-- EDIT886 SECTION "Electrical Connectivity" [41032-42748] -->
 900 <h1 class="sectionedit887"><a name="components_symbols_objects_attributes" id="components_symbols_objects_attributes">Components &amp; Symbols &amp; Objects &amp; Attributes</a></h1>
 901 <div class="level1">
 902
 903 <p>
 904 There is a hierarchical association between components, symbols, objects, and attributes.
 905 </p>
 906
 907 </div>
 908 <!-- EDIT887 SECTION "Components & Symbols & Objects & Attributes" [42749-42897] -->
 909 <h2 class="sectionedit888"><a name="components" id="components">Components</a></h2>
 910 <div class="level2">
 911
 912 <p>
 913 A component is the instantiation of a specific symbol, as placed on the schematic. When discussing a schematic you refer to <em class="u">components</em> on the schematic, not <em class="u">symbols</em> on the schematic. Think of symbols as being <em class="u">conceptual</em>, and components as being <em class="u">concrete</em>.<br/>
 914
 915 The component consists of a graphic representation and the attributes describing the component&#039;s features.<br/>
 916
 917 The component inherits all of the attributes defined in the symbol. Certain attributes in the symbol:
 918 </p>
 919 <ul>
 920 <li class="level1"><div class="li"> those explicitly defined as visible unattached attributes (see <a href="#attributes" title=":geda:gschem_ug.fr.txt &crarr;" class="wikilink1">Attributes</a>)</div>
 921 </li>
 922 <li class="level1"><div class="li"> specific attributes such as <code>symversion</code> and <code>refdes</code></div>
 923 </li>
 924 </ul>
 925
 926 <p>
 927
 928 are promoted to the component level for manipulation by the circuit designer. These attributes may optionally be exposed (made viewable) with the component&#039;s graphic, and their values may be changed.<br/>
 929
 930 Any attribute not defined in the symbol may be defined in the component. For example, if the symbol does not define the <code>comment</code> attribute, this attribute may be added to the component, perhaps to add a comment for the Bill of Material or Assembly Instructions.<br/>
 931
 932 Unfortunately, it is difficult to determine a component&#039;s attributes from <strong>gschem</strong> while entering the schematic. You have to place a symbol on the schematic, select the resulting component, and select <strong>Hierarchy | Down Symbol</strong> from the pull-down menus. Then, you have to unhide all attributes with <strong>Edit | Make Inv Text Vis</strong> from the pull-down menus. Then you have to expand your view of the symbol with <strong>View | Extents</strong>. Then, you have to go back to the schematic by selecting <strong>Hierarchy | Up</strong> from the pull-down menus. Then, you have to select <strong>Edit | Edit…</strong> to bring up the “Edit Attributes” dialog box to determine if any attributes have been added at the component level.
 933 </p>
 934
 935 </div>
 936 <!-- EDIT888 SECTION "Components" [42898-44712] -->
 937 <h2 class="sectionedit889"><a name="symbols" id="symbols">Symbols</a></h2>
 938 <div class="level2">
 939
 940 <p>
 941 Symbols are just a collection of objects and attributes.<br/>
 942
 943 The objects have positional significance in the symbol, and define the graphic that is viewed.<br/>
 944
 945 Attributes may be attached to objects, or they may be attached to the symbol itself (termed as “unattached” attributes, because they are not attached to an object).
 946 </p>
 947
 948 </div>
 949 <!-- EDIT889 SECTION "Symbols" [44713-45054] -->
 950 <h2 class="sectionedit890"><a name="objects" id="objects">Objects</a></h2>
 951 <div class="level2">
 952
 953 <p>
 954 The following are objects:
 955 </p>
 956 <ul>
 957 <li class="level1"><div class="li"> Line</div>
 958 </li>
 959 <li class="level1"><div class="li"> Box</div>
 960 </li>
 961 <li class="level1"><div class="li"> Circle</div>
 962 </li>
 963 <li class="level1"><div class="li"> Arc</div>
 964 </li>
 965 <li class="level1"><div class="li"> Pin</div>
 966 </li>
 967 <li class="level1"><div class="li"> Picture</div>
 968 </li>
 969 <li class="level1"><div class="li"> Text</div>
 970 </li>
 971 </ul>
 972
 973 </div>
 974 <!-- EDIT890 SECTION "Objects" [45055-45167] -->
 975 <h2 class="sectionedit891"><a name="attributes" id="attributes">Attributes</a></h2>
 976 <div class="level2">
 977
 978 <p>
 979 An attribute is text which is in the form <code>name=value</code> (there are no spaces to the left or right of the name,value pair). An attribute can be either attached to an object or unattached. Attributes are used extensively in the gEDA project to convey information (e.g., device name, pin numbers, hidden nets, and unit reference numbers). Check <a href="http://www.geda.seul.org/docs/current/attributes/index.html" class="urlextern" title="http://www.geda.seul.org/docs/current/attributes/index.html"  rel="nofollow">gEDA/gaf Master Attribute Document</a> for a complete list of attributes.<br/>
 980
 981 There are three kinds of attributes:</p>
 982 <dl>
 983 <dt><span class='term'> Attached attributes</span></dt>
 984 <dd>These are attributes which take on the standard form and are attached to some object (pin, net, component, or box etc…) to associate a value with the attribute. For example: a pin number associated with a pin. <span class="hilited">These attributes are usually yellow in color.</span></dd>
 985 <dt><span class='term'> Unattached attributes</span></dt>
 986 <dd>These are attributes which take on the standard form, but are not attached to any object and usually convey some information which is global in nature. For example: a <code>device=</code> attribute (which lives inside symbols) and specifies what device the entire symbol represents. These attributes are also known as floating or toplevel attributes.</dd>
 987 <dt><span class='term'> Promoted attributes</span></dt>
 988 <dd>These are unattached attributes in the symbol&#039;s definition that get turned into attached attributes in the component&#039;s definition when the symbol is instantiated as a component when placed in the schematic. If you place an unattached visible attribute inside a symbol and then instantiate that symbol, then that unattached attribute gets “promoted”; that is, it becomes an attached attribute. This mechanism of attribute reattachement (from within a symbol) is known as attribute promotion.</dd>
 989 </dl>
 990 <p>There are some gotchas about attribute promotion:
 991 </p>
 992 <ul>
 993 <li class="level1"><div class="li"> Promotion <strong>only</strong> happens when the symbol is first placed. That means that if you place a symbol (e.g., sym1) and then change it on disk (by adding or removing new unattached attributes), existing sym1&#039;s will not reflect these new unattached attributes (i.e., they won&#039;t get promoted) in any schematic.</div>
 994 </li>
 995 <li class="level1"><div class="li"> The <code>device=</code> attribute is not promoted.</div>
 996 </li>
 997 <li class="level1"><div class="li"> Invisible attributes are not promoted by default. If you add an unattached attribute (e.g., numslots=#) and make it invisible, it will not be promoted.</div>
 998 </li>
 999 </ul>
1000
1001 <p>
1002
1003 Now, in order to make everybody happy, this attribute promotion behavior is configurable.<br/>
1004
1005 The system-gschemrc file defines:
1006 <pre STYLE="background : LightGreen;
1007 margin-left : 2em"><font size="+0">(attribute-promotion &quot;enabled&quot;)</font></pre>
1008 </p>
1009
1010 <p>
1011 which enables attribute promotion.<br/>
1012
1013 If you override the system-gschemrc&#039;s default promote-invisible setting by adding:
1014 <pre STYLE="background : LightGreen;
1015 margin-left : 2em"><font size="+0">(promote-invisible &quot;enabled&quot;)</font></pre>
1016 </p>
1017
1018 <p>
1019 to either your user&#039;s ~/gschemrc or local &#039;pwd&#039;/gschemrc file, invisible unattached attributes will also be promoted <span class="hilited">(and in memory removed)</span>.
1020 </p>
1021
1022 <p>
1023 However, if you do this, component slotting will break because <strong>gschem</strong> expects certain unattached attributes inside the symbol <span class="hilited">(in memory even though they are invisible)</span>.<br/>
1024
1025 So you can add:
1026 <pre STYLE="background : LightGreen;
1027 margin-left : 2em"><font size="+0">(keep-invisible &quot;enabled&quot;)</font></pre>
1028 </p>
1029
1030 <p>
1031 to either your user&#039;s ~/gschemrc or local &#039;pwd&#039;/gschemrc file. This is enabled by default, but has no effect unless promote-invisible is enabled.
1032 </p>
1033
1034 <p>
1035 So, to summarize, attribute promotion takes unattached attributes inside symbols and attaches them to the outside of a placed symbol. Three *rc keywords control this behavior: attribute-promotion, promote-invisible, and keep-invisible.
1036 </p>
1037
1038 </div>
1039 <!-- EDIT891 SECTION "Attributes" [45168-48554] -->
1040 <h1 class="sectionedit892"><a name="the_main_window" id="the_main_window">The Main Window</a></h1>
1041 <div class="level1">
1042 <div class="table sectionedit893"><table class="inline">
1043         <tr class="row0">
1044                 <td class="col0"> <a href="media/geda/gschem_screenshot_001.jpg" class="media" target="_blank" title="geda:gschem_screenshot_001.jpg"><img src="media/geda/gschem_screenshot_001.jpg" class="media" alt="" /></a> </td>
1045         </tr>
1046 </table></div>
1047 <!-- EDIT893 TABLE [48585-48624] -->
1048 <p>
1049
1050 There are several ways to interact with <strong>gschem</strong>. <strong>gschem</strong> requires a keyboard and mouse. There are three ways to initiate an operation or command:
1051 </p>
1052 <ul>
1053 <li class="level1"><div class="li"> Using the mouse to select the operation off a menu</div>
1054 </li>
1055 <li class="level1"><div class="li"> Typing the keyboard shortcut(s).</div>
1056 </li>
1057 <li class="level1"><div class="li"> Draw the appropriate stroke (if stroke support is enabled)</div>
1058 </li>
1059 </ul>
1060
1061 <p>
1062
1063 To make usage matters more confusing, selecting an operation off of the menus behaves slightly differently than typing the keyboard shortcut. Most of the operations operate on the currently selected object(s), hence you need to select the object first before manipulating them. The menu selected operations usually require some more input (usually a mouse click) after they are picked off of the menu. The keyboard shortcut operations take that required input as the current mouse position. This saves an extra click since you can position the mouse at the right place, type in the shortcut(s), and the command then executes. Note, you can change this so that both menu and shortcut behavior is exactly the same. See the section on the resource file for more info on how to configure this.<br/>
1064
1065 Most of the interaction with <strong>gschem</strong> is fairly mode oriented (similar to the great text editor vi). If you select operations off of the menu, then you are placed into the corresponding mode (like copy or move mode). You must then select an anchor point (or whatever the appropriate point is) to continue the operation. Most of the commands off of the menu expect the objects to be already selected. Some of the modes persist after being execute while other immediately return you into select mode (the default mode).<br/>
1066
1067 The shortcuts are also mode like in nature. Most of the default shortcuts are for the various commands are not single keystrokes. There are a few which are single keystrokes (like zoom in: `z&#039; or pan: `x&#039;), but most are typically two keystrokes long. As examples, to execute File/Save you would type `f&#039; and `s&#039; (without the quotes) or Add/Line is `a&#039; and `l&#039;. You can get a listing of the shortcuts by picking Help/Hotkeys. You can also see the hotkey assignments in the pulldown menus as well. The shortcuts are defined in the resource files (<strong>system-gschemrc</strong>, <strong>/.gEDA/gschemrc</strong>, or <strong>`pwd`/gschemrc</strong>). See the section on the resource file for more info.<br/>
1068
1069 The mouse button actions in <strong>gschem</strong> are mostly configurable. The first mouse button is always used to select objects or pick points. This button is not configurable. The second mouse button is either a copy/move action (when held down over an object), a repeat last command or used to draw a stroke to execute a command. The third mouse button is either a mouse pan (when held down as the mouse is moved) or a popup menu. The behavior of the second and third mouse buttons is controlled through the resource file (see the section below for more info).
1070 </p>
1071
1072 </div>
1073 <!-- EDIT892 SECTION "The Main Window" [48555-51468] -->
1074 <h1 class="sectionedit894"><a name="the_status_window" id="the_status_window">The Status Window</a></h1>
1075 <div class="level1">
1076 <div class="table sectionedit895"><table class="inline">
1077         <tr class="row0">
1078                 <td class="col0"> <a href="media/geda/status_screenshot.jpg" class="media" target="_blank" title="geda:status_screenshot.jpg"><img src="media/geda/status_screenshot.jpg" class="media" title=":geda:status_screenshot.jpg" alt=":geda:status_screenshot.jpg" /></a> </td>
1079         </tr>
1080 </table></div>
1081 <!-- EDIT895 TABLE [51501-51564] -->
1082 <p>
1083
1084 Add some details about what gets displayed in the status window.
1085 </p>
1086
1087 </div>
1088 <!-- EDIT894 SECTION "The Status Window" [51469-51631] -->
1089 <h1 class="sectionedit896"><a name="the_schematic_file" id="the_schematic_file">The Schematic File</a></h1>
1090 <div class="level1">
1091
1092 <p>
1093 Schematic files. These files contain components, nets, text, and sometimes primitive objects (like lines, circles, box etc…) Schematics do not contain pins. Schematic filenames should follow this convention: name_#.sch where:
1094 </p>
1095 <ul>
1096 <li class="level1"><div class="li"> name is a text string which describes what this schematic contains.</div>
1097 </li>
1098 <li class="level1"><div class="li"> _# is an underscore and a number (like _1, _2, _7, _13, etc…) This number is used to sequence schematic pages in a multiple page schematic.</div>
1099 </li>
1100 <li class="level1"><div class="li"> .sch is the schematic extension/suffix. It is important the schematic pages have this extension.</div>
1101 </li>
1102 </ul>
1103
1104 <p>
1105
1106 Schematic files are pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym> and will always be pure <acronym title="American Standard Code for Information Interchange">ASCII</acronym>. gEDA does not support any binary file formats. The file format for schematics is described in the gEDA file formats document.
1107 </p>
1108
1109 </div>
1110 <!-- EDIT896 SECTION "The Schematic File" [51632-52401] -->
1111 <h1 class="sectionedit897"><a name="the_symbol_file" id="the_symbol_file">The Symbol File</a></h1>
1112 <div class="level1">
1113
1114 <p>
1115 Symbol files. The schematic and symbol file formats are identical. <strong>gschem</strong> (or a text editor) is used to create symbol files as well as schematics. Symbol files contain lines, circles, boxes, arcs, pins, text, and attributes.<br/>
1116
1117 The naming convention for symbol files is: name-#.sym where:
1118 </p>
1119 <ul>
1120 <li class="level1"><div class="li"> name is a text string which describes what the symbol represents.</div>
1121 </li>
1122 <li class="level1"><div class="li"> -# is a dash and a number (like -1, -2 etc…) The number is used to allow for a symbols to have the same name yet different contents. There might be multiple representations for resistors so these symbols should be called: resistor-1.sym, resistor-2.sym, and resistor-3.sym.</div>
1123 </li>
1124 <li class="level1"><div class="li"> .sym is the symbol extension/suffix. It is important the symbols have this extension.</div>
1125 </li>
1126 </ul>
1127
1128 <p>
1129
1130 The way of specifying hierarchy is by using the source= attribute. Please see the master attribute document for info on this mechanism.<br/>
1131
1132 The hierarchy mechanism is still in heavy flux, so there might be some more changes.
1133 </p>
1134
1135 </div>
1136 <!-- EDIT897 SECTION "The Symbol File" [52402-53388] -->
1137 <h1 class="sectionedit898"><a name="symbol_libraries" id="symbol_libraries">Symbol Libraries</a></h1>
1138 <div class="level1">
1139
1140 <p>
1141 Components are searched for by specifying (component-library ”…”) inside one of the *rc files. See below for more info.
1142 </p>
1143
1144 </div>
1145 <!-- EDIT898 SECTION "Symbol Libraries" [53389-53542] -->
1146 <h1 class="sectionedit899"><a name="the_log_file" id="the_log_file">The Log File</a></h1>
1147 <div class="level1">
1148
1149 <p>
1150 Log file. This file contains informative, error, warnings etc… messages when <strong>gschem</strong> was run. This file is created in the working directory that <strong>gschem</strong> was started in. This allows the user to preserve log files between independent projects.
1151 </p>
1152
1153 </div>
1154 <!-- EDIT899 SECTION "The Log File" [53543-53820] -->
1155 <h1 class="sectionedit900"><a name="grips" id="grips">Grips</a></h1>
1156 <div class="level1">
1157
1158 <p>
1159 Grips are a mechanism used in <strong>gschem</strong> to provide an easy way of modifying objects inside schematics. When you select an object, little squares are placed in strategic locations (line end points or circle radius point or corners of a box) which allow you to change the object quickly. Grip support currently exists for lines, nets, pins, buses, circles, and boxes. Arcs do not yet have grips, but will eventually have them.
1160 </p>
1161
1162 <p>
1163 Using grips is easy:
1164 </p>
1165 <ul>
1166 <li class="level1"><div class="li"> Select the object you want to change. The grips (the little boxes) will appear.</div>
1167 </li>
1168 <li class="level1"><div class="li"> Click and hold the first mouse button inside the box.</div>
1169 </li>
1170 <li class="level1"><div class="li"> Move the mouse around till you have the object where you want it</div>
1171 </li>
1172 <li class="level1"><div class="li"> Release the mouse button.</div>
1173 </li>
1174 </ul>
1175
1176 </div>
1177 <!-- EDIT900 SECTION "Grips" [53821-54530] -->
1178 <h1 class="sectionedit901"><a name="menu_operations" id="menu_operations">Menu Operations</a></h1>
1179 <div class="level1">
1180
1181 </div>
1182 <!-- EDIT901 SECTION "Menu Operations" [54531-54560] -->
1183 <h2 class="sectionedit902"><a name="file" id="file">File</a></h2>
1184 <div class="level2">
1185
1186 <p>
1187 The <strong>gschem</strong> application is primarily used for the creation of schematic files (i.e., filename.sch) and symbol files (filename.sym).<br/>
1188
1189 The following operations are related to the manipulation of these files.<br/>
1190
1191 Note that <strong>gschem</strong> automatically maintains backups of open schematic/symbol files, in the /tmp directory, for the purpose of Undo/Redo. <strong>gschem</strong> cleans up these files when it exits gracefully. If <strong>gschem</strong> does not exit gracefully, the next time you launch <strong>gschem</strong> you will be prompted with a dialog similar to:
1192 <pre STYLE="background : LightGreen;
1193 margin-left : 2em"><font size="+0">WARNING: Found an autosave backup file:
1194         {filename}
1195
1196       The backup copy is newer than the schematic, so it seems you
1197       load it instead of the original file.
1198       gschem usually makes backup copies automatically, and this
1199       situation happens when it crashed or it was forced to exit
1200       abruptly.
1201
1202       If you load the original file, the backup file will be overwritten in
1203       the next autosave timeout and it will be lost.
1204
1205       Do you want to load the backup file?</font></pre>
1206 </p>
1207
1208 <p>
1209 The following are available from the <strong>gschem</strong> main window&#039;s menu-bar when you expand <strong>File</strong>:
1210 </p>
1211
1212 </div>
1213 <!-- EDIT902 SECTION "File" [54561-55714] -->
1214 <h3 class="sectionedit903"><a name="new_window_fw" id="new_window_fw">New Window (fw)</a></h3>
1215 <div class="level3">
1216
1217 <p>
1218 <strong>File | New Window</strong> Ouvre une nouvelle fenêtre. Chaque fenêtre est totalement séparée des autres fenêtres.
1219 </p>
1220
1221 </div>
1222 <!-- EDIT903 SECTION "New Window (fw)" [55715-55855] -->
1223 <h3 class="sectionedit904"><a name="new_page_fn" id="new_page_fn">New Page (fn)</a></h3>
1224 <div class="level3">
1225
1226 <p>
1227 <strong>File | New Page</strong> Ouvre une nouvelle page en plus de toute page ouverte existante. Cette page sera habituellement appelée «·untitled_N.sch·» où N est un nombre incrémenté.
1228 </p>
1229
1230 </div>
1231 <!-- EDIT904 SECTION "New Page (fn)" [55856-56062] -->
1232 <h3 class="sectionedit905"><a name="open_page_fo" id="open_page_fo">Open Page... (fo)</a></h3>
1233 <div class="level3">
1234
1235 <p>
1236 <strong>File | Open Page…</strong> Ouvre une page depuis le disque.<br/>
1237
1238 The “Open…” dialog box pops up providing:
1239 </p>
1240 <ul>
1241 <li class="level1"><div class="li"> Directory navigation aids</div>
1242 </li>
1243 <li class="level1"><div class="li"> Filters for restricting the displayed files:</div>
1244 <ul>
1245 <li class="level2"><div class="li"> Schematics</div>
1246 </li>
1247 <li class="level2"><div class="li"> Symbols</div>
1248 </li>
1249 <li class="level2"><div class="li"> Schematics and Symbols</div>
1250 </li>
1251 <li class="level2"><div class="li"> All files</div>
1252 </li>
1253 </ul>
1254 </li>
1255 </ul>
1256
1257 </div>
1258 <!-- EDIT905 SECTION "Open Page... (fo)" [56063-56349] -->
1259 <h3 class="sectionedit906"><a name="close_page_pc" id="close_page_pc">Close Page (pc)</a></h3>
1260 <div class="level3">
1261
1262 <p>
1263 <strong>File | Close Page</strong> Fermer la page actuellement affichée. Il vous sera demandé de faire une sauvegarde si vous avez fait des modifications sur la page.
1264 </p>
1265
1266 </div>
1267 <!-- EDIT906 SECTION "Close Page (pc)" [56350-56532] -->
1268 <h3 class="sectionedit907"><a name="revert_page_pr" id="revert_page_pr">Revert Page (pr)</a></h3>
1269 <div class="level3">
1270
1271 <p>
1272 <strong>File | Revert Page</strong> Ferme et réouvre la page actuellement affichée. Il ne vous sera pas demandé de sauvegarder la page courante et effacera toutes les changements que vous avez fait en réouvrant le schéma sauvegardé dans le disque. A utiliser avec précaution.
1273 </p>
1274
1275 </div>
1276 <!-- EDIT907 SECTION "Revert Page (pr)" [56533-56830] -->
1277 <h3 class="sectionedit908"><a name="save_page_fs" id="save_page_fs">Save Page (fs)</a></h3>
1278 <div class="level3">
1279
1280 <p>
1281 <strong>File | Save Page</strong> Sauve la page courante. The current filename is displayed in the <strong>gschem</strong> status-bar.<br/>
1282
1283 Si la page est appelée untitled_N.sch (o N est un entier) alors une boîte de dialogue avec Save As… apparaîtra demandant un nouveau nom de fichier.<br/>
1284
1285 If the page&#039;s filename is NOT “untitled_N.sch” (where N is a integer), then the Save As… dialog box will NOT be displayed, and:
1286 </p>
1287 <ul>
1288 <li class="level1"><div class="li"> the backup file will be created for the previous version, named {filename}~ That is, the ”~” (tilde character) is appended to the filename. Any previous backup file is lost.</div>
1289 </li>
1290 <li class="level1"><div class="li"> the file will be saved to the current filename.<br/>
1291 </div>
1292 </li>
1293 </ul>
1294
1295 </div>
1296 <!-- EDIT908 SECTION "Save Page (fs)" [56831-57484] -->
1297 <h3 class="sectionedit909"><a name="save_page_as_fa" id="save_page_as_fa">Save Page As... (fa)</a></h3>
1298 <div class="level3">
1299
1300 <p>
1301 <strong>File | Save Page As…</strong> Ouvre la boîte de dialogue Save As.<br/>
1302
1303 If the current filename is “untitled_N.sch”, the Save As… dialog box prompts for a new filename.<br/>
1304
1305 If the current filename is NOT “untitled_N.sch”, the Save As… dialog box prompts for a new filename, filling in the current filename as a default.<br/>
1306
1307 In either case the filename may be changed, and a new file created when the Save As button is clicked.
1308 </p>
1309
1310 </div>
1311 <!-- EDIT909 SECTION "Save Page As... (fa)" [57485-57937] -->
1312 <h3 class="sectionedit910"><a name="save_all_fl_fl" id="save_all_fl_fl">Save All (fl) (fl)</a></h3>
1313 <div class="level3">
1314
1315 <p>
1316 <strong>File | Save All</strong> Sauvegarde inconditionnelle de tous les schémas chargés dans la mémoire.
1317 </p>
1318
1319 </div>
1320 <!-- EDIT910 SECTION "Save All (fl) (fl)" [57938-58063] -->
1321 <h3 class="sectionedit911"><a name="print_fp" id="print_fp">Print... (fp)</a></h3>
1322 <div class="level3">
1323
1324 <p>
1325 <strong>File | Print…</strong> Affiche la boîte de dialogue Print.<br/>
1326
1327 The following may be selected:
1328 </p>
1329 <ul>
1330 <li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, this filename defaults to the page currently displayed).</div>
1331 </li>
1332 <li class="level1"><div class="li"> Paper size (that is loaded into your printer).</div>
1333 </li>
1334 <li class="level1"><div class="li"> The print type:</div>
1335 <ul>
1336 <li class="level2"><div class="li"> Extents with margins – the current page, with margins where the printer doesn&#039;t output.</div>
1337 </li>
1338 <li class="level2"><div class="li"> Extents no margins – the current page, but without margins where the printer doesn&#039;t output. The printer output may be scaled larger than when using “Entents with margins”, but at the loss along the borders of the schematic.</div>
1339 </li>
1340 <li class="level2"><div class="li"> Current window – Scaled to fit the page size, but not optimally.</div>
1341 </li>
1342 </ul>
1343 </li>
1344 <li class="level1"><div class="li"> Orientation:</div>
1345 <ul>
1346 <li class="level2"><div class="li"> Landscape</div>
1347 </li>
1348 <li class="level2"><div class="li"> Portrait</div>
1349 </li>
1350 </ul>
1351 </li>
1352 </ul>
1353
1354 <p>
1355
1356 Pressing Print will generate a PostScript file with the filname format of the form {filename}.ps (e.g., printing schematic file First_1.sch would generate First_1.ps).<br/>
1357
1358 Printing the PostScript file to your printer is distribution dependent:</p>
1359 <dl>
1360 <dt><span class='term'> Fedora Core (from the command-line):</span></dt>
1361 <dd><code>lp First_1.ps</code></dd>
1362 </dl>
1363
1364
1365 </div>
1366 <!-- EDIT911 SECTION "Print... (fp)" [58064-59112] -->
1367 <h3 class="sectionedit912"><a name="write_png_fi" id="write_png_fi">Write PNG... (fi)</a></h3>
1368 <div class="level3">
1369
1370 <p>
1371 <strong>File | Write <acronym title="Portable Network Graphics">PNG</acronym>…</strong> Affiche la boîte de dialogue Write <acronym title="Portable Network Graphics">PNG</acronym>. Note you must have libgdgeda installed (and any required dependencies) if you want to output images.<br/>
1372
1373 The dialog box allows you to select:
1374 </p>
1375 <ul>
1376 <li class="level1"><div class="li"> Width x Height:</div>
1377 <ul>
1378 <li class="level2"><div class="li"> 320 x 240</div>
1379 </li>
1380 <li class="level2"><div class="li"> 640 x 480</div>
1381 </li>
1382 <li class="level2"><div class="li"> 800 x 600</div>
1383 </li>
1384 <li class="level2"><div class="li"> 1024 x 768</div>
1385 </li>
1386 <li class="level2"><div class="li"> 1280 x 960</div>
1387 </li>
1388 <li class="level2"><div class="li"> 1600 x 1200</div>
1389 </li>
1390 <li class="level2"><div class="li"> 3200 x 2400</div>
1391 </li>
1392 </ul>
1393 </li>
1394 <li class="level1"><div class="li"> Filename (if <strong>gschem</strong> has multiple pages loaded, the currently displayed page&#039;s filname is given)</div>
1395 </li>
1396 </ul>
1397
1398 <p>
1399
1400 When the OK button is clicked, a <acronym title="Portable Network Graphics">PNG</acronym> graphic file with a filename of the form {filename}.png is created (e.g., writing a <acronym title="Portable Network Graphics">PNG</acronym> for schematic file First_1.sch will generate a First_1.png file).<br/>
1401
1402 This file may be used any way a <acronym title="Portable Network Graphics">PNG</acronym> file is used (e.g., web-page, document insertion, image manipulation with the GIMP, etc.).
1403 </p>
1404
1405 </div>
1406 <!-- EDIT912 SECTION "Write PNG... (fi)" [59113-59909] -->
1407 <h3 class="sectionedit913"><a name="execute_script_ft" id="execute_script_ft">Execute Script... (ft)</a></h3>
1408 <div class="level3">
1409
1410 <p>
1411 <strong>File | Execute Script…</strong> …..TBD
1412 </p>
1413
1414 </div>
1415 <!-- EDIT913 SECTION "Execute Script... (ft)" [59910-59981] -->
1416 <h3 class="sectionedit914"><a name="close_window_fc" id="close_window_fc">Close Window (fc)</a></h3>
1417 <div class="level3">
1418
1419 <p>
1420 <strong>File | Close Window</strong> Ferme la fenêtre actuelle. S’il y a des schémas modifiés, une boîte de dialogue “There are unsaved schematics” apparaîtra. Cliquer sur OK fera perdre tous les schémas non sauvegardés.
1421 </p>
1422
1423 </div>
1424 <!-- EDIT914 SECTION "Close Window (fc)" [59982-60232] -->
1425 <h3 class="sectionedit915"><a name="quit_alt-q" id="quit_alt-q">Quit (Alt-q)</a></h3>
1426 <div class="level3">
1427
1428 <p>
1429 <strong>File | Quit</strong> closes all opened windows and exits <strong>gschem</strong>. A “There are unsaved schematics” dialog box will appear for each window that has unsaved schematics.
1430 </p>
1431
1432 </div>
1433 <!-- EDIT915 SECTION "Quit (Alt-q)" [60233-60425] -->
1434 <h2 class="sectionedit916"><a name="edit" id="edit">Edit</a></h2>
1435 <div class="level2">
1436
1437 <p>
1438 The following are available from the <strong>gschem</strong> main window’s menu-bar when you expand <strong>Edit</strong>:
1439 </p>
1440
1441 </div>
1442 <!-- EDIT916 SECTION "Edit" [60426-60542] -->
1443 <h3 class="sectionedit917"><a name="undo_shift-u" id="undo_shift-u">Undo (shift-u)</a></h3>
1444 <div class="level3">
1445
1446 <p>
1447 <strong>Edit | Undo</strong> does exactly that, it undos the last action which changed the schematic.<br/>
1448
1449 The depth of undo (how many undo steps can be performed) is set in the system-gschemrc file. The default is 10. Simply override this setting by placing the following lines in either your ~/.gEDA/gschemrc file or your local gschemrc file:
1450 <pre STYLE="background : LightGreen;
1451 margin-left : 2em"><font size="+0">; undo-levels number
1452 ;
1453 ; Determines the number of levels of undo.  Basically this number decides
1454 ; how many backup schematics are saved on disk.
1455 ;
1456 (undo-levels 10)</font></pre>
1457 </p>
1458
1459 <p>
1460 After every action (including zooming and panning) the schematic is saved to disk (in /tmp). The undo-levels setting determines how many of these temporary files are maintained in the /tmp directory. <strong>gschem</strong> does clean-up after itself when you exit.<br/>
1461
1462 Should <strong>gschem</strong> crash, the saved files remain in /tmp for disaster recovery. You will be prompted the next time the schematic is opened to recover from the backup.<br/>
1463
1464 </p>
1465
1466 </div>
1467 <!-- EDIT917 SECTION "Undo (shift-u)" [60543-61501] -->
1468 <h3 class="sectionedit918"><a name="redo_shift-r" id="redo_shift-r">Redo (shift-r)</a></h3>
1469 <div class="level3">
1470
1471 <p>
1472 <strong>Edit | Redo</strong> only applies after you have done an <strong>Edit | Undo</strong>. You can undo something and then immediately redo it. However if you do anything in between you will lose the undo info. You can undo and redo to your hearts desire up and down till you reach the max undo levels.<br/>
1473
1474 </p>
1475
1476 </div>
1477 <!-- EDIT918 SECTION "Redo (shift-r)" [61502-61810] -->
1478 <h3 class="sectionedit919"><a name="select_mode_s" id="select_mode_s">Select Mode (s)</a></h3>
1479 <div class="level3">
1480
1481 <p>
1482 <strong>Edit | Select Mode</strong> is the initial mode in which <strong>gschem</strong> starts.<br/>
1483
1484 When in <strong>Select Mode</strong>, an unlocked object (i.e., component, line, box, circle, …) may be selected by placing the mouse pointer within the outline of the object and single-clicking, or by dragging a box (i.e., holding down the first mouse-button) around the object. Selecting an already selected object will leave the object selected (i.e., you can not unselect an object by single-clicking it). Multiple unlocked objects may be selected by dragging a box around the objects.<br/>
1485
1486 A locked object may be selected by dragging a box around the object.<br/>
1487
1488 To de-select all objects, single-click anywhere on the schematic where there is no object.<br/>
1489
1490 A visible attribute for an unlocked component may be selected by placing the mouse pointer over the component&#039;s visible attribute and single-clicking. Placing the mouse pointer over the unlocked component&#039;s visible attribute and double-clicking will open the edit dialog box appropriate for the attribute.<br/>
1491
1492 Objects will change color when selected.<br/>
1493
1494 You stay in <strong>Select Mode</strong> until you select one of the other Modes (e.g., Line, Copy, Move, etc.).<br/>
1495
1496 Your current Mode is displayed on the status-bar, in the lower-right corner of the <strong>gschem</strong> window.<br/>
1497
1498 If multiple objects overlap, single-clicking where they overlap will cycle through the objects.<br/>
1499
1500 If you hold down the SHIFT key and single-click, you can select and deselect multiple objects. Doing this with multiple overlapping objects will cause the selection to cycle among the possible object selections.<br/>
1501
1502 If you hold down the CONTROL key and single-click, you will toggle the object in and out of the current selection list.<br/>
1503
1504 If you hold down the SHIFT key while drawing a selection box you will add to the currently selected objects. Objects cannot be removed using the selection box and holding down the SHIFT key.<br/>
1505
1506 If you hold down the CONTROL key while drawing a selection box then you will toggle any encompassed objects. If an object was selected then it will be unselected and vice versa.<br/>
1507
1508 If you pick a component, its visible and invisible attributes are selected as well.
1509 If you just want to select the object, you must deselect the attributes.<br/>
1510
1511 The selection mechanisms are not obvious and do require some practice. There are some quirks so please report them as you come across them.
1512 </p>
1513
1514 </div>
1515 <!-- EDIT919 SECTION "Select Mode (s)" [61811-64218] -->
1516 <h3 class="sectionedit920"><a name="edit_ee" id="edit_ee">Edit... (ee)</a></h3>
1517 <div class="level3">
1518
1519 <p>
1520 First, select the object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
1521
1522 If the object is a component, <strong>Edit | Edit…</strong> then pops up a dialog box that allows you to edit the component&#039;s attributes:
1523 </p>
1524 <ul>
1525 <li class="level1"><div class="li"> Existing attributes (e.g., refdes) are displayed.</div>
1526 </li>
1527 <li class="level1"><div class="li"> A drop-down list of pre-defined attributes permits selection, and a edit-box provides association of a value to the attribute.</div>
1528 </li>
1529 <li class="level1"><div class="li"> The attribute&#039; name and/or value may be made visible or invisible,</div>
1530 </li>
1531 </ul>
1532
1533 <p>
1534
1535 If the ojbect is a text string, <strong>Edit…</strong> then pops up a dialog box that allows you to modify the text string&#039;s attributes:
1536 </p>
1537 <ul>
1538 <li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
1539 </li>
1540 <li class="level1"><div class="li"> The text color may be modified.</div>
1541 </li>
1542 <li class="level1"><div class="li"> The text size may be modified.</div>
1543 </li>
1544 <li class="level1"><div class="li"> The text alignment:</div>
1545 <ul>
1546 <li class="level2"><div class="li"> Lower/middle/upper left</div>
1547 </li>
1548 <li class="level2"><div class="li"> Lower/middle/upper middle</div>
1549 </li>
1550 <li class="level2"><div class="li"> Lower/middle/upper right</div>
1551 </li>
1552 </ul>
1553 </li>
1554 </ul>
1555
1556 <p>
1557
1558 Apply the changes by pressing OK.
1559 </p>
1560
1561 <p>
1562 <strong>Notes:</strong><br/>
1563
1564 If you need to change the attributes to more than just a few components, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
1565 </p>
1566
1567 </div>
1568 <!-- EDIT920 SECTION "Edit... (ee)" [64219-65413] -->
1569 <h3 class="sectionedit921"><a name="edit_text_ex" id="edit_text_ex">Edit Text... (ex)</a></h3>
1570 <div class="level3">
1571
1572 <p>
1573 First, select the text object to be edited (i.e., in <strong>Select Mode</strong>).<br/>
1574
1575 <strong>Edit | Edit Text…</strong> allows you to edit just text.<br/>
1576
1577 <strong>Edit | Edit Text…</strong> then pops up a dialog box that allows you to modify the text string&#039;s attributes:
1578 </p>
1579 <ul>
1580 <li class="level1"><div class="li"> The text string may be modified. Multiple lines of text may be entered by inserting carriage-returns.</div>
1581 </li>
1582 <li class="level1"><div class="li"> The text color may be modified.</div>
1583 </li>
1584 <li class="level1"><div class="li"> The text size may be modified.</div>
1585 </li>
1586 <li class="level1"><div class="li"> The text alignment:</div>
1587 <ul>
1588 <li class="level2"><div class="li"> Lower/middle/upper left</div>
1589 </li>
1590 <li class="level2"><div class="li"> Lower/middle/upper middle</div>
1591 </li>
1592 <li class="level2"><div class="li"> Lower/middle/upper right</div>
1593 </li>
1594 </ul>
1595 </li>
1596 </ul>
1597
1598 <p>
1599
1600 Apply the changes by pressing OK.
1601 </p>
1602
1603 <p>
1604 <strong>Notes:</strong><br/>
1605
1606 If you need to change the attributes to more than just a few text strings, consider saving your schematics, closing <strong>gschem</strong>, and using the <strong>gattrib</strong> application, the <strong>grenum</strong> application, or the <strong>refdes_renum</strong> application to make the changes.
1607 </p>
1608
1609 </div>
1610 <!-- EDIT921 SECTION "Edit Text... (ex)" [65414-66272] -->
1611 <h3 class="sectionedit922"><a name="copy_mode_ec" id="copy_mode_ec">Copy Mode (ec)</a></h3>
1612 <div class="level3">
1613
1614 <p>
1615 <strong>Edit | Copy Mode</strong> allows you to copy (i.e., duplicate) the currently selected objects.<br/>
1616
1617 To copy the object(s):
1618 </p>
1619 <ul>
1620 <li class="level1"><div class="li"> Select the objects to be copied (i.e., in <strong>Select Mode</strong>)</div>
1621 </li>
1622 <li class="level1"><div class="li"> Select <strong>Edit | Copy Mode</strong></div>
1623 </li>
1624 <li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Copy Mode</strong></div>
1625 </li>
1626 <li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
1627 </li>
1628 <li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
1629 </li>
1630 <li class="level1"><div class="li"> Place the components where you want them</div>
1631 </li>
1632 <li class="level1"><div class="li"> Click to anchor the copied components in place.</div>
1633 </li>
1634 </ul>
1635
1636 <p>
1637
1638 After finishing the copy, you automatically return to <strong>Select Mode</strong>.<br/>
1639
1640 Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
1641
1642 To copy objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
1643
1644 </p>
1645
1646 </div>
1647 <!-- EDIT922 SECTION "Copy Mode (ec)" [66273-67197] -->
1648 <h3 class="sectionedit923"><a name="move_mode_em" id="move_mode_em">Move Mode (em)</a></h3>
1649 <div class="level3">
1650
1651 <p>
1652 <strong>Edit | Move Mode</strong> allows you to move the currently selected objects.<br/>
1653
1654 To move the object(s):
1655 </p>
1656 <ul>
1657 <li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>)</div>
1658 </li>
1659 <li class="level1"><div class="li"> Select <strong>Edit | Move Mode</strong></div>
1660 </li>
1661 <li class="level1"><div class="li"> Observe the status-bar now indicates <strong>Move Mode</strong></div>
1662 </li>
1663 <li class="level1"><div class="li"> Click on the selected component(s) to establish an origin of reference</div>
1664 </li>
1665 <li class="level1"><div class="li"> Observe a shadow/outline appears for the selected components that moves with the mouse</div>
1666 </li>
1667 <li class="level1"><div class="li"> Place the components where you want them</div>
1668 </li>
1669 <li class="level1"><div class="li"> Click to anchor the moved components in place.</div>
1670 </li>
1671 </ul>
1672
1673 <p>
1674
1675 After finishing the move, you automatically return to <strong>Select Mode</strong>.<br/>
1676
1677 Holding down the CONTROL key as you move the outline around will constrain the movement to be either horizontal or vertical.<br/>
1678
1679 To move objects using the shortcut keys is almost the same as above except that the origin point is selected automatically for you once you hit the copy mode shortcut.<br/>
1680
1681 </p>
1682
1683 <p>
1684 Since version 20060906, there is another way to move object(s):<br/>
1685
1686 </p>
1687 <ul>
1688 <li class="level1"><div class="li"> Select the objects to be moved (i.e., in <strong>Select Mode</strong>).<br/>
1689 </div>
1690 </li>
1691 <li class="level1"><div class="li"> Put the mouse pointer on one of the selected objects, then drag the objects and drop them where you want them.<br/>
1692 </div>
1693 </li>
1694 </ul>
1695
1696 </div>
1697 <!-- EDIT923 SECTION "Move Mode (em)" [67198-68351] -->
1698 <h3 class="sectionedit924"><a name="delete_delete-key" id="delete_delete-key">Delete (Delete-key)</a></h3>
1699 <div class="level3">
1700
1701 <p>
1702 <strong>Edit | Delete</strong> allows you to remove objects off of the page.<br/>
1703
1704 To delete objects:
1705 </p>
1706 <ul>
1707 <li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
1708 </li>
1709 <li class="level1"><div class="li"> Select <strong>Edit | Delete</strong></div>
1710 </li>
1711 </ul>
1712
1713 <p>
1714
1715 The object(s) will be deleted immediately. If you inadvertantly delete a component, you can use Undo to recover.
1716 </p>
1717
1718 </div>
1719 <!-- EDIT924 SECTION "Delete (Delete-key)" [68352-68670] -->
1720 <h3 class="sectionedit925"><a name="rotate_90_mode_er" id="rotate_90_mode_er">Rotate 90 Mode (er)</a></h3>
1721 <div class="level3">
1722
1723 <p>
1724 <strong>Edit | Rotate 90 Mode</strong> allows you to rotate objects 90 degrees around a pivot/center point.<br/>
1725
1726 To rotate objects:
1727 </p>
1728 <ul>
1729 <li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
1730 </li>
1731 <li class="level1"><div class="li"> Select <strong>Edit | Rotate 90 Mode</strong></div>
1732 </li>
1733 <li class="level1"><div class="li"> Click on the pivot (or center) point of the rotate</div>
1734 </li>
1735 </ul>
1736
1737 <p>
1738
1739 The object(s) will be rotated 90º counter-clockwise immediately. If you inadvertantly rotate a component, you can use Undo to recover.<br/>
1740
1741 Rotating objects using the shortcut keys is similar to above except that the center point is the last mouse position at which you typed the shortcut.<br/>
1742
1743 </p>
1744
1745 </div>
1746 <!-- EDIT925 SECTION "Rotate 90 Mode (er)" [68671-69260] -->
1747 <h3 class="sectionedit926"><a name="mirror_mode_ei" id="mirror_mode_ei">Mirror Mode (ei)</a></h3>
1748 <div class="level3">
1749
1750 <p>
1751 <strong>Edit | Mirror Mode</strong> allows you to mirror objects horizontally around a pivot point.<br/>
1752
1753 To mirror objects:
1754 </p>
1755 <ul>
1756 <li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
1757 </li>
1758 <li class="level1"><div class="li"> Select <strong>Edit | Mirror Mode</strong></div>
1759 </li>
1760 <li class="level1"><div class="li"> Click on the pivot (or center) point of the mirror</div>
1761 </li>
1762 </ul>
1763
1764 <p>
1765
1766 Mirroring objects using the shortcut keys is similar to above except that the pivot point is the last mouse position at which you typed the shortcut.<br/>
1767
1768 Objects are mirrored horizontally about the pivot point. If you want to get a vertical mirror then rotate and mirror the object(s) till you get the desired position.<br/>
1769
1770 Mirroring of embedded components is not supported.
1771 </p>
1772
1773 </div>
1774 <!-- EDIT926 SECTION "Mirror Mode (ei)" [69261-69917] -->
1775 <h3 class="sectionedit927"><a name="slot_e_shift-s" id="slot_e_shift-s">Slot... (e shift-s)</a></h3>
1776 <div class="level3">
1777
1778 <p>
1779 Some physical packages (e.g., the classic 7400 Quad NAND gate) contain more than one logical component (e.g., one of the NAND gates). In <strong>gchem</strong> terminology, each of these logical components is termed a “slot” (e.g., there would be 4 slots in the 7400 Quad NAND gate). Each slot is associated with specific pins on the physical package.<br/>
1780
1781 <strong>Edit | Slot…</strong> allows you to change the slot number of a multiple-slot package. The package must support slotting. Refer to the <a href="http://www.geda.seul.org/docs/current/symbols/index.html" class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"  rel="nofollow">gEDA/gaf Symbol Creation Document</a> for more details.<br/>
1782
1783 To change the slot number (i.e., select which package pins are associated with a logical component):
1784 </p>
1785 <ul>
1786 <li class="level1"><div class="li"> Select the desired logical component (i.e., in <strong>Select Mode</strong>)</div>
1787 </li>
1788 <li class="level1"><div class="li"> Select <strong>Edit | Slot…</strong></div>
1789 </li>
1790 <li class="level1"><div class="li"> Change the “slot=n” value in the “Edit slot number” dialog box</div>
1791 </li>
1792 <li class="level1"><div class="li"> Press OK</div>
1793 </li>
1794 </ul>
1795
1796 <p>
1797
1798 Note that selecting the slot on a package often effects the layout of the printed circuit board, as the slot may be on the wrong side of the package for effecient routing of nets. Don&#039;t worry, you can always come back and change the slot selection once you start laying out your board and know which slots route best.
1799 </p>
1800
1801 </div>
1802 <!-- EDIT927 SECTION "Slot... (e shift-s)" [69918-71134] -->
1803 <h3 class="sectionedit928"><a name="color_eo" id="color_eo">Color... (eo)</a></h3>
1804 <div class="level3">
1805
1806 <p>
1807 <strong>Edit | Color…</strong> allows you to change the color of any selected object (with the exception of components).<br/>
1808
1809 To change the color of the currently selected objects:
1810 </p>
1811 <ul>
1812 <li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
1813 </li>
1814 <li class="level1"><div class="li"> Select <strong>Edit | Color…</strong></div>
1815 </li>
1816 <li class="level1"><div class="li"> The “Edit | Color Edit” dialog box, with a drop down list for colors, will appear:</div>
1817 <ul>
1818 <li class="level2"><div class="li"> 1 | pin | black</div>
1819 </li>
1820 <li class="level2"><div class="li"> 2 | net endpoint | red</div>
1821 </li>
1822 <li class="level2"><div class="li"> 3 | graphic | green4</div>
1823 </li>
1824 <li class="level2"><div class="li"> 4 | net | blue2</div>
1825 </li>
1826 <li class="level2"><div class="li"> 5 | attribute | black</div>
1827 </li>
1828 <li class="level2"><div class="li"> 6 | logic bubble | DarkCyan</div>
1829 </li>
1830 <li class="level2"><div class="li"> 8 | detached attribute | red</div>
1831 </li>
1832 <li class="level2"><div class="li"> 9 | text | green4</div>
1833 </li>
1834 <li class="level2"><div class="li"> 10 | bus | green2</div>
1835 </li>
1836 <li class="level2"><div class="li"> 11 | select | firebrick</div>
1837 </li>
1838 <li class="level2"><div class="li"> 12 | bounding box | orange</div>
1839 </li>
1840 <li class="level2"><div class="li"> 13 | zoom box | DarkCyan</div>
1841 </li>
1842 <li class="level2"><div class="li"> 14 | stroke | grey90</div>
1843 </li>
1844 <li class="level2"><div class="li"> 15 | lock | grey40</div>
1845 </li>
1846 </ul>
1847 </li>
1848 <li class="level1"><div class="li"> Pick the new color</div>
1849 </li>
1850 <li class="level1"><div class="li"> Press Apply</div>
1851 </li>
1852 </ul>
1853
1854 <p>
1855
1856 The color change will take effect once you press Apply.<br/>
1857
1858 You can leave this dialog box up and select other objects and change their color by pressing Apply.
1859 </p>
1860
1861 </div>
1862 <!-- EDIT928 SECTION "Color... (eo)" [71135-72093] -->
1863 <h3 class="sectionedit929"><a name="lock_el_unlock_e_shift-l" id="lock_el_unlock_e_shift-l">Lock (el) / Unlock (e shift-l)</a></h3>
1864 <div class="level3">
1865
1866 <p>
1867 <strong>Edit | Lock</strong> and <strong>Edit | Unlock</strong> allow you to lock/unlock components in a schematic. A locked component cannot be selected by a single click. To select locked component(s), drag a box around the component(s).<br/>
1868
1869 Locking a component is useful for components such as title blocks, which should not be selectable because there are other objects inside its boundaries. If the titleblock was not locked, and you missed selecting a component by clicking it with the mouse, you would end up selecting the titleblock instead.<br/>
1870
1871 Locking a component is also useful just to prevent it from being inadvertantly selected.<br/>
1872
1873 To lock/unlock components:
1874 </p>
1875 <ul>
1876 <li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
1877 </li>
1878 <li class="level1"><div class="li"> Select <strong>Edit | Lock</strong> or <strong>Edit | Unlock</strong></div>
1879 </li>
1880 </ul>
1881
1882 <p>
1883
1884 The locked/unlocked state of components is preserved when <strong>gschem</strong> exits, so components which were locked remain locked the next time the schematic is opened.<br/>
1885
1886 You can lock and unlock regular objects (e.g., lines, pins, boxes…). This is nice when you are drawing something and an object is in the way. Just lock it, and you will not have to think about it when you click to select other objects. Locking an object is not preserved in the file format, so once you quit <strong>gschem</strong> any locked objects will be unlocked the next time the schematic is opened.<br/>
1887
1888 Note that if a component is locked, you can not single-click to select a visible attribute, or double-click to select and edit a visible component. First unlock such locked components.
1889 </p>
1890
1891 </div>
1892 <!-- EDIT929 SECTION "Lock (el) / Unlock (e shift-l)" [72094-73632] -->
1893 <h3 class="sectionedit930"><a name="line_width_type_ew" id="line_width_type_ew">Line Width &amp; Type... (ew)</a></h3>
1894 <div class="level3">
1895
1896 <p>
1897 The <strong>Edit | Line Width &amp; Type…</strong> dialog box lets you control the width and type of lines, boxes, circles, and arcs on the schematic/symbol.<br/>
1898
1899 To change the <strong>Line Width &amp; Type…</strong>:
1900 </p>
1901 <ul>
1902 <li class="level1"><div class="li"> Select the desired object(s) (i.e., in <strong>Select Mode</strong>)</div>
1903 </li>
1904 <li class="level1"><div class="li"> Select <strong>Edit | Line Width &amp; Type…</strong></div>
1905 </li>
1906 <li class="level1"><div class="li"> The “Edit Line Width * Type” dialog box displays</div>
1907 </li>
1908 <li class="level1"><div class="li"> Change the following as suites the object:</div>
1909 <ul>
1910 <li class="level2"><div class="li"> Line Width</div>
1911 </li>
1912 <li class="level2"><div class="li"> Line Type</div>
1913 </li>
1914 <li class="level2"><div class="li"> Line Dash Length</div>
1915 </li>
1916 <li class="level2"><div class="li"> Line Dash Space</div>
1917 </li>
1918 </ul>
1919 </li>
1920 <li class="level1"><div class="li"> Press OK to apply the changes</div>
1921 </li>
1922 </ul>
1923
1924 <p>
1925
1926 Note that if the line width doesn&#039;t seem to change, just pick a larger value.
1927 </p>
1928
1929 </div>
1930 <!-- EDIT930 SECTION "Line Width & Type... (ew)" [73633-74248] -->
1931 <h3 class="sectionedit931"><a name="fill_type_ef" id="fill_type_ef">Fill Type... (ef)</a></h3>
1932 <div class="level3">
1933
1934 <p>
1935 <strong>Edit | Fill Type…</strong> is used to fill boxes and circles.<br/>
1936
1937 To fill a box or circle:
1938 </p>
1939 <ul>
1940 <li class="level1"><div class="li"> Select the box or circle.</div>
1941 </li>
1942 <li class="level1"><div class="li"> Select <strong>Edit | Fill Type…</strong>. The “Edit FIll Type” dialog box is displayed.</div>
1943 </li>
1944 <li class="level1"><div class="li"> Enter:</div>
1945 <ul>
1946 <li class="level2"><div class="li"> Fill Type</div>
1947 </li>
1948 <li class="level2"><div class="li"> Line Width</div>
1949 </li>
1950 <li class="level2"><div class="li"> Angle 1</div>
1951 </li>
1952 <li class="level2"><div class="li"> Pitch 1</div>
1953 </li>
1954 <li class="level2"><div class="li"> Angle 2</div>
1955 </li>
1956 <li class="level2"><div class="li"> Pitch 2</div>
1957 </li>
1958 </ul>
1959 </li>
1960 <li class="level1"><div class="li"> Press OK.</div>
1961 </li>
1962 </ul>
1963
1964 </div>
1965 <!-- EDIT931 SECTION "Fill Type... (ef)" [74249-74589] -->
1966 <h3 class="sectionedit932"><a name="symbol_translate_et" id="symbol_translate_et">Symbol Translate... (et)</a></h3>
1967 <div class="level3">
1968
1969 <p>
1970 <strong>Edit | Symbol Translate…</strong> is used when creating a symbol, to translate the symbol to an origin for subsequent placement. The symbol may take an optional offset (in mils), as appropriate to the symbol.<br/>
1971
1972 To translate the symbol:
1973 </p>
1974 <ul>
1975 <li class="level1"><div class="li"> Open a file for the symbol</div>
1976 </li>
1977 <li class="level1"><div class="li"> Set the grid snap spacing to 100 mils (<strong>Options</strong> | <strong>Snap Grid Spacing…</strong>).</div>
1978 </li>
1979 <li class="level1"><div class="li"> Toggle the grid ON (<strong>Options</strong> | <strong>Toggle Grid On/Off</strong>)</div>
1980 </li>
1981 <li class="level1"><div class="li"> Toggle the grid snap ON (<strong>Options</strong> | <strong>Toggle Snap On/Off</strong>)</div>
1982 </li>
1983 <li class="level1"><div class="li"> Zoom as appropriate for the symbol&#039;s dimensions</div>
1984 </li>
1985 <li class="level1"><div class="li"> Draw the symbol, according to the recommendations in the <a href="http://www.geda.seul.org/docs/current/symbols/index.html" class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/index.html"  rel="nofollow">gEDA/gaf Symbol Creation Document</a></div>
1986 </li>
1987 <li class="level1"><div class="li"> Select <strong>Edit | Symbol Translate…</strong></div>
1988 </li>
1989 <li class="level1"><div class="li"> The “Translate” dialog box is displayed.</div>
1990 </li>
1991 <li class="level1"><div class="li"> Enter 0 to translate to the origin, or enter a value (in mils), positive or negative, to offset the symbol from the origin.</div>
1992 </li>
1993 <li class="level1"><div class="li"> Press OK to apply</div>
1994 </li>
1995 <li class="level1"><div class="li"> Save the symbol to the file</div>
1996 </li>
1997 </ul>
1998
1999 <p>
2000
2001 If you enter a 0, then all the objects will be translated to the origin.<br/>
2002
2003 If you enter a non-zero offset, this will be applied equally in both the X and the Y directions.<br/>
2004
2005 </p>
2006
2007 </div>
2008 <!-- EDIT932 SECTION "Symbol Translate... (et)" [74590-75754] -->
2009 <h3 class="sectionedit933"><a name="embed_component_picture_eb" id="embed_component_picture_eb">Embed Component/Picture (eb)</a></h3>
2010 <div class="level3">
2011
2012 <p>
2013 <strong>gschem</strong> supports the concept of embedded components and graphics, where all the information necessary to display a component/graphic is placed in the schematic file. <strong>Edit | Embed Component/Picture</strong> causes schematic files to be significantly larger, but it makes it easy to share schematics with other people or archive schematics. You should only embed components when absolutely necessary.<br/>
2014
2015 To <strong>Embed Component/Picture</strong>:
2016 </p>
2017 <ul>
2018 <li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
2019 </li>
2020 <li class="level1"><div class="li"> Select <strong>Edit | Embed Component/Picture</strong></div>
2021 </li>
2022 </ul>
2023
2024 <p>
2025
2026 Save the schematic. The schematic file will now contain the text strings for the embedded component or embedded graphic.<br/>
2027
2028 The <strong>Add Component…</strong> dialog box allows you to optionally embed the component.<br/>
2029
2030 The <strong>Add Picture…</strong> dialog box does NOT allow you to optionally embed the component.<br/>
2031
2032 You can only embed and unembed components. Also, you cannot embed and then mirror a component (this is a limitation of <strong>gschem</strong> and will eventually be fixed).
2033 </p>
2034
2035 </div>
2036 <!-- EDIT933 SECTION "Embed Component/Picture (eb)" [75755-76784] -->
2037 <h3 class="sectionedit934"><a name="unembed_component_picture_eu" id="unembed_component_picture_eu">Unembed Component/Picture (eu)</a></h3>
2038 <div class="level3">
2039
2040 <p>
2041 <strong>Edit | Unembed Component/Picture</strong> will move the component&#039;s or graphic&#039;s information from the schematic file&#039;s contents and output it to the original file&#039;s path/filename (i.e., the schematic file includes the path/filename information).
2042 To <strong>Unembed Component/Picture</strong>:
2043 </p>
2044 <ul>
2045 <li class="level1"><div class="li"> Select the component/picture (in <strong>Select Mode</strong>)</div>
2046 </li>
2047 <li class="level1"><div class="li"> Select <strong>Edit | Unembed Component/Picture</strong></div>
2048 </li>
2049 </ul>
2050
2051 <p>
2052
2053 Save the schematic. The schematic file will now NOT contain the text strings for the embedded component or embedded graphic.<br/>
2054
2055 You can only embed and unembed components.
2056 </p>
2057
2058 </div>
2059 <!-- EDIT934 SECTION "Unembed Component/Picture (eu)" [76785-77374] -->
2060 <h3 class="sectionedit935"><a name="update_component_ep" id="update_component_ep">Update Component (ep)</a></h3>
2061 <div class="level3">
2062
2063 <p>
2064 <strong>Edit | Update Component</strong> updates a component&#039;s definition.<br/>
2065
2066 A symbol can be modified from within <strong>gschem</strong> using the following sequence:
2067 </p>
2068 <ul>
2069 <li class="level1"><div class="li"> Select the component for which the symbol should be changed.</div>
2070 </li>
2071 <li class="level1"><div class="li"> Select <strong>Hierarchy | Down Symbol</strong>. This takes you to the symbol editor</div>
2072 </li>
2073 <li class="level1"><div class="li"> Modify the symbol. This includes modifying the symbol&#039;s graphic objects, adding/changing/deleting attributes, and moving objects with respect to the origin</div>
2074 </li>
2075 <li class="level1"><div class="li"> Don&#039;t forget to <strong>Edit | Symbol Translate</strong></div>
2076 </li>
2077 <li class="level1"><div class="li"> Select <strong>File | Save Page</strong> to save the symbol to it&#039;s file</div>
2078 </li>
2079 <li class="level1"><div class="li"> Select <strong>Hierarchy | Up Symbol</strong>. This returns you to the schematic editor</div>
2080 </li>
2081 <li class="level1"><div class="li"> With the component still selected, select <strong>Edit | Update Component</strong> to update the componet&#039;s description from the modified symbol&#039;s definition</div>
2082 </li>
2083 <li class="level1"><div class="li"> Select each component on the schematic(s) made from this symbol, and select <strong>Edit | Update Component</strong></div>
2084 </li>
2085 </ul>
2086
2087 <p>
2088
2089 New components placed on the schematic from this updated symbol will use the new symbol definition.<br/>
2090
2091 Components placed on the schematic from this symbol will be updated the next time this schematic is opened.<br/>
2092
2093 The symbol&#039;s <code>symversion</code> attribute will automatically be incremented for non-trivial changes when the symbol is saved. When a schematic is opened by <strong>gschem</strong>, all symbols used by the schematic are read from their libraries. The <code>symversion</code> attribute of the symbol read from the library is compared to the <code>symversion</code> attribute of the components in the schematic. If the <code>symversion</code> attributes are different, the <code>symversion</code> attribute is exposed on the schematic for those symbols effected. Note that:
2094 </p>
2095 <ul>
2096 <li class="level1"><div class="li"> This is a “hint” to the designer to check the symbol.</div>
2097 </li>
2098 <li class="level1"><div class="li"> You need to actually open a schematic file with <strong>gschem</strong> for the components to be updated.</div>
2099 </li>
2100 </ul>
2101
2102 </div>
2103 <!-- EDIT935 SECTION "Update Component (ep)" [77375-79184] -->
2104 <h3 class="sectionedit936"><a name="show_hide_inv_text_en" id="show_hide_inv_text_en">Show/Hide Inv Text (en)</a></h3>
2105 <div class="level3">
2106
2107 <p>
2108 <strong>Edit | Show/Hide Inv Text</strong> is most appropriate when creating or editing symbols, to view or hide the text for all of the symbol&#039;s invisible attributes.<br/>
2109
2110 <a href="#make_inv_text_vis" title=":geda:gschem_ug.fr.txt &crarr;" class="wikilink1">Make Inv Text Vis</a> is most appropriate when adding symbols to schematics, to view the text for the symbol&#039;s modifiable invisible attributes.<br/>
2111
2112 <strong>Edit | Show/Hide Inv Text</strong> toggles between making all invisible text visible and hiding all invisible text. When selected, all objects in the symbol are effected.<br/>
2113
2114 Visible text always remains visible.<br/>
2115
2116 A symbol has the following <em class="u">potential</em> attributes :
2117 </p>
2118 <ul>
2119 <li class="level1"><div class="li"> netname</div>
2120 </li>
2121 <li class="level1"><div class="li"> refdes</div>
2122 </li>
2123 <li class="level1"><div class="li"> slot</div>
2124 </li>
2125 <li class="level1"><div class="li"> value</div>
2126 </li>
2127 <li class="level1"><div class="li"> net</div>
2128 </li>
2129 <li class="level1"><div class="li"> device</div>
2130 </li>
2131 <li class="level1"><div class="li"> pinnumber</div>
2132 </li>
2133 <li class="level1"><div class="li"> pinseq</div>
2134 </li>
2135 <li class="level1"><div class="li"> pintype</div>
2136 </li>
2137 <li class="level1"><div class="li"> pinlabel</div>
2138 </li>
2139 <li class="level1"><div class="li"> source</div>
2140 </li>
2141 <li class="level1"><div class="li"> numslots</div>
2142 </li>
2143 <li class="level1"><div class="li"> slotdef</div>
2144 </li>
2145 <li class="level1"><div class="li"> graphical</div>
2146 </li>
2147 <li class="level1"><div class="li"> footprint</div>
2148 </li>
2149 <li class="level1"><div class="li"> description</div>
2150 </li>
2151 <li class="level1"><div class="li"> documentation</div>
2152 </li>
2153 <li class="level1"><div class="li"> symversion</div>
2154 </li>
2155 <li class="level1"><div class="li"> comment</div>
2156 </li>
2157 <li class="level1"><div class="li"> file</div>
2158 </li>
2159 <li class="level1"><div class="li"> model-name</div>
2160 </li>
2161 </ul>
2162
2163 <p>
2164
2165 Not all attributes need to be used to define a symbol (see the discussion of <a href="docs-20060124-gschem_ug-app_a.html" class="wikilink2" title="docs-20060124-gschem_ug-app_a.html">Appendix A -- Heavy vs Light Symbol Libraries</a>). The <strong>gschem</strong> default is to define symbols as “light”, indicating that the symbol includes as few attributes as necessary to describe the symbol. “light” symbols depend on the designer attaching additional descriptive attributes to the symbol when the symbol is placed on the schematic. For example: a “light” symbol for a resistor might include just the graphic for a resistor, its pin attributes, and the “refdes” attribute. This describes a resistor. It would be the designer&#039;s responsibility, after the resistor has been placed on the schematic, to add the “value” and “footprint” attributes appropriate for the specific resistor in the circuit. A “heavy” symbol includes more descriptive attributes. Using “light” vs. “heavy” symbols is up to the designer.<br/>
2166
2167 A symbol&#039;s attributes may be flagged as either visible or invisible. Attributes are flagged as invisible to reduce the clutter around a symbol on the schematic.<br/>
2168
2169 When creating or editing the symbol, and changing a visible attribute to an invisible attribute, the attribute can not be viewed during further editing of the symbol. It becomes difficult to place attribute text. To view both the visible and invisible text, select <strong>Edit | Show/Hide Inv Text</strong>.<br/>
2170
2171 When a symbol is instantiated on a schematic as a component, only the symbol&#039;s visible attributes are promoted to the component. For example: if a resistor&#039;s symbol defines “refdes” as the only visible attribute defined in the symbol, the only attribute that the component contains is the “refdes” attribute). Those attributes not included in the symbol definition may be added at the schematic level, component-by-component.<br/>
2172
2173 This operation is useful when drawing/debugging symbols.<br/>
2174
2175 When hidden text is visible, “Show Hidden” will appear on the status-bar in the lower right.
2176 </p>
2177
2178 </div>
2179 <!-- EDIT936 SECTION "Show/Hide Inv Text (en)" [79185-82012] -->
2180 <h3 class="sectionedit937"><a name="make_inv_text_vis_ev" id="make_inv_text_vis_ev">Make Inv Text Vis (ev)</a></h3>
2181 <div class="level3">
2182
2183 <p>
2184 <strong>Edit | Make Inv Text Vis</strong> is a quick method of making all of a component&#039;s invisible attributes visible. The same effect can be accomplished by double-clicking on the component and marking all of the entries in the Attributes listbox as “Vis?” (i.e., visible).<br/>
2185
2186 To <strong>Make Inv Text Vis</strong> for a component:
2187 </p>
2188 <ul>
2189 <li class="level1"><div class="li"> Select the component(s) in <strong>Select Mode</strong></div>
2190 </li>
2191 <li class="level1"><div class="li"> Select <strong>Edit | Make Inv Text Vis</strong></div>
2192 </li>
2193 </ul>
2194
2195 <p>
2196
2197 The attributes that had been hidden are displayed.<br/>
2198
2199 To hide the attributes again, you need to double-click the component to bring up it&#039;s “Edit Attributes” dialog box, and explicitly place a check for each attribute you want hidden.
2200 </p>
2201
2202 </div>
2203 <!-- EDIT937 SECTION "Make Inv Text Vis (ev)" [82013-82676] -->
2204 <h2 class="sectionedit938"><a name="buffer" id="buffer">Buffer</a></h2>
2205 <div class="level2">
2206
2207 <p>
2208 <strong>gschem</strong> supports 5 copy/cut/paste buffers which are visible across all opened pages and windows.
2209 </p>
2210
2211 </div>
2212 <!-- EDIT938 SECTION "Buffer" [82677-82796] -->
2213 <h3 class="sectionedit939"><a name="copy_into_1_2_3_4_5_yc" id="copy_into_1_2_3_4_5_yc">Copy into 1/2/3/4/5 (yc)</a></h3>
2214 <div class="level3">
2215
2216 <p>
2217 To copy something into a buffer:
2218 </p>
2219 <ol>
2220 <li class="level1"><div class="li"> Select the objects you want to copy.</div>
2221 </li>
2222 <li class="level1"><div class="li"> Select Buffer/Copy/Copy into buffer #.</div>
2223 </li>
2224 </ol>
2225
2226 </div>
2227 <!-- EDIT939 SECTION "Copy into 1/2/3/4/5 (yc)" [82797-82949] -->
2228 <h3 class="sectionedit940"><a name="cut_into_1_2_3_4_5_yu" id="cut_into_1_2_3_4_5_yu">Cut into 1/2/3/4/5 (yu)</a></h3>
2229 <div class="level3">
2230
2231 <p>
2232 Cut is like copy in that it removes the objects from the schematic
2233 </p>
2234
2235 </div>
2236 <!-- EDIT940 SECTION "Cut into 1/2/3/4/5 (yu)" [82950-83051] -->
2237 <h3 class="sectionedit941"><a name="paste_from_1_2_3_4_5_yp" id="paste_from_1_2_3_4_5_yp">Paste from 1/2/3/4/5 (yp)</a></h3>
2238 <div class="level3">
2239
2240 <p>
2241 To paste a buffer into the current schematic:
2242 </p>
2243 <ol>
2244 <li class="level1"><div class="li"> Fill the buffer using the above Copy or Cut.</div>
2245 </li>
2246 <li class="level1"><div class="li"> Go to the new schematic page/window.</div>
2247 </li>
2248 <li class="level1"><div class="li"> Select Buffer/Paste/Paste from buffer #.</div>
2249 </li>
2250 <li class="level1"><div class="li"> Click the first mouse button to pick an anchor point.</div>
2251 </li>
2252 <li class="level1"><div class="li"> Move the mouse to the final spot.</div>
2253 </li>
2254 <li class="level1"><div class="li"> Click the first mouse button again.</div>
2255 </li>
2256 </ol>
2257
2258 </div>
2259 <!-- EDIT941 SECTION "Paste from 1/2/3/4/5 (yp)" [83052-83405] -->
2260 <h2 class="sectionedit942"><a name="view" id="view">View</a></h2>
2261 <div class="level2">
2262
2263 </div>
2264 <!-- EDIT942 SECTION "View" [83406-83423] -->
2265 <h3 class="sectionedit943"><a name="redraw_vr" id="redraw_vr">Redraw (vr)</a></h3>
2266 <div class="level3">
2267
2268 <p>
2269 <strong>View | Redraw</strong> re-paints the current window.<br/>
2270
2271 This is useful when you have mouse/component/line/text etc… droppings left over from a previous action. It is also useful when you want to update all visual connectivity cues.
2272 </p>
2273
2274 </div>
2275 <!-- EDIT943 SECTION "Redraw (vr)" [83424-83674] -->
2276 <h3 class="sectionedit944"><a name="pan_x" id="pan_x">Pan (x)</a></h3>
2277 <div class="level3">
2278
2279 <p>
2280 <strong>View | Pan</strong> lets you change the focus of the display.<br/>
2281
2282 To pan the display:
2283 </p>
2284 <ul>
2285 <li class="level1"><div class="li"> Select <strong>View | Pan</strong></div>
2286 </li>
2287 <li class="level1"><div class="li"> Click the first mouse button at the new center of the display.</div>
2288 </li>
2289 </ul>
2290
2291 <p>
2292
2293 To pan the display using the shortcut is much simpler, simply place the mouse pointer where you want the display centered and type “x”. The display will jump to the mouse&#039;s location.<br/>
2294
2295 Pan behavior is configurable. The system-gschemrc file defines:
2296 <pre STYLE="background : LightGreen;
2297 margin-left : 2em"><font size="+0">(third-button &quot;popup&quot;)</font></pre>
2298 </p>
2299
2300 <p>
2301 If you override the system-gschemrc&#039;s default, of popping up a menu when the third mouse button is clicked, by adding:
2302 <pre STYLE="background : LightGreen;
2303 margin-left : 2em"><font size="+0">(third-button &quot;mousepan&quot;)</font></pre>
2304 </p>
2305
2306 <p>
2307 to either your user&#039;s ~/gschemrc file or local &#039;pwd&#039;/gschemrc file, the third mouse button (i.e., the right mouse button on scroll-wheel mice) will allow you to pan the schematic by holding down the third mouse button and dragging.<br/>
2308
2309 The system-gschemrc file also defines:
2310 <pre STYLE="background : LightGreen;
2311 margin-left : 2em"><font size="+0">(fast-mousepan &quot;enabled&quot;)</font></pre>
2312 </p>
2313
2314 <p>
2315 If you override the system-gschemrc&#039;s default by adding:
2316 <pre STYLE="background : LightGreen;
2317 margin-left : 2em"><font size="+0">(fast-mousepan &quot;disabled&quot;)</font></pre>
2318 </p>
2319
2320 <p>
2321 to either your user&#039;s ~/gschemrc file or local &#039;pwd&#039;/gschemrc file, text will be displayed properly when the third mouse button is held down while dragging. The <code>(third-button “mousepan”)</code> setting must also be applied for this to work. Disabling <code>fast-mousepan</code> adversely effects rendering speed while panning on large “complicated” schematics.<br/>
2322
2323 The system-gschemrc file also defines:
2324 <pre STYLE="background : LightGreen;
2325 margin-left : 2em"><font size="+0">(zoom-with-pan &quot;enabled&quot;)</font></pre>
2326 </p>
2327
2328 <p>
2329 If you override the system-gschemrc&#039;s default by adding:
2330 <pre STYLE="background : LightGreen;
2331 margin-left : 2em"><font size="+0">(zoom-with-pan &quot;disabled&quot;)</font></pre>
2332 </p>
2333
2334 <p>
2335 to either your user&#039;s ~/gschemrc file or local &#039;pwd&#039;/gschemrc file, whenever you zoom in/out, the zoom will NOT center on the mouse pointer, effectively removing the pan feature of the zoom in/out operations.
2336 </p>
2337
2338 </div>
2339 <!-- EDIT944 SECTION "Pan (x)" [83675-85471] -->
2340 <h3 class="sectionedit945"><a name="zoom_box_w" id="zoom_box_w">Zoom Box (w)</a></h3>
2341 <div class="level3">
2342
2343 <p>
2344 <strong>View | Zoom Box</strong> allows you to draw a box around a part of the <strong>gschem</strong> window and zoom  in.<br/>
2345
2346 To use <strong>View | Zoom Box</strong>:
2347 </p>
2348 <ul>
2349 <li class="level1"><div class="li"> Select <strong>View | Zoom Box</strong></div>
2350 </li>
2351 <li class="level1"><div class="li"> Position the mouse pointer at one corner of the box you want to draw</div>
2352 </li>
2353 <li class="level1"><div class="li"> Click and hold down the first mouse button</div>
2354 </li>
2355 <li class="level1"><div class="li"> Drag the mouse, drawing the zoom box around the area to which you want to zoom</div>
2356 </li>
2357 <li class="level1"><div class="li"> Release the mouse button and the display will zoom</div>
2358 </li>
2359 </ul>
2360
2361 <p>
2362
2363 To use <strong>View | Zoom Box</strong> by typing the equivalent shortcut (i.e., “<strong>w</strong>”) is more convenient. Simply position the mouse pointer at one corner of the zoom box, then type “<strong>w</strong>”.  The zoom box will start immediately using the current mouse location as the first corner of the box.<br/>
2364
2365 <strong>View | Zoom Box</strong> will attempt to zoom to the requested area, but some boxes are not legal and <strong>gschem</strong> will do it&#039;s best to zoom the requested area.
2366 </p>
2367
2368 </div>
2369 <!-- EDIT945 SECTION "Zoom Box (w)" [85472-86352] -->
2370 <h3 class="sectionedit946"><a name="zoom_extents_ve" id="zoom_extents_ve">Zoom Extents (ve)</a></h3>
2371 <div class="level3">
2372
2373 <p>
2374 <strong>View | Extents</strong> will zoom the display to fit all of the placed objects into the current window.<br/>
2375
2376 To view all of the current window&#039;s objects:
2377 </p>
2378 <ul>
2379 <li class="level1"><div class="li"> Select <strong>View | Extents</strong></div>
2380 </li>
2381 </ul>
2382
2383 <p>
2384
2385 Typing the <strong>View | Extents</strong> shortcut (i.e., “<strong>ve</strong>”) is particularly convenient for those that have learned to navigate the schematics using the shortcuts.<br/>
2386
2387 </p>
2388
2389 </div>
2390 <!-- EDIT946 SECTION "Zoom Extents (ve)" [86353-86719] -->
2391 <h3 class="sectionedit947"><a name="zoom_in_z" id="zoom_in_z">Zoom In (z)</a></h3>
2392 <div class="level3">
2393
2394 <p>
2395 <strong>View | Zoom In</strong> zooms the display in. The current center of the window is the center of the new window. This command zooms in by a factor.<br/>
2396
2397 To zoom in:
2398 </p>
2399 <ul>
2400 <li class="level1"><div class="li"> Select <strong>View | Zoom In</strong></div>
2401 </li>
2402 </ul>
2403
2404 <p>
2405
2406 The (zoom-with-pan “enabled”) configuration setting in the gschemrc files effects the operation of the zoom in shortcut (i.e., “<strong>z</strong>”). The default system-gschemrc setting for:
2407 <pre STYLE="background : LightGreen;
2408 margin-left : 2em"><font size="+0">(zoom-with-pan &quot;enabled&quot;)</font></pre>
2409 </p>
2410
2411 <p>
2412 enables zooming in, using the mouse pointer&#039;s location as the new center of the window. If this changed to:
2413 <pre STYLE="background : LightGreen;
2414 margin-left : 2em"><font size="+0">(zoom-with-pan &quot;disabled&quot;)</font></pre>
2415 </p>
2416
2417 <p>
2418 in either your user&#039;s ~/gschemrc file or local &#039;pwd&#039;/gschemrc file, whenever you zoom in, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom in operation.<br/>
2419
2420 To zoom in using the shortcut:
2421 </p>
2422 <ul>
2423 <li class="level1"><div class="li"> If the default (zoom-with-pan “enabled”) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
2424 </li>
2425 <li class="level1"><div class="li"> Type “<strong>z</strong>”</div>
2426 </li>
2427 </ul>
2428
2429 <p>
2430
2431 Typing “<strong>z</strong>” is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
2432 </p>
2433
2434 </div>
2435 <!-- EDIT947 SECTION "Zoom In (z)" [86720-87881] -->
2436 <h3 class="sectionedit948"><a name="zoom_out_z" id="zoom_out_z">Zoom Out (Z)</a></h3>
2437 <div class="level3">
2438
2439 <p>
2440 <strong>View | Zoom Out</strong> zooms the display out. The current center of the window is the center of the new window. This command zooms out by a factor.<br/>
2441
2442 To zoom out:
2443 </p>
2444 <ul>
2445 <li class="level1"><div class="li"> Select <strong>View | Zoom Out</strong></div>
2446 </li>
2447 </ul>
2448
2449 <p>
2450
2451 The (zoom-with-pan “enabled”) configuration setting in the gschemrc files effects the operation of the zoom out shortcut (i.e., “<strong>z</strong>”). The default system-gschemrc setting for:
2452 <pre STYLE="background : LightGreen;
2453 margin-left : 2em"><font size="+0">(zoom-with-pan &quot;enabled&quot;)</font></pre>
2454 </p>
2455
2456 <p>
2457 enables zooming out, using the mouse pointer&#039;s location as the new center of the window. If this changed to:
2458 <pre STYLE="background : LightGreen;
2459 margin-left : 2em"><font size="+0">(zoom-with-pan &quot;disabled&quot;)</font></pre>
2460 </p>
2461
2462 <p>
2463 in either your user&#039;s ~/gschemrc file or local &#039;pwd&#039;/gschemrc file, whenever you zoom out, the zoom will NOT center on the mouse pointer but will center on the current center of the window, effectively removing the pan feature of the zoom out operation.<br/>
2464
2465 To zoom out using the shortcut:
2466 </p>
2467 <ul>
2468 <li class="level1"><div class="li"> If the default (zoom-with-pan “enabled”) is configured in one of the gschemrc files, position the mouse pointer in the window where you want the new center</div>
2469 </li>
2470 <li class="level1"><div class="li"> Type “<strong>Z</strong>” (i.e., shift-z)</div>
2471 </li>
2472 </ul>
2473
2474 <p>
2475
2476 Typing “<strong>Z</strong>” is particularly convenient for those that have learned to navigate the schematics using the shortcuts.
2477 </p>
2478
2479 </div>
2480 <!-- EDIT948 SECTION "Zoom Out (Z)" [87882-89070] -->
2481 <h3 class="sectionedit949"><a name="zoom_full_vf" id="zoom_full_vf">Zoom Full (vf)</a></h3>
2482 <div class="level3">
2483
2484 <p>
2485 <strong>View | Zoom Full</strong> will zoom the display to the maximum possible displayable view.<br/>
2486
2487 </p>
2488
2489 <p>
2490 To view the maximum displayable area:
2491 </p>
2492 <ul>
2493 <li class="level1"><div class="li"> Select <strong>View | Zoom Full</strong></div>
2494 </li>
2495 </ul>
2496
2497 <p>
2498
2499 The window contents will immediately change to show the maximum possible displayable view.<br/>
2500
2501 </p>
2502
2503 <p>
2504 To view the maximum displayable area using the keyboard shortcut (i.e., “<strong>vf</strong>”):
2505 </p>
2506 <ul>
2507 <li class="level1"><div class="li"> Type “<strong>vf</strong>”</div>
2508 </li>
2509 </ul>
2510
2511 <p>
2512
2513 The window contents will immediately change to show the maximum possible displayable view.<br/>
2514
2515 </p>
2516
2517 <p>
2518 <strong>View | Zoom Full</strong> is useful if you like to put your working notes outside the titleblock for you schematic, for example. Just remember, these notes would now be considered part of the windows extents, so if you were to <strong>View | Extents</strong>, the display would show the titleblock and your working notes.
2519 </p>
2520
2521 </div>
2522 <!-- EDIT949 SECTION "Zoom Full (vf)" [89071-89849] -->
2523 <h2 class="sectionedit950"><a name="page" id="page">Page</a></h2>
2524 <div class="level2">
2525
2526 </div>
2527 <!-- EDIT950 SECTION "Page" [89850-89868] -->
2528 <h3 class="sectionedit951"><a name="manager_pm" id="manager_pm">Manager... (pm)</a></h3>
2529 <div class="level3">
2530
2531 </div>
2532 <!-- EDIT951 SECTION "Manager... (pm)" [89869-89896] -->
2533 <h3 class="sectionedit952"><a name="next" id="next">Next (&gt;)</a></h3>
2534 <div class="level3">
2535
2536 </div>
2537 <!-- EDIT952 SECTION "Next (>)" [89897-89917] -->
2538 <h3 class="sectionedit953"><a name="previous" id="previous">Previous (&lt;)</a></h3>
2539 <div class="level3">
2540
2541 </div>
2542 <!-- EDIT953 SECTION "Previous (<)" [89918-89942] -->
2543 <h3 class="sectionedit954"><a name="new_pe" id="new_pe">New (pe)</a></h3>
2544 <div class="level3">
2545
2546 </div>
2547 <!-- EDIT954 SECTION "New (pe)" [89943-89963] -->
2548 <h3 class="sectionedit955"><a name="revert_pr" id="revert_pr">Revert (pr)</a></h3>
2549 <div class="level3">
2550
2551 </div>
2552 <!-- EDIT955 SECTION "Revert (pr)" [89964-89987] -->
2553 <h3 class="sectionedit956"><a name="close_pc" id="close_pc">Close (pc)</a></h3>
2554 <div class="level3">
2555
2556 </div>
2557 <!-- EDIT956 SECTION "Close (pc)" [89988-90010] -->
2558 <h3 class="sectionedit957"><a name="discard_pd" id="discard_pd">Discard (pd)</a></h3>
2559 <div class="level3">
2560
2561 </div>
2562 <!-- EDIT957 SECTION "Discard (pd)" [90011-90035] -->
2563 <h2 class="sectionedit958"><a name="add" id="add">Add</a></h2>
2564 <div class="level2">
2565
2566 </div>
2567 <!-- EDIT958 SECTION "Add" [90036-90052] -->
2568 <h3 class="sectionedit959"><a name="component_i" id="component_i">Component... (i)</a></h3>
2569 <div class="level3">
2570
2571 <p>
2572 <strong>Add | Component…</strong> Ouvre une boîte de dialogue qui vous
2573 </p>
2574 <pre class="code">permet de placer les composants depuis les bibliothèques de composants.\\</pre>
2575
2576 <p>
2577 Pour placer un composant:
2578 </p>
2579 <ul>
2580 <li class="level1"><div class="li"> Select <strong>Add |Component…</strong></div>
2581 </li>
2582 <li class="level1"><div class="li"> Select a component Library from the left list-box</div>
2583 </li>
2584 <li class="level1"><div class="li"> Sélectionnez un Composant dans la liste de droite</div>
2585 </li>
2586 <li class="level1"><div class="li"> Confirm the symbol is correct by reviewing the image in the Preview window</div>
2587 </li>
2588 <li class="level1"><div class="li"> Move the mouse into the main drawing window (you should see an outline follow the mouse pointer).</div>
2589 </li>
2590 <li class="level1"><div class="li"> Press the first mouse button to anchor the component</div>
2591 </li>
2592 <li class="level1"><div class="li"> Position the mouse pointer, and keep pressing the first mouse button to anchor additional instances of the component</div>
2593 </li>
2594 <li class="level1"><div class="li"> When finished anchoring components, press the last mouse button or the ESC key</div>
2595 </li>
2596 </ul>
2597
2598 <p>
2599
2600 Si un nom de composant est déjà sélectionné, taper Appliquer et déplacer la souris dans la fenêtre   principale vous permettra placer à nouveau ce composant.<br/>
2601
2602 Vous pouvez effectuer une rotation avant le placement du composant en cliquant sur le bouton du milieu. Pour chaque clic de bouton, le composant effectuera une rotation de 90 degrésdans le sens inverse des aiguilles.<br/>
2603
2604 Care has been taken to give components descriptive names in the libraries, though it is sometimes difficult to determine what the component really represents from its name.<br/>
2605
2606 For example: in the analog library there are four capacitor entries:
2607 </p>
2608 <ul>
2609 <li class="level1"><div class="li"> capacitor-1.sym</div>
2610 </li>
2611 <li class="level1"><div class="li"> capacitor-2.sym</div>
2612 </li>
2613 <li class="level1"><div class="li"> capacitor-3.sym</div>
2614 </li>
2615 <li class="level1"><div class="li"> capacitor-4.sym</div>
2616 </li>
2617 </ul>
2618
2619 <p>
2620
2621 It helps to preview the symbol in the “Select Component” dialog box before selecting and placing the symbol.
2622 </p>
2623
2624 </div>
2625 <!-- EDIT959 SECTION "Component... (i)" [90053-91651] -->
2626 <h3 class="sectionedit960"><a name="net_n" id="net_n">Net (n)</a></h3>
2627 <div class="level3">
2628
2629 <p>
2630 <strong>Net</strong> Dessine un nouveau segment de liaison.<br/>
2631
2632 A net is typically a contiguous set of line segments between two pins, though it is possible to draw nets between a pin and a point on another net, or between two nets.<br/>
2633
2634 For example, the following diagram shows 3 net segments:
2635 </p>
2636 <ul>
2637 <li class="level1"><div class="li"> Between R1 and R2</div>
2638 </li>
2639 <li class="level1"><div class="li"> Between R3 and R4</div>
2640 </li>
2641 <li class="level1"><div class="li"> Between the two nets</div>
2642 </li>
2643 </ul>
2644 <div class="table sectionedit961"><table class="inline">
2645         <tr class="row0">
2646                 <td class="col0"> <a href="media/geda/nets.jpg" class="media" target="_blank" title="geda:nets.jpg"><img src="media/geda/nets.jpg" class="media" alt="" /></a> </td>
2647         </tr>
2648 </table></div>
2649 <!-- EDIT961 TABLE [92017-92039] -->
2650 <p>
2651
2652 Note the small red segment at the end of the resistor&#039;s pins. All pins in <strong>gschem</strong> have this red segment. This is the connectivity cue for the pin. It is sometimes difficult to “grab” this attachment point when drawing nets, you may need to zoom in on the pin. To zoom in, press the “z” key. To zoom out, press the “Z” (i.e., shift-z) key.<br/>
2653
2654 To begin drawing a net using the menu:
2655 </p>
2656 <ul>
2657 <li class="level1"><div class="li"> Select <strong>Add | Net</strong></div>
2658 </li>
2659 <li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pin&#039;s attachment point</div>
2660 </li>
2661 <li class="level1"><div class="li"> Position the mouse pointer over the pin&#039;s connectivity cue</div>
2662 </li>
2663 <li class="level1"><div class="li"> Press the first mouse button to start the net</div>
2664 </li>
2665 </ul>
2666
2667 <p>
2668
2669 To begin drawing the net using the shortcut:
2670 </p>
2671 <ul>
2672 <li class="level1"><div class="li"> Zoom in on the component where the net is to start, so that you can easily grab the pin&#039;s attachment point</div>
2673 </li>
2674 <li class="level1"><div class="li"> Position the mouse pointer over the pin&#039;s connectivity cue</div>
2675 </li>
2676 <li class="level1"><div class="li"> Press the “n” key</div>
2677 </li>
2678 </ul>
2679
2680 <p>
2681
2682 To continue drawing the net segment(s):
2683 </p>
2684 <ul>
2685 <li class="level1"><div class="li"> Drag the mouse pointer in the direction of the end-point</div>
2686 </li>
2687 <li class="level1"><div class="li"> For any necessary 90º turns, single-click the mouse, and continue dragging the mouse pointer toward the end-point</div>
2688 </li>
2689 <li class="level1"><div class="li"> For any necessary non-orthogonal net segments (e.g., 45º angle), hold down the CONTROL button, single-click the mouse, and continue dragging the mouse pointer to the end-point</div>
2690 </li>
2691 <li class="level1"><div class="li"> When you reach the end-point, press the first mouse button to end the net segment</div>
2692 </li>
2693 <li class="level1"><div class="li"> Another net segment will start at the last end-point</div>
2694 <ul>
2695 <li class="level2"><div class="li"> If this second pin is to be connected to a third pin, continue as above</div>
2696 </li>
2697 <li class="level2"><div class="li"> If this is the end of the connections, press the last mouse button (or ESC) to end the net</div>
2698 </li>
2699 </ul>
2700 </li>
2701 </ul>
2702
2703 <p>
2704
2705 Appuyez sur le dernier bouton de souris ou sur ESC pour effacer toute liaison en cours.<br/>
2706
2707 If the net is cancelled you are automatically placed in <strong>Select Mode</strong>. You must pick <strong>Add | Net</strong> again or type the shortcut to add more nets.<br/>
2708
2709 You cannot connect a net segment to the middle of a non-orthogonal net.<br/>
2710
2711 The boxes at the end of the nets are connectivity cues. Red boxes signify a dangling net (not connected to anything).<br/>
2712
2713 Filled circles are midpoint connections/junctions. These cues are drawn automatically and are an indicator of electrical connectivity.<br/>
2714
2715 See <a href="docs-20060124-gschem_ug-electrical_connectivity.html" class="wikilink2" title="docs-20060124-gschem_ug-electrical_connectivity.html">Electrical Connectivity</a> for more information.
2716 </p>
2717
2718 </div>
2719 <!-- EDIT960 SECTION "Net (n)" [91652-94283] -->
2720 <h3 class="sectionedit962"><a name="bus_u" id="bus_u">Bus (u)</a></h3>
2721 <div class="level3">
2722
2723 <p>
2724 <strong>Add | Bus</strong> est basiquement la même chose que <strong>Add | Net</strong>, except that it draws buses.<br/>
2725
2726 Buses are very new and there are many aspects which are not defined yet, so keep that in mind as you uses buses. More to be added here eventually.
2727 </p>
2728
2729 </div>
2730 <!-- EDIT962 SECTION "Bus (u)" [94284-94543] -->
2731 <h3 class="sectionedit963"><a name="attribute_aa" id="attribute_aa">Attribute... (aa)</a></h3>
2732 <div class="level3">
2733
2734 <p>
2735 <strong>Add | Attribute…</strong> is appropriate when creating or editing symbols, to add a new attribute.<br/>
2736
2737 <strong>Add | Attribute…</strong> brings up the “Single Attribute Editor” dialog box. This dialog box is ONLY used to add attributes. It does not display or manipulate already placed attributes.<br/>
2738
2739 Un attribut n&#039;est rien de plus qu&#039;un objet texte qui est de la forme name=value (Il ne peut y avoir  d&#039;espace à gauche et à droite de la paire name,value). Il peut soit être attaché à un objet ou détaché.<br/>
2740
2741 Pour attacher un attribut détaché (e.g., “comment”, “documentation”, etc.) au symbole:
2742 </p>
2743 <ul>
2744 <li class="level1"><div class="li"> Select <strong>Add | Attribute…</strong></div>
2745 </li>
2746 <li class="level1"><div class="li"> Select an attribute name off of the pulldown list, or type the attribute name into the name entry</div>
2747 </li>
2748 <li class="level1"><div class="li"> Saisissez la valeur pour l&#039;attribut</div>
2749 </li>
2750 <li class="level1"><div class="li"> Pick any of the attribute options</div>
2751 </li>
2752 <li class="level1"><div class="li"> Cliquez sur OK et l&#039;attribut sera placé.</div>
2753 </li>
2754 </ul>
2755
2756 <p>
2757
2758 Si vous voulez attacher un attribut à un objet, sélectionnez d&#039;abord l&#039;objet souhaité et pressez ensuite
2759 <strong>Add | Attribute…</strong> depuis le menu déroulant. Si vous cliquez sur un objet qui possède des attributs attachés, ils doivent être aussi sélectionnés.<br/>
2760
2761 Si vous sélectionnez <strong>Add | Attribute…</strong> en dehors des menus déroulants alors vous n&#039;avez pas beaucoup de contrôle sur le placement de l&#039;attribut (il prend place soit en bas à gauche de l&#039;extension de l&#039;objet soit à l&#039;origine de tout objet sélectionné). Si vous exécutez néanmoins Add/Attribute (i.e., “aa”) en utilisant la touche de raccourci alors la position courante de la souris est utilisé comme point d&#039;encrage pour l&#039;objet attribut.<br/>
2762
2763 Vous ne pouvez pas placer un attribut incomplet (un attribut sans nom et sans valeur).<br/>
2764
2765 Please see <a href="docs-20060124-gschem_ug-components_symbols_objects_attributes.html" class="wikilink2" title="docs-20060124-gschem_ug-components_symbols_objects_attributes.html">Components/Symbols/Objects/Attributes</a> for more info on how to use attributes.
2766 </p>
2767
2768 </div>
2769 <!-- EDIT963 SECTION "Attribute... (aa)" [94544-96350] -->
2770 <h3 class="sectionedit964"><a name="text_at" id="text_at">Text... (at)</a></h3>
2771 <div class="level3">
2772
2773 <p>
2774 <strong>Add | Text…</strong> displays the “Text Entry…” dialog box.
2775 To place text:
2776 </p>
2777 <ul>
2778 <li class="level1"><div class="li"> Select <strong>Options | Text Size…</strong> and select the size for the text</div>
2779 </li>
2780 <li class="level1"><div class="li"> Select <strong>Add | Text…</strong></div>
2781 </li>
2782 <li class="level1"><div class="li"> Type the text in the entry field (multiple lines may be entered by pressing Enter)</div>
2783 </li>
2784 <li class="level1"><div class="li"> Press Apply or type Enter</div>
2785 </li>
2786 <li class="level1"><div class="li"> Déplacez la souris dans la fenêtre principale (un soulignement de texte devrait apparaître et suivre </div>
2787 </li>
2788 </ul>
2789
2790 <p>
2791 la souris)
2792 </p>
2793 <ul>
2794 <li class="level1"><div class="li"> Pressez le premier bouton de souris pour ancrer le texte</div>
2795 </li>
2796 <li class="level1"><div class="li"> Close the “Text Entry…” dialog box</div>
2797 </li>
2798 </ul>
2799
2800 <p>
2801
2802 Si vous laissez la boîte de dialogue d&#039;ajout de texte (<strong>Add | Text…</strong>) ouverte, vous pouvez replacer le même objet texte encore et encore en cliquant simplement sur apply (ou en pressant enter) et en déplaçant la souris dans la fenêtre principale.<br/>
2803
2804 The following settings in the system-gschemrc file, the user&#039;s ~/gschemrc file, or the local &#039;pwd&#039;/gschemrc file control how text is displayed:</p>
2805 <dl>
2806 <dt><span class='term'> text-origin-marker</span></dt>
2807 <dd>Controls if the text origin markers are displayed.</dd>
2808 <dt><span class='term'> text-size</span></dt>
2809 <dd>Sets the default text size.</dd>
2810 <dt><span class='term'> text-caps-style</span></dt>
2811 <dd>Sets the default caps style used for the display of text</dd>
2812 <dt><span class='term'> output-text</span></dt>
2813 <dd>Controls how text is rendered to postscript</dd>
2814 </dl>
2815 <p>Le texte placé débutera automatiquement avec une majuscule. Veuillez voir la section Fichiers
2816 Ressource ci-dessous sur comment contrôler ce comportement.<br/>
2817
2818 Pour effacer un emplacement de texte, pressez le dernier bouton de souris ou sur la touche ESC.<br/>
2819
2820 Si vous créez du texte dans la forme name=value alors vous êtes en cours de création d&#039;attributs. gEDA permet aux attributs généraux de flotter librement (ou détachés). C&#039;est une bonne idée de changer la couleur de ces attributs flottants à la couleur des attributs courants (qui est aussi appelée couleur d&#039;attribut attaché) pour indiquer que le l&#039;objet texte est un attribut.<br/>
2821
2822 Vous pouvez faire pivoter le texte avant de le placer en cliquant sur le bouton milieu. Pour chaque clic de bouton, le texte fera une rotation de 90 degrés.<br/>
2823
2824 </p>
2825
2826 </div>
2827 <!-- EDIT964 SECTION "Text... (at)" [96351-98361] -->
2828 <h3 class="sectionedit965"><a name="line_l" id="line_l">Line (l)</a></h3>
2829 <div class="level3">
2830
2831 <p>
2832 <strong>Add | Line</strong> draws a single line segment.<br/>
2833
2834 To draw a line:
2835 </p>
2836 <ul>
2837 <li class="level1"><div class="li"> If you want to snap the line to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you don&#039;t see “Snap Off” on the status-bar</div>
2838 </li>
2839 <li class="level1"><div class="li"> Select <strong>Add | Line</strong></div>
2840 </li>
2841 <li class="level1"><div class="li"> If you want to constrain the line to 90º movements, hold the CONTROL key down while moving the mouse</div>
2842 </li>
2843 <li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
2844 </li>
2845 <li class="level1"><div class="li"> Press the first mouse button</div>
2846 </li>
2847 <li class="level1"><div class="li"> Move the mouse in the intended direction</div>
2848 </li>
2849 <li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
2850 </li>
2851 <li class="level1"><div class="li"> Continue placing lines, until you either press the second mouse button or type the Escape key</div>
2852 </li>
2853 </ul>
2854
2855 <p>
2856
2857 <strong>Add | Line</strong> dessine une ligne de la même manière qu&#039;en dessinant les réseaux avec les exceptions suivantes:
2858 </p>
2859 <ul>
2860 <li class="level1"><div class="li"> Une ligne n&#039;a pas de signification électrique</div>
2861 </li>
2862 <li class="level1"><div class="li"> Seule un segment de ligne est dessiné</div>
2863 </li>
2864 <li class="level1"><div class="li"> Vous gardez les lignes dessinées tant que vous êtes dans le mode de dessin de lignes (<strong>Line Mode</strong>).</div>
2865 </li>
2866 </ul>
2867
2868 <p>
2869
2870 Pour effacer une ligne directe en cours, pressez le dernier bouton de souris ou la touche ESC.
2871 </p>
2872
2873 </div>
2874 <!-- EDIT965 SECTION "Line (l)" [98362-99530] -->
2875 <h3 class="sectionedit966"><a name="box_b" id="box_b">Box (b)</a></h3>
2876 <div class="level3">
2877
2878 <p>
2879 <strong>Add | Box</strong> draws a box.
2880 To draw a box:
2881 </p>
2882 <ul>
2883 <li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you don’t see “Snap Off” on the status-bar</div>
2884 </li>
2885 <li class="level1"><div class="li"> Select <strong>Add | Box</strong></div>
2886 </li>
2887 <li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
2888 </li>
2889 <li class="level1"><div class="li"> Press the first mouse button</div>
2890 </li>
2891 <li class="level1"><div class="li"> Move the mouse in the intended direction</div>
2892 </li>
2893 <li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again</div>
2894 </li>
2895 <li class="level1"><div class="li"> Continue placing boxes, until you either press the second mouse button or type the ESC key</div>
2896 </li>
2897 </ul>
2898
2899 <p>
2900
2901 To cancel a box in progress, press the last mouse button or type the ESC key.<br/>
2902
2903 A box has no electrical significance.
2904 </p>
2905
2906 </div>
2907 <!-- EDIT966 SECTION "Box (b)" [99531-100283] -->
2908 <h3 class="sectionedit967"><a name="circle_ai" id="circle_ai">Circle (ai)</a></h3>
2909 <div class="level3">
2910
2911 <p>
2912 <strong>Add | Circle</strong> creates a circle.<br/>
2913
2914 To draw a circle:
2915 </p>
2916 <ul>
2917 <li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you don’t see “Snap Off” on the status-bar</div>
2918 </li>
2919 <li class="level1"><div class="li"> Select <strong>Add | Circle</strong></div>
2920 </li>
2921 <li class="level1"><div class="li"> Placez le centre du cercle </div>
2922 </li>
2923 <li class="level1"><div class="li"> Pressez le premier bouton</div>
2924 </li>
2925 <li class="level1"><div class="li"> Déplacez la souris pour voir un surlignement du cercle</div>
2926 </li>
2927 <li class="level1"><div class="li"> Pressez le premier bouton de souris pour terminer le cercle</div>
2928 </li>
2929 <li class="level1"><div class="li"> Continue placing circles, until you either press the second mouse button or type the ESC key</div>
2930 </li>
2931 </ul>
2932
2933 <p>
2934
2935 Pour dessiner un cercle (en utilisant le raccourci clavier), identique à au-dessus excepté que ce centre
2936 du cercle est pris sur la dernière position de souris lorsque vous saisissez le raccourci.<br/>
2937
2938 Pour effacer un dessin de cercle en cours, pressez sur le dernier bouton de souris ou sur la touche ESC.<br/>
2939
2940 </p>
2941
2942 </div>
2943 <!-- EDIT967 SECTION "Circle (ai)" [100284-101234] -->
2944 <h3 class="sectionedit968"><a name="arc_ar" id="arc_ar">Arc (ar)</a></h3>
2945 <div class="level3">
2946
2947 <p>
2948 <strong>Add | Arc</strong> draws an arc.
2949 Pour dessiner un arc:
2950 </p>
2951 <ul>
2952 <li class="level1"><div class="li"> If you want to snap the box to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you don’t see “Snap Off” on the status-bar</div>
2953 </li>
2954 <li class="level1"><div class="li"> Select <strong>Add | Arc</strong></div>
2955 </li>
2956 <li class="level1"><div class="li"> Place the mouse pointer at the center-point for the arc</div>
2957 </li>
2958 <li class="level1"><div class="li"> Press the first mouse button</div>
2959 </li>
2960 <li class="level1"><div class="li"> Move the mouse to the right, to define the radius of the arc</div>
2961 </li>
2962 <li class="level1"><div class="li"> Press the first mouse button again</div>
2963 </li>
2964 <li class="level1"><div class="li"> Enter the Start Angle (in degrees) – 0º is the “x” axis</div>
2965 </li>
2966 <li class="level1"><div class="li"> Enter the Degrees of Sweep (for counter-clockwise sweep)</div>
2967 </li>
2968 <li class="level1"><div class="li"> Press OK</div>
2969 </li>
2970 <li class="level1"><div class="li"> Continue placing arcs, until you either press the second mouse button or type the ESC key</div>
2971 </li>
2972 </ul>
2973
2974 <p>
2975
2976 L&#039;angle de démarrage peut être positif ou négatif. Les degrés sont spécifiés en utilisant le système des coordonnées Cartésiennes standard. Les degrés de sweep peuvent être positifs ou négatifs.<br/>
2977
2978 Pour effacer un arc en cours de dessin (lorsqu&#039;il y a le rayon) pressez le dernier bouton de souris ou la touche ESC ou pressez le bouton Cancel dans la boîte de dialogue arc.
2979 </p>
2980
2981 </div>
2982 <!-- EDIT968 SECTION "Arc (ar)" [101235-102395] -->
2983 <h3 class="sectionedit969"><a name="pin_ap" id="pin_ap">Pin (ap)</a></h3>
2984 <div class="level3">
2985
2986 <p>
2987 <strong>Add | Pin</strong> adds a pin.<br/>
2988
2989 Though you can <strong>Add | Pin</strong> while entering a schematic, it only makes sense to create pins while creating or editing symbol files.<br/>
2990
2991 To draw a pin:
2992 </p>
2993 <ul>
2994 <li class="level1"><div class="li"> Set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you don’t see “Snap Off” on the status-bar. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf" class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"  rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies grid settings for pin placement in gEDA/gaf compliant symbols files.</div>
2995 </li>
2996 <li class="level1"><div class="li"> Select <strong>Add | Pin</strong></div>
2997 </li>
2998 <li class="level1"><div class="li"> Pins are constrained to 90º movements</div>
2999 </li>
3000 <li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
3001 </li>
3002 <li class="level1"><div class="li"> Press the first mouse button</div>
3003 </li>
3004 <li class="level1"><div class="li"> Move the mouse in the intended direction. The <a href="http://www.geda.seul.org/docs/current/symbols/symbols.pdf" class="urlextern" title="http://www.geda.seul.org/docs/current/symbols/symbols.pdf"  rel="nofollow">gEDA/gaf Symbol Creation Document</a> specifies the length of pins in gEDA/gaf compliant symbol files.</div>
3005 </li>
3006 <li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button</div>
3007 </li>
3008 <li class="level1"><div class="li"> Continue placing pins, until you either press the second mouse button or type the Escape key</div>
3009 </li>
3010 </ul>
3011
3012 <p>
3013
3014 To cancel a pin in progress, press the last mouse button or the ESC key.
3015 </p>
3016
3017 </div>
3018 <!-- EDIT969 SECTION "Pin (ap)" [102396-103583] -->
3019 <h3 class="sectionedit970"><a name="picture_ag" id="picture_ag">Picture... (ag)</a></h3>
3020 <div class="level3">
3021
3022 <p>
3023 <strong>Add | Picture</strong> places a graphic in the schematic.
3024 To draw a picture:
3025 </p>
3026 <ul>
3027 <li class="level1"><div class="li"> If you want to snap the picture to the grid, set the grid spacing by selecting <strong>Options | Snap Grid Spacing…</strong> and entering the grid spacing, and then selecting <strong>Options | Toggle Snap On/Off</strong> until you don’t see “Snap Off” on the status-bar</div>
3028 </li>
3029 <li class="level1"><div class="li"> Select <strong>Add | Picture</strong></div>
3030 </li>
3031 <li class="level1"><div class="li"> Select the graphic file from the “Please select a picture file” dialog box</div>
3032 </li>
3033 <li class="level1"><div class="li"> Press OK</div>
3034 </li>
3035 <li class="level1"><div class="li"> Position the mouse pointer to the start-point</div>
3036 </li>
3037 <li class="level1"><div class="li"> Press the first mouse button</div>
3038 </li>
3039 <li class="level1"><div class="li"> Move the mouse in the intended direction. The outline of the picture will appear, retaining the aspect ratio of the original picture.</div>
3040 </li>
3041 <li class="level1"><div class="li"> When positioned at the end-point, press the first mouse button again.</div>
3042 </li>
3043 <li class="level1"><div class="li"> Continue placing pictures, until you either press the second mouse button or type the ESC key</div>
3044 </li>
3045 </ul>
3046
3047 <p>
3048
3049 To cancel a picture in progress, press the last mouse button or type the ESC key.<br/>
3050
3051 A picture has no electrical significance.
3052 </p>
3053
3054 </div>
3055 <!-- EDIT970 SECTION "Picture... (ag)" [103584-104579] -->
3056 <h2 class="sectionedit971"><a name="hierarchy" id="hierarchy">Hierarchy</a></h2>
3057 <div class="level2">
3058
3059 </div>
3060 <!-- EDIT971 SECTION "Hierarchy" [104580-104602] -->
3061 <h3 class="sectionedit972"><a name="down_schematic_hd" id="down_schematic_hd">Down Schematic (Hd)</a></h3>
3062 <div class="level3">
3063
3064 <p>
3065 <strong>Hierarchy | Down Schematic</strong> shifts the focus from the current schematic to a sub-schematic.<br/>
3066
3067 Descend dans un symbole, en ouvrant tous les schémas sous-jacents. Cela ouvrira typiquement un schéma sous-jacent du composant sélectionné s&#039;il existe dans le chemin de recherche de la bibliothèque source. Voyez la section des Fichiers Ressource sur la manière de définir ce chemin.<br/>
3068
3069 Il y a actuellement deux manières de spécifier qu&#039;un symbole possède un schéma sous-jacent ou des schémas:
3070 </p>
3071 <ol>
3072 <li class="level1"><div class="li"> Le schéma sous-jacent doit avoir le même nom que le symbole mais avec une extension .sch et doit suivre la convention de nommage de suffixe _#. Voyez la section Fichiers au-dessus à propos de cette convention.</div>
3073 </li>
3074 <li class="level1"><div class="li"> Attacher un attribut au symbole appelé source=filename.sch filename.sch n&#039;est pas un chemin vers le symbole mais plutôt un nom de base (le dernier fichier dans le spécificateur de chemin) du chemin de symbole. Le schéma sous-jacent sera encore recherché dans le chemin de bibliothèque source. Vous pouvez spécifier des attributs source= multiples. Les schémas sous-jacents seront ouverts dans l&#039;ordre de découverte de l&#039;attribut source= .</div>
3075 </li>
3076 </ol>
3077
3078 <p>
3079
3080 S&#039;il a des schémas sous-jacents multiples, ils seront chargés. Le mouvement entre les pages de schéma est limité (au niveau du même jeu des schémas sous-jacent) à moins que le mot-clé rc enforce-hierarchy ne soit modifié pour permettre un mode de libre circulation transversal. Veuillez voir la section des Fichiers de Ressource pour plus d&#039;informations.<br/>
3081
3082 Il est aussi recommandé que vous mainteniez des noms uniques pour les divers niveaux (lorsque vous
3083 utilisez l&#039;attribut source=) pour éviter des possibles confusions. Les mécanismes hiérarchiques sont assez nouveaux et vous pouvez craindre quelques anomalies (et veuillez les rapporter s&#039;il vous plaît).
3084 </p>
3085
3086 </div>
3087 <!-- EDIT972 SECTION "Down Schematic (Hd)" [104603-106479] -->
3088 <h3 class="sectionedit973"><a name="down_symbol_hs" id="down_symbol_hs">Down Symbol (Hs)</a></h3>
3089 <div class="level3">
3090
3091 <p>
3092 Cette option ouvrira le symbole du composant sélectionné.<br/>
3093
3094 Une fois que le symbole est ouvert, l&#039;utilisateur peut l&#039;éditer et le sauvegarder.<br/>
3095
3096 A ce moment, le schéma principal ne verra pas les changements du symbole à moins que le schéma principal
3097 ne soit rechargé ou que File/Revert ne soit exécuté. Cela sera modifié un jour.
3098 </p>
3099
3100 </div>
3101 <!-- EDIT973 SECTION "Down Symbol (Hs)" [106480-106848] -->
3102 <h3 class="sectionedit974"><a name="up_hu" id="up_hu">Up (Hu)</a></h3>
3103 <div class="level3">
3104
3105 <p>
3106 Cette option permettra de remonter dans la hiérarchie (s&#039;il y a des pages au-dessus de la page
3107 actuellement affichée).
3108 </p>
3109
3110 </div>
3111 <!-- EDIT974 SECTION "Up (Hu)" [106849-106989] -->
3112 <h3 class="sectionedit975"><a name="documentation_ho" id="documentation_ho">Documentation (Ho)</a></h3>
3113 <div class="level3">
3114
3115 <p>
3116 Open any documentation available for the selected symbol/component.<br/>
3117
3118 The job is handed over to “gschemdoc”, which makes a best-effort attempt of finding relevant documentation.<br/>
3119
3120 The documention would normally be in <acronym title="Portable Document Format">PDF</acronym>, <acronym title="HyperText Markup Language">HTML</acronym>, text or image format, but gschemdoc tries to be as transparent as possible on this account.<br/>
3121
3122 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 <acronym title="Uniform Resource Locator">URL</acronym>.<br/>
3123
3124 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.<br/>
3125
3126 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”.<br/>
3127
3128 Failing that, the file name for the symbol itself will be used as basis for the search.
3129 </p>
3130
3131 </div>
3132 <!-- EDIT975 SECTION "Documentation (Ho)" [106990-108074] -->
3133 <h2 class="sectionedit976"><a name="attributes1" id="attributes1">Attributes</a></h2>
3134 <div class="level2">
3135
3136 </div>
3137 <!-- EDIT976 SECTION "Attributes" [108075-108098] -->
3138 <h3 class="sectionedit977"><a name="attach_ta" id="attach_ta">Attach (ta)</a></h3>
3139 <div class="level3">
3140
3141 <p>
3142 The Attach command allows you to take a text item (in the proper form; <code>name=value</code>) and attach it to another object.<br/>
3143
3144 To use Attributes/Attach:
3145 </p>
3146 <ol>
3147 <li class="level1"><div class="li"> Select the object which will receive the attributes</div>
3148 </li>
3149 <li class="level1"><div class="li"> Select the text object(s) which will be attached to the above object</div>
3150 </li>
3151 <li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Attach</div>
3152 </li>
3153 </ol>
3154
3155 <p>
3156
3157 The order of the sequence of selecting the object and then the text items is important; <strong>gschem</strong> will not allow you to select the text items first and then the object. After going through the above sequence the text item will turn yellow (or the current attached attribute color) signifying that the text item is an attached attribute.<br/>
3158
3159 You cannot attach a single attribute to several different objects. You cannot attach non-text items as attributes.
3160 </p>
3161
3162 </div>
3163 <!-- EDIT977 SECTION "Attach (ta)" [108099-108906] -->
3164 <h3 class="sectionedit978"><a name="detach_td" id="detach_td">Detach (td)</a></h3>
3165 <div class="level3">
3166
3167 <p>
3168 Detach allows you to deassociate attributes from objects.<br/>
3169
3170 To deselect an object of all attributes:
3171 </p>
3172 <ol>
3173 <li class="level1"><div class="li"> Select the object of interest</div>
3174 </li>
3175 <li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Detach</div>
3176 </li>
3177 </ol>
3178
3179 <p>
3180
3181 All the attached attributes (even if they are not selected) will be detached from the object. This behavior is probably broken and will eventually be fixed (so that only selected attributes are detached).<br/>
3182
3183 When you detach attributes then they turn red (or the current detached attribute color). This color changes allows you to spot text which was an attribute and is now dangling (unattached).
3184 </p>
3185
3186 </div>
3187 <!-- EDIT978 SECTION "Detach (td)" [108907-109513] -->
3188 <h3 class="sectionedit979"><a name="show_value_tv" id="show_value_tv">Show Value (tv)</a></h3>
3189 <div class="level3">
3190
3191 <p>
3192 These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
3193
3194 To use the options:
3195 </p>
3196 <ol>
3197 <li class="level1"><div class="li"> Select the attribute(s) of interest</div>
3198 </li>
3199 <li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
3200 </li>
3201 </ol>
3202
3203 <p>
3204
3205 The text item(s) should immediately change.<br/>
3206
3207 These operations only work on text items which are in the form <code>name=value</code>
3208 </p>
3209
3210 </div>
3211 <!-- EDIT979 SECTION "Show Value (tv)" [109514-110052] -->
3212 <h3 class="sectionedit980"><a name="show_name_tn" id="show_name_tn">Show Name (tn)</a></h3>
3213 <div class="level3">
3214
3215 <p>
3216 These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
3217
3218 To use the options:
3219 </p>
3220 <ol>
3221 <li class="level1"><div class="li"> Select the attribute(s) of interest</div>
3222 </li>
3223 <li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
3224 </li>
3225 </ol>
3226
3227 <p>
3228
3229 The text item(s) should immediately change.<br/>
3230
3231 These operations only work on text items which are in the form <code>name=value</code>
3232 </p>
3233
3234 </div>
3235 <!-- EDIT980 SECTION "Show Name (tn)" [110053-110590] -->
3236 <h3 class="sectionedit981"><a name="show_both_tb" id="show_both_tb">Show Both (tb)</a></h3>
3237 <div class="level3">
3238
3239 <p>
3240 These operations allow you to control which part of the attribute string is visible. Usually you are just interested in seeing the <code>value</code> of the attribute, but there are circumstances where seeing the <code>name</code> and <code>value</code> (or maybe just the <code>name</code>) would be useful.<br/>
3241
3242 To use the options:
3243 </p>
3244 <ol>
3245 <li class="level1"><div class="li"> Select the attribute(s) of interest</div>
3246 </li>
3247 <li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Show *</div>
3248 </li>
3249 </ol>
3250
3251 <p>
3252
3253 The text item(s) should immediately change.<br/>
3254
3255 These operations only work on text items which are in the form <code>name=value</code>
3256 </p>
3257
3258 </div>
3259 <!-- EDIT981 SECTION "Show Both (tb)" [110591-111128] -->
3260 <h3 class="sectionedit982"><a name="toggle_visibility_tt" id="toggle_visibility_tt">Toggle Visibility (tt)</a></h3>
3261 <div class="level3">
3262
3263 <p>
3264 This operation allows you to toggle the visibility of attributes.<br/>
3265
3266 To use this option:
3267 </p>
3268 <ol>
3269 <li class="level1"><div class="li"> Select the text item(s) of interest</div>
3270 </li>
3271 <li class="level1"><div class="li"> Pick or type the shortcut for Attributes/Toggle Vis</div>
3272 </li>
3273 </ol>
3274
3275 <p>
3276
3277 The text item(s) should change their visibility immediately.<br/>
3278
3279 If you make an attached attribute invisible, then you can simply select the parent object and select Toggle Vis and the attribute will be come visible (likewise any visible attributes attached to that object will become invisible).<br/>
3280
3281 If you make a free floating (unattached) attribute invisible, then the only way to make it visible (and all other invisible attributes) is to use the Edit/Show Hidden Text option.
3282 </p>
3283
3284 </div>
3285 <!-- EDIT982 SECTION "Toggle Visibility (tt)" [111129-111824] -->
3286 <h3 class="sectionedit983"><a name="find_specific_text_t_shift-f" id="find_specific_text_t_shift-f">Find Specific Text... (t shift-f)</a></h3>
3287 <div class="level3">
3288
3289 </div>
3290 <!-- EDIT983 SECTION "Find Specific Text... (t shift-f)" [111825-111869] -->
3291 <h3 class="sectionedit984"><a name="hide_specific_text_th" id="hide_specific_text_th">Hide Specific Text... (th)</a></h3>
3292 <div class="level3">
3293
3294 </div>
3295 <!-- EDIT984 SECTION "Hide Specific Text... (th)" [111870-111907] -->
3296 <h3 class="sectionedit985"><a name="show_specific_text_t_shift-h" id="show_specific_text_t_shift-h">Show Specific Text... (t shift-h)</a></h3>
3297 <div class="level3">
3298
3299 </div>
3300 <!-- EDIT985 SECTION "Show Specific Text... (t shift-h)" [111908-111951] -->
3301 <h3 class="sectionedit986"><a name="autonumber_text_tu" id="autonumber_text_tu">Autonumber Text... (tu)</a></h3>
3302 <div class="level3">
3303
3304 </div>
3305 <!-- EDIT986 SECTION "Autonumber Text... (tu)" [111952-111986] -->
3306 <h2 class="sectionedit987"><a name="options" id="options">Options</a></h2>
3307 <div class="level2">
3308
3309 </div>
3310 <!-- EDIT987 SECTION "Options" [111987-112007] -->
3311 <h3 class="sectionedit988"><a name="text_size_ot" id="text_size_ot">Text Size... (ot)</a></h3>
3312 <div class="level3">
3313
3314 <p>
3315 <strong>Options | Text Size…</strong> pops up a dialog box which allows you to specify the text size of all text (including attributes placed with the Add/Attribute… dialog box).<br/>
3316
3317 The text size is in points (1/72”). The default text size is 10 point text. The smallest text size is 2 points.
3318 </p>
3319
3320 </div>
3321 <!-- EDIT988 SECTION "Text Size... (ot)" [112008-112320] -->
3322 <h3 class="sectionedit989"><a name="toggle_grid_on_off_og" id="toggle_grid_on_off_og">Toggle Grid On/Off (og)</a></h3>
3323 <div class="level3">
3324
3325 <p>
3326 <strong>Options | Toggle Grid On/Off</strong> toggles the visible grid.
3327 </p>
3328
3329 </div>
3330 <!-- EDIT989 SECTION "Toggle Grid On/Off (og)" [112321-112414] -->
3331 <h3 class="sectionedit990"><a name="toggle_snap_on_off_os" id="toggle_snap_on_off_os">Toggle Snap On/Off (os)</a></h3>
3332 <div class="level3">
3333
3334 <p>
3335 <strong>Options | Toggle Snap On/Off</strong> toggles the snap. Be very careful using this. Connections between pins and nets (and nets to nets) depends on being exactly connected. Turning of the grid will almost guarantee that nets/pins do not connect.<br/>
3336
3337 Before you translate a symbol using Edit/Symbol Translate, make sure the snap is on.<br/>
3338
3339 When snap mode is off, the text “Snap Off” will appear in the lower, righthand corner.
3340 </p>
3341
3342 </div>
3343 <!-- EDIT990 SECTION "Toggle Snap On/Off (os)" [112415-112866] -->
3344 <h3 class="sectionedit991"><a name="snap_grid_spacing_os" id="snap_grid_spacing_os">Snap Grid Spacing... (oS)</a></h3>
3345 <div class="level3">
3346
3347 <p>
3348 <strong>Options | Snap Grid Spacing…</strong> brings up a dialog box which allows you to change the snap grid spacing (not the grid spacing). The units for this spacing are mils.<br/>
3349
3350 Before you translate a symbol using Edit/Symbol Translate, make sure this spacing is set to 100.
3351 </p>
3352
3353 </div>
3354 <!-- EDIT991 SECTION "Snap Grid Spacing... (oS)" [112867-113170] -->
3355 <h3 class="sectionedit992"><a name="toggle_outline_box_oa" id="toggle_outline_box_oa">Toggle Outline/Box (oa)</a></h3>
3356 <div class="level3">
3357
3358 <p>
3359 <strong>Options | Toggle Outline/Box</strong> toggles between drawing the outline of the current selection or just drawing a box when doing moves/copies/component and text places. The outline mode looks better, but tends to be significantly slower than using the box (bounding box) mode.
3360 </p>
3361
3362 </div>
3363 <!-- EDIT992 SECTION "Toggle Outline/Box (oa)" [113171-113480] -->
3364 <h3 class="sectionedit993"><a name="toggle_net_rubberband_or" id="toggle_net_rubberband_or">Toggle Net/Rubberband (or)</a></h3>
3365 <div class="level3">
3366
3367 <p>
3368 <strong>Options | Toggle Net/Rubberband</strong> …..????
3369 </p>
3370
3371 </div>
3372 <!-- EDIT993 SECTION "Toggle Net/Rubberband (or)" [113481-113564] -->
3373 <h3 class="sectionedit994"><a name="show_log_window_ol" id="show_log_window_ol">Show Log Window (ol)</a></h3>
3374 <div class="level3">
3375
3376 <p>
3377 <strong>Options | Show Log Window</strong> displays the log window if it has been closed or disabled from being displayed when you start up <strong>gschem</strong>.
3378 </p>
3379
3380 </div>
3381 <!-- EDIT994 SECTION "Show Log Window (ol)" [113565-113735] -->
3382 <h3 class="sectionedit995"><a name="show_coord_window_oc" id="show_coord_window_oc">Show Coord Window... (oc)</a></h3>
3383 <div class="level3">
3384
3385 <p>
3386 <strong>Options | Show Coord Window…</strong> displays a pop-up window that displays the coordinates of the mouse pointer on the schematic. Useful for accurately placing objects.
3387 </p>
3388
3389 </div>
3390 <!-- EDIT995 SECTION "Show Coord Window... (oc)" [113736-113940] -->
3391 <h2 class="sectionedit996"><a name="help" id="help">Help</a></h2>
3392 <div class="level2">
3393
3394 </div>
3395 <!-- EDIT996 SECTION "Help" [113941-113958] -->
3396 <h3 class="sectionedit997"><a name="about_ha" id="about_ha">About... (ha)</a></h3>
3397 <div class="level3">
3398
3399 <p>
3400 Every <acronym title="Graphical User Interface">GUI</acronym> application needs an <strong>Help | About…</strong> feature, to display:
3401 </p>
3402 <ul>
3403 <li class="level1"><div class="li"> The application&#039;s name.</div>
3404 </li>
3405 <li class="level1"><div class="li"> The version of the software.</div>
3406 </li>
3407 <li class="level1"><div class="li"> The author&#039;s name(s) and how to contact.</div>
3408 </li>
3409 </ul>
3410
3411 </div>
3412 <!-- EDIT997 SECTION "About... (ha)" [113959-114161] -->
3413 <h3 class="sectionedit998"><a name="manual_hm" id="manual_hm">Manual... (hm)</a></h3>
3414 <div class="level3">
3415
3416 <p>
3417 <strong>Help | Manual…</strong> brings up the “gEDA/gaf Documention” web-page installed on this computer. Very useful for accessing the various documentation available for the gEDA/gaf applications.
3418 </p>
3419
3420 </div>
3421 <!-- EDIT998 SECTION "Manual... (hm)" [114162-114375] -->
3422 <h3 class="sectionedit999"><a name="hotkeys_hh" id="hotkeys_hh">Hotkeys... (hh)</a></h3>
3423 <div class="level3">
3424
3425 <p>
3426 <strong>Help | Hotkeys…</strong> lists the current hotkeys (a.k.a., shortcuts, a.k.a., keyboard accellerators).
3427 </p>
3428
3429 </div>
3430 <!-- EDIT999 SECTION "Hotkeys... (hh)" [114376-114503] -->
3431 <h3 class="sectionedit1000"><a name="component_ho" id="component_ho">Component... (Ho)</a></h3>
3432 <div class="level3">
3433
3434 <p>
3435 If you select a component on the schematic, and select <strong>Help | Component…</strong>, <strong>gschem</strong> uses the gschemdoc script to do its best job finding some documentation appropriate for the component:
3436 </p>
3437 <ul>
3438 <li class="level1"><div class="li"> If the component&#039;s symbol included the <code>documentation=documentation_locator</code> attribute, this <acronym title="Uniform Resource Identifier">URI</acronym> is used to retreive the documentation. If the full <acronym title="Uniform Resource Identifier">URI</acronym> is given, the <acronym title="Uniform Resource Identifier">URI</acronym> on the internet is retrieved. If the <acronym title="Uniform Resource Identifier">URI</acronym> is not fully qualified, it is considered to be local to this computer, and is searched for and displayed.</div>
3439 </li>
3440 <li class="level1"><div class="li"> If the component&#039;s symbol does not include the <code>documentation=documentation_locator</code> attribute, a Google search is performed for <acronym title="Portable Document Format">PDF</acronym> documents, based on the <code>device=</code> attribute, the <code>value=</code> attribute, and the symbol basename.</div>
3441 </li>
3442 </ul>
3443
3444 </div>
3445 <!-- EDIT1000 SECTION "Component... (Ho)" [114504-115286] -->
3446 <h1 class="sectionedit1001"><a name="appendix_a_--_heavy_vs_light_symbol_libraries" id="appendix_a_--_heavy_vs_light_symbol_libraries">Appendix A -- Heavy vs Light Symbol Libraries</a></h1>
3447 <div class="level1">
3448
3449 <p>
3450 A short discussion of Light Symbol Libraries as the default for <strong>gschem</strong>, and the option to build your own Heavy Symbol Libraries.
3451 </p>
3452
3453 </div>
3454 <!-- EDIT1001 SECTION "Appendix A -- Heavy vs Light Symbol Libraries" [115287-115480] -->
3455 <h1 class="sectionedit1002"><a name="appendix_b_--_printing_schematics_and_symbols" id="appendix_b_--_printing_schematics_and_symbols">Appendix B -- Printing Schematics and Symbols</a></h1>
3456 <div class="level1">
3457
3458 <p>
3459 To be supplied…
3460 </p>
3461
3462 </div>
3463 <!-- EDIT1002 SECTION "Appendix B -- Printing Schematics and Symbols" [115481-115559] -->
3464 <h1 class="sectionedit1003"><a name="appendix_c_--_writing_guile_scripts" id="appendix_c_--_writing_guile_scripts">Appendix C -- Writing guile Scripts</a></h1>
3465 <div class="level1">
3466
3467 <p>
3468 To be supplied…
3469 </p>
3470
3471 </div>
3472 <!-- EDIT1003 SECTION "Appendix C -- Writing guile Scripts" [115560-115628] -->
3473 <h1 class="sectionedit1004"><a name="appendix_d_--_i_want_to_build_a_printed_circuit_board" id="appendix_d_--_i_want_to_build_a_printed_circuit_board">Appendix D -- I Want To Build A Printed Circuit Board</a></h1>
3474 <div class="level1">
3475
3476 <p>
3477 <strong>gschem</strong> is used for two primary design workflows:
3478 </p>
3479 <ul>
3480 <li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards (PCBs).</div>
3481 </li>
3482 <li class="level1"><div class="li"> Circuit design intended for simulation.</div>
3483 </li>
3484 </ul>
3485
3486 <p>
3487
3488 The following guidelines will assist you in developing quality designs intended for use by applications that support the creation of Printed Circuit Boards:
3489 </p>
3490 <ul>
3491 <li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
3492 </li>
3493 </ul>
3494
3495 <p>
3496
3497 The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a PCB:
3498 </p>
3499 <ul>
3500 <li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html" class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/gschem-warmup.html"  rel="nofollow">Bill Wilson&#039;s gschem warmup</a></div>
3501 </li>
3502 <li class="level1"><div class="li"> <a href="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html" class="urlextern" title="http://www.geda.seul.org/docs/current/tutorials/gsch2pcb/tutorial.html"  rel="nofollow">Bill Wilson&#039;s gsch2pcb tutorial</a></div>
3503 </li>
3504 </ul>
3505
3506 </div>
3507 <!-- EDIT1004 SECTION "Appendix D -- I Want To Build A Printed Circuit Board" [115629-116418] -->
3508 <h1 class="sectionedit1005"><a name="appendix_e_--_i_want_to_simulate_my_design" id="appendix_e_--_i_want_to_simulate_my_design">Appendix E -- I Want To Simulate My Design</a></h1>
3509 <div class="level1">
3510
3511 <p>
3512 <strong>gschem</strong> is used for two primary design workflows:
3513 </p>
3514 <ul>
3515 <li class="level1"><div class="li"> Circuit design intended for production of Printed Circuit Boards.</div>
3516 </li>
3517 <li class="level1"><div class="li"> Circuit design intended for simulation.</div>
3518 </li>
3519 </ul>
3520
3521 <p>
3522
3523 The following guidelines will assist you in developing quality designs intended for simulation:
3524 </p>
3525 <ul>
3526 <li class="level1"><div class="li"> Discuss attributes appropriate for a SPICE model, and how these differ from attributes appropriate for a PCB.</div>
3527 </li>
3528 <li class="level1"><div class="li"> <span class="hilited">To be supplied…</span></div>
3529 </li>
3530 </ul>
3531
3532 <p>
3533
3534 The following on-line tutorials are an excellent method for the beginner to learn the gEDA Tools Suite design workflow resulting in a SPICE simulation:
3535 </p>
3536 <ul>
3537 <li class="level1"><div class="li"> <a href="http://www.brorson.com/gEDA/SPICE/t1.html" class="urlextern" title="http://www.brorson.com/gEDA/SPICE/t1.html"  rel="nofollow">&quot;Circuit simulation using gEDA and SPICE -- HOWTO&quot; by Stuart Brorson</a></div>
3538 </li>
3539 <li class="level1"><div class="li"> <a href="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf" class="urlextern" title="http://www-mdp.eng.cam.ac.uk/urop05/files/gedalib/starting_gEDA.pdf"  rel="nofollow">Starting with gEDA at the Cambridge University Engineering Department</a></div>
3540 </li>
3541 </ul>
3542
3543 </div>
3544 <!-- EDIT1005 SECTION "Appendix E -- I Want To Simulate My Design" [116419-117298] -->
3545 <h1 class="sectionedit1006"><a name="appendix_f_--_change_gschemdoc_user-defined_preferences" id="appendix_f_--_change_gschemdoc_user-defined_preferences">Appendix F -- Change gschemdoc User-Defined Preferences</a></h1>
3546 <div class="level1">
3547
3548 <p>
3549 As installed, the <strong>gschemdoc</strong> utility script is used by <strong>gschem</strong> to:
3550 </p>
3551 <ul>
3552 <li class="level1"><div class="li"> Display the “gEDA/gaf Documentation” (i.e., <strong>Help | Manual…</strong>)</div>
3553 </li>
3554 <li class="level1"><div class="li"> Display component documentation (i.e., <strong>Help | Component…</strong>)</div>
3555 </li>
3556 </ul>
3557
3558 <p>
3559
3560 The list of application launchers that <strong>gschemdoc</strong> uses are defined in the {binary-install-path}/bin/gschemdoc file:
3561 <pre STYLE="background : LightGreen;
3562 margin-left : 2em"><font size="+0">#
3563 # these may be changed to suit local preferences
3564 #
3565 CANDIDATE_BROWSER=&quot;galeon mozilla phoenix netscape netscape-navigator opera firefox konqueror&quot;
3566 CANDIDATE_PDFREADER=&quot;xpdf acroread ggv gv&quot;
3567 CANDIDATE_LOCATE=&quot;slocate locate&quot;</font></pre>
3568 </p>
3569
3570 <p>
3571 To select a different application launcher, simply edit the {binary-install-path}/bin/gschemdoc file, find the above lines, and move your favorite application to the beginning of the list. For example, to use <strong>firefox</strong> as your preferred browser, move it to the beginning of the <strong>CANDIDATE_BROWSER=</strong> list, to use <strong>acroread</strong> (Adobe&#039;s Acrobat Reader) as your preferred <acronym title="Portable Document Format">PDF</acronym> reader, move it to the beginning of the <strong>CANDIDATE_PDFREADER=</strong> list, and to use <strong>locate</strong> as your preferred filesystem search utility, move it to the beginning of the <strong>CANDIDATE_LOCATE=</strong> list.
3572 </p>
3573
3574 </div>
3575 <!-- EDIT1006 SECTION "Appendix F -- Change gschemdoc User-Defined Preferences" [117299-118515] -->
3576 <h1 class="sectionedit1007"><a name="appendix_g_--_breaking_a_large_symbol_into_smaller_symbols" id="appendix_g_--_breaking_a_large_symbol_into_smaller_symbols">Appendix G -- Breaking a Large Symbol Into Smaller Symbols</a></h1>
3577 <div class="level1">
3578
3579 <p>
3580 To be supplied…
3581 </p>
3582
3583 </div>
3584 <!-- EDIT1007 SECTION "Appendix G -- Breaking a Large Symbol Into Smaller Symbols" [118516-118607] -->
3585 <h1 class="sectionedit1008"><a name="appendix_h_--_definition_of_terms" id="appendix_h_--_definition_of_terms">Appendix H -- Definition of Terms</a></h1>
3586 <div class="level1">
3587
3588 <p>
3589 Some terms used in the art of schematic capture:</p>
3590 <dl>
3591 <dt><span class='term'> <strong>attribute</strong></span></dt>
3592 <dd>A text item which is in the form <code>name=value</code>. It can be either unattached or attached.</dd>
3593 <dt><span class='term'> <strong>buffer</strong></span></dt>
3594 <dd>…</dd>
3595 <dt><span class='term'> <strong>component</strong></span></dt>
3596 <dd>Also know as <strong>part</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board. Components are instances of a <strong>symbol</strong> placed on a schematic.</dd>
3597 <dt><span class='term'> <strong>device</strong></span></dt>
3598 <dd>Also known as “package”. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
3599 <dt><span class='term'> <strong>dialog box</strong></span></dt>
3600 <dd>…</dd>
3601 <dt><span class='term'> <strong>embedded component</strong></span></dt>
3602 <dd>A component whose definition is saved as part of the schematic&#039;s file.</dd>
3603 <dt><span class='term'> <strong>footprint</strong></span></dt>
3604 <dd>Also known as a <strong>land pattern</strong>. The surface space occupied by a <strong>component</strong>/<strong>package</strong>/<strong>part</strong>.</dd>
3605 <dt><span class='term'> <strong>gEDA/gaf</strong></span></dt>
3606 <dd><strong>gschem</strong> is a component of the gEDA/gaf set of tools, which tend to integrate together in the development and maintenance of schematics and symbols. The term “gaf” stands for “<em class="u">g</em>EDA <em class="u">a</em>nd <em class="u">f</em>riends”).</dd>
3607 <dt><span class='term'> <strong>grip</strong></span></dt>
3608 <dd>…</dd>
3609 <dt><span class='term'> <strong>guile</strong></span></dt>
3610 <dd><a href="http://www.gnu.org/software/guile/" class="urlextern" title="http://www.gnu.org/software/guile/"  rel="nofollow">GNU Guile</a> is an interpreter for Scheme, a version of Lisp.</dd>
3611 <dt><span class='term'> <strong>HDL</strong></span></dt>
3612 <dd>Hardware Description Language (e.g., VHDL, Verilog, etc.). Used to simulate or document a device.</dd>
3613 <dt><span class='term'> <strong>hierarchical</strong></span></dt>
3614 <dd>The concept that designs can contain nested levels of schematics, so that all the circuit doesn&#039;t need to be placed on a single sheet.</dd>
3615 <dt><span class='term'> <strong>land pattern</strong></span></dt>
3616 <dd>Also known as a <strong>footprint</strong>. The surface space occupied by a structure or device.</dd>
3617 <dt><span class='term'> <strong>library</strong></span></dt>
3618 <dd>A collection of symbols.</dd>
3619 <dt><span class='term'> <strong>line</strong></span></dt>
3620 <dd>A straight drawing element, connecting two points. On the schematic it has no electrical significance. In a symbol, a line is part of the symbol&#039;s graphic elements.</dd>
3621 <dt><span class='term'> <strong>model</strong></span></dt>
3622 <dd>A description of how a device behaves. Most often this is a SPICE model. The model is defined in <strong>gschem</strong>, but used in subsequent applications such as <strong>ngspice</strong>, <strong>gnucap</strong>, etc.</dd>
3623 <dt><span class='term'> <strong>net</strong></span></dt>
3624 <dd>A net connects two or more pins on a schematic, and is made up of segments. The net&#039;s equivalent is a “wire” or “trace” on the printed circuit board.</dd>
3625 <dt><span class='term'> <strong>object</strong></span></dt>
3626 <dd>A line, circle, pin, net, box, bus, text/attribute, or picture.</dd>
3627 <dt><span class='term'> <strong>package</strong></span></dt>
3628 <dd>Also known as <strong>device</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
3629 <dt><span class='term'> <strong>page</strong></span></dt>
3630 <dd>Also known as a schematic&#039;s <strong>sheet</strong>.</dd>
3631 <dt><span class='term'> <strong>part</strong></span></dt>
3632 <dd> Also know as <strong>component</strong>. The equivalent of an [electronics] device, as one may place on a printed circuit board.</dd>
3633 <dt><span class='term'> <strong>project</strong></span></dt>
3634 <dd>A collection of schematics, custom symbols, models, documentation, etc.</dd>
3635 <dt><span class='term'> <strong>segment</strong></span></dt>
3636 <dd>Part of a net. A segment has two end-points, or “grips”.</dd>
3637 <dt><span class='term'> <strong>schematic</strong></span></dt>
3638 <dd>A <strong>page</strong>/<strong>sheet</strong> with electronics symbols, text, and drawing elements (i.e., lines, circles, boxes, etc.) representing a diagram of an electrical or mechanical system.</dd>
3639 <dt><span class='term'> <strong>series</strong></span></dt>
3640 <dd>A collection of schematics which share a common basename (e.g., schematic_1.sch, schematic_2.sch, schematic_3.sch, etc.). The series basename ties schematics together.</dd>
3641 <dt><span class='term'> <strong>slotted device</strong></span></dt>
3642 <dd>Also known as a <strong>slotted package</strong>. A physical [electronics] device consisting of multiple identical components (e.g., the 7400 quad NAND device consists of 4 identical NAND gates).</dd>
3643 <dt><span class='term'> <strong>source</strong></span></dt>
3644 <dd>A schematic, HDL code, or model which implements, describes, or documents some aspect of the project.</dd>
3645 <dt><span class='term'> <strong>symbol</strong></span></dt>
3646 <dd>A collection of <strong>objects</strong>. The objects may have <strong>attributes</strong> attatched (i.e., associated) with them. There may also be <strong>attributes</strong> attached (i.e., associated) to the <strong>symbol</strong> itself (i.e., not specifically associated with an object).</dd>
3647 <dt><span class='term'> <strong>sheet</strong></span></dt>
3648 <dd>Also known as a schematic&#039;s <strong>page</strong>.</dd>
3649 <dt><span class='term'> <strong>trace</strong></span></dt>
3650 <dd>The equivalent of a wire on a printed circuit board.</dd>
3651 <dt><span class='term'> <strong>window</strong></span></dt>
3652 <dd>…</dd>
3653 <dt><span class='term'> <strong>workflow</strong></span></dt>
3654 <dd>The process of designing. Usually includes continuous review and re-design, until it works. In the gEDA Tools Suite design workflow, multiple applications are used. One application typically is followed by another. The flow of data collected and how this data effects the design is considered the workflow.</dd>
3655 </dl>
3656 <p>~~DISCUSSION~~
3657
3658 </p>
3659
3660 </div>
3661 <!-- EDIT1008 SECTION "Appendix H -- Definition of Terms" [118608-] --></body>
3662 </html>