>--- Abd ulRahman Lomax <[EMAIL PROTECTED]> wrote:
> If you are using Net Labels and Ports Global scope,
> you must place a net 
> label to force the assignment of a net name. With
> this scope, you don't 
> need to use ports at all....

I don't?  Great!  But then how do I generate the
little strings next to the net labels that tell me
what page and grid reference the net goes to?

I'll tell you how I've done it in the past -- by hand!
 It's time consuming and error prone, but necessary. 
My schematics are typically about 10 pages or so so I
need an aid to help me find the other end of the wire.
 (When I'm debugging in the field, I'm using paper
copies.)

Ports allow me to automate the process but with two
distinct disadvantages over my tedious manual method:

1. It seems impossible to generate references within
the same page automatically (without 3rd party tools).

2. The automatically generated references sometimes
appear on the wrong side of the port so that the text
is placed directly over a wire.  Sometimes I can fix
this; sometimes I can't.

Anybody have any clever ways they handle generating
net cross references?  I've seen schematics (not drawn
in Protel) that include tables at the end with this
kind of information.  Although, in my opinion, that's
not quite as convenient as having the information
embedded on every page, if I could generate that kind
of table automatically I'd adopt that method in a
second.

Thanks!
Matt

__________________________________________________
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* To post a message: mailto:[EMAIL PROTECTED]
*
* To leave this list visit:
* http://www.techservinc.com/protelusers/leave.html
*
* Contact the list manager:
* mailto:[EMAIL PROTECTED]
*
* Forum Guidelines Rules:
* http://www.techservinc.com/protelusers/forumrules.html
*
* Browse or Search previous postings:
* http://www.mail-archive.com/proteledaforum@techservinc.com
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to