X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=PlvAefZcWZtyWd2+ngBQz5r6EzhS5ad3nb78wzOS1GQ=; b=qqXSaJOslZ9Q0mVAn2LoONe9OZC701IwJd8N+NvPoRclRgB5RQ9+iZoCXr42BZJebS Os8eS64L9yAacrwYDtJtqi3SrlsAkLbie3LLozcXSz6D2ebGMDW1oNOzUmcBVZOzRlE7 5mRd/4myMan8VVFsc3CgQAgRXEgE9voLXEkQ6D+W65Yr0pRh6BJCXdjjfK2zxHKEh+Pq ZN9iFSmBZotcrPiAfN8DlgK3RtewjyvdHugGfZm4gnL2MXPkzXnE7zqwc0sH2GwLKIhp 2r0+X0HQjkBVR4McQ1z4KyVtKq1AQYjV05DpPf3NQkgno51rM7qJjRPrUQM+LnJKXBk+ UobQ== MIME-Version: 1.0 X-Received: by 10.50.143.12 with SMTP id sa12mr900693igb.64.1440489345674; Tue, 25 Aug 2015 00:55:45 -0700 (PDT) In-Reply-To: <1508250606.AA24247@ivan.Harhan.ORG> References: <1508250606 DOT AA24247 AT ivan DOT Harhan DOT ORG> Date: Tue, 25 Aug 2015 09:55:45 +0200 Message-ID: Subject: Re: [geda-user] pcb file format (functions to walk thru by different properties) From: "Levente (leventelist AT gmail DOT com) [via geda-user AT delorie DOT com]" To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=001a1134cd02c082f9051e1e0f92 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --001a1134cd02c082f9051e1e0f92 Content-Type: text/plain; charset=UTF-8 You can define a padstacks, that can be reused. You can define sub-pcbs, and reuse. You can define multiple component, and add the same sub-pcb to them. Lev On Tue, Aug 25, 2015 at 8:06 AM, Spacefalcon the Outlaw < falcon AT ivan DOT harhan DOT org> wrote: > DJ Delorie wrote: > > > Another thing which might be useful is to store each footprint *once* > > and refer to it for each element, > > That's what PADS does. > > > but that means you'd need a way to > > override individual parts of the footprint for each element, too. > > AFAICT PADS does not provide any such "override" mechanism; one has to > create two different "part decals" (PADS term for footprint) with > different names if any changes to the content of the "part decal" are > desired. > > SF > --001a1134cd02c082f9051e1e0f92 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
You can define a padstacks, that can be reused. You c= an define sub-pcbs, and reuse. You can define multiple component, and add t= he same sub-pcb to them.

Lev

On Tue, Aug 25, 2015 at 8:06 AM, Spacefal= con the Outlaw <falcon AT ivan DOT harhan DOT org> wrote:
DJ Delorie <dj AT delorie DOT com> wrote:

> Another thing which might be useful is to store each footprint *once*<= br> > and refer to it for each element,

That's what PADS does.

> but that means you'd need a way to
> override individual parts of the footprint for each element, too.

AFAICT PADS does not provide any such "override" mechanism= ; one has to
create two different "part decals" (PADS term for footprint) with=
different names if any changes to the content of the "part decal"= are
desired.

SF

--001a1134cd02c082f9051e1e0f92--