That would help him if he were using DXP, but since he is using P99SE his 
only choice is to use the hole size editor and manually check that the 
holes are in his list.

So you can make a rule to limit your holes to a list in DXP but not in 
P99SE.

Robert D. LaMoreaux
MTS Systems Corp. 
Powertrain Technology Division
4622 Runway Blvd.
Ann Arbor, MI 48108
734-822-9696
Fax 734-973-1103
Main Desk 734-973-1111




"Wojciech Oborski" <[EMAIL PROTECTED]>
02/24/2003 10:06 AM
Please respond to "Protel EDA Forum"

 
        To:     "Protel EDA Forum" <[EMAIL PROTECTED]>
        cc: 
        Subject:        Re: [PEDA] Hole Size Constraint


I know this is not exactly what is expected, but maybe it can be
considered as a workaround:

1. Specify (using query manager) a selection query looking like:
    select all pad.hole size which are not equal to 28 and
    select all pad.hole size which are not equal to 32 and
    select all pad.hole size which are not equal to 40 and
    select all via.hole size which are not equal to 24 and
    select all via.hole size which are not equal to 28
    - if there are any SMD components, then add:
    select all pad.hole size which are not equal to 0
2. Hit Apply - as a result one gets selected pads and vias
    not meeting desired "rule"

Pads and vias may be processed separately - 2 different queries
would be needed.

Having all pads (and/or vias) not meeting the "rule" selected
(instead of listed in DRC report) may be a benefit - one may use
it to globally edit them or even easily create pad class for them.

Wojciech Oborski







* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* 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/[EMAIL PROTECTED]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Reply via email to