Is there any reason to have a designator for any type of passive item (nut, 
washer, mousebites etc)? If not, then couldn't an item of this type be 
designator free and therefore not subject to the netlisting interface...

Doug

> >'delete components not in netlist'
> >would be a lot more useful if there was a way wo make exceptions, like
> >maybe don't delete them if they are locked or selected or had a special
> >property for that purpose
> >
> >else you have to put a bunch of mounting holes and mouse bites and such
> >in the schematic which makes a bunch of clutter and work
> >
> >Dennis Saputelli
>
>Yes, Dennis, I agree. I have been asking for a NO_UPDATE attribute for 
>components for some time. I do not like putting mounting holes on the Sch 
>so I usually place mounting holes etc as components from my library (which 
>include washer and nut clearances etc) and then explode to free primitives 
>to save removing the component delete macros that keep trying to delete my 
>mounting holes.  I would prefer a component attribute that prevented the 
>synch updating anything on that component - I think it should be 
>(optionally, maybe) listed in the Preview Changes dialog as a change that 
>is blocked by the NO_UPDATE  attribute to allow us to see possible 
>unintended consequences of the NO_UPDATE attribute.
>
>I think the attribute should be available to both Sch and PCB components.
>
>Ian Wilson


_________________________________________________________________
Join the world s largest e-mail service with MSN Hotmail. 
http://www.hotmail.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