Actions
Forum Thread Details
  • Replies 13 replies
  • Subscribers 180 subscribers
  • Views 1351 views
  • Users 0 members are here
Related

Pads

autodeskguest

Hi again,

Sorry for the newbie question but I'm really at my wit's end.

I would like to change the diameter of the pads to the passive components on

the already routed board image but the CHANGE command won't let me, even if

the Pads layer is active. All I get is a rude noise, even while the status

bar tells me to left-click on the component I want to change.

Also, it would make my life a lot easier if I could duplicate a section of

the board elsewhere on the same board without having to do it in the

schematic editor. Imagine 2 channels of a stereo system placed side by side

with interconnecting circuitry routed manually. This would look neater, not

to mention making trouble-shooting a lot easier on the actual physical

hardware.

Any help would be gratefully appreciated.

Thanks,

Martin

 

 

 

 

Parents

  • On 10/21/2009 9:35 AM, Rob wrote:

    Travis,

    What you are "learning" is how to work around limitations. . You could just

    as easily be learning how to reduce a single pad.  All programs have

    limitations and little anomolies.

     

     

    While I will admit to what Andrew said, I otherwise disagree with your

    point of view here. Learning to edit the lib taught me, at a very early

    stage, that I needed to build my own libs and organize the parts I use

    so my workflow will be optimal. It takes me MUCH less time to generate a

    board and order parts for a production assembly run now that I have my

    own libs with my own often-used parts.

     

    The option to change pads in the board, I'll grant, could be useful in

    particular cases where you only need 1 or 2 pads changed, and only for

    that board. But I wouldn't want the program to allow it without warning

    users they should edit the library if it's a change they may want for

    other boards.

     

    So I'd agree to the change, but only if, on a per-board basis, you had

    to agree to a messagebox that told you something similar to:

    "You are about to edit a part's package. This should be done by editing

    the package in the Library, unless this is a change that is specific to

    this board layout and you will never need again. Otherwise, please

    proceed to the library editor to edit this package. Do you still want to

    edit the package?"

     

    Travis

     

Reply

  • On 10/21/2009 9:35 AM, Rob wrote:

    Travis,

    What you are "learning" is how to work around limitations. . You could just

    as easily be learning how to reduce a single pad.  All programs have

    limitations and little anomolies.

     

     

    While I will admit to what Andrew said, I otherwise disagree with your

    point of view here. Learning to edit the lib taught me, at a very early

    stage, that I needed to build my own libs and organize the parts I use

    so my workflow will be optimal. It takes me MUCH less time to generate a

    board and order parts for a production assembly run now that I have my

    own libs with my own often-used parts.

     

    The option to change pads in the board, I'll grant, could be useful in

    particular cases where you only need 1 or 2 pads changed, and only for

    that board. But I wouldn't want the program to allow it without warning

    users they should edit the library if it's a change they may want for

    other boards.

     

    So I'd agree to the change, but only if, on a per-board basis, you had

    to agree to a messagebox that told you something similar to:

    "You are about to edit a part's package. This should be done by editing

    the package in the Library, unless this is a change that is specific to

    this board layout and you will never need again. Otherwise, please

    proceed to the library editor to edit this package. Do you still want to

    edit the package?"

     

    Travis

     

Children
No Data