[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

gEDA-user: hierarchy and refdes_renum



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I'm just trying around with hierarchy. This is my first hierarchy
design, and some questions remained open. I used the gTAG example as a
starting point.

What symbols do you use to 'declare' the pins in the subcircuit? I used
the in-1.sym and out-1.sym, but using the refdes for the pin identifier
looks like a hack to me. Is the used of these two symbols still state of
the art or are there better ways to follow?
So when renumbering the parts in the file, refdes_renum attaches a 1
suffix to all the refdes attributes of the in-1 and out-1 symbols on the
sheet, which is just a mess. Some Perl warnings pop up on the command
line, BTW.

What can I do to fix it?

I run the outdated gEDA suite 1.4.0, but I md5-verified that in-1.sym,
out-1.sym and refdes_renum are the same in the newest 1.4.3 release.

CU
- - Christoph
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKPK5TWo2QgtqY4K8RAti1AJ0RMEC0h2rsUvEKnXhVL+ebRrZtMgCggxiP
OZN6KKI5RRXeZz9sXfMpPKM=
=4tCj
-----END PGP SIGNATURE-----


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user