room for ambiguity.
sheet 2 as a subset of a higher level sheet 2 would become 22R21 sheet 22 could have a an R21 so another component becomes 22R21 Steve Meier On Fri, 2008-06-20 at 15:41 +0000, Kai-Martin Knaak wrote: > On Tue, 17 Jun 2008 05:29:20 -0400, gene wrote: > > > I just need to figure out how to handle the silkscreen. There's a > > thread on this subject somewhere that I ran across while googling last > > night. > > There is a couple of hierarchy related settings in system-gnetlistrc. You > can set them to values other than the default in $HOME/.gEDA/gnetlistrc . > Currently, mine looks like this: > > (hierarchy-traversal "enabled") > (hierarchy-uref-mangle "enabled") > (hierarchy-uref-separator "") > (hierarchy-netname-mangle "enabled") > (hierarchy-netname-separator "") > (hierarchy-netattrib-mangle "disabled") > (hierarchy-netattrib-separator "/") > (unnamed-netname "noname") > > I set the uref seperator to an empty string. For minimum kludge of > component names I set the uref of hierarchy symbols to pure, single > digits. That way the uref of a component R21 from a sub sheet number 2 > translates to "2R21". > > ---<(kaimartin)>---- _______________________________________________ geda-user mailing list geda-user@moria.seul.org http://www.seul.org/cgi-bin/mailman/listinfo/geda-user