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=20230601; t=1714667050; x=1715271850; darn=delorie.com; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=nU10eEhVgKQ4lxfQo54FRx73NBVnbhvghRwkCl7smeM=; b=E/P+aE6kTlRSuDeuxuwQ2xwL8/j+/M6KvM2ICZlLPgLYfygajZDSpoiJquSW876420 FrApVn55oiRWOYJr38IomtxyGZGBstr2NlxiyYRLCaL2W8pT8llNLDJDWm50RVfeXsef z/ARaf6QiOzFMbiLXppM3w7rEmy6yejoxoy1lmmmxPyGnIuMBnYE2rCFzrWAYp9p9rmO Q6AZRMF9JM/45+IDeDy8/hRWIehg/s/HawRFBihTZbFAeUZddKaMfRUPbyKKvDgzlBwD o/l18J92bK3hlq/T3cJprONy54a/rXv1i0j/b7ryzr/bnHxo+nkfI92RdOtxvpK4T84T 8zDw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714667050; x=1715271850; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nU10eEhVgKQ4lxfQo54FRx73NBVnbhvghRwkCl7smeM=; b=SfddULunBhfAeLhnBeogd83OXmapbA/+DyVBPr/t7okvPdW5te/3o52ad0fJhCxqT4 lKXKPB4T7/oc0fVkSQZbsW3Z2Cg5VG4xzNLvPUjf+rzYINvV6UJKbEA4j3NtsBN3sCbq 6ewv2n4hJZ4G0/oVU0Qv3HN2BS5OR8ZBjLzP4xS/DUBsQ+gcO8i3G8+FNsNDP039WJxA FaRPWykmFxL9vZKbX0hp0pYLDXR5uL0S283UMGl7LhQRj7cvwMy0mkXTAw5sCVavALka emAseurl2HLwCEVvCrc1rN/b/0Ncx7OdutMXC2CTLu78DD0Xivqfao5xNQQyBUxMbirL /q7g== X-Gm-Message-State: AOJu0Yzl/h7tf2Y4Q7nKgGtM8wIyubxgzMBk6kLeNWbHX5tkopZG4bHA ToS9N6pXWkJU6rrxTVZgje4HMB2iLSV/ysenNbMS48zp2Qa31UT6Zu3kbvH085+4ejLe/c75sQA nApR6Yq7+hBDmhFHH+uysYd9WqwKFAA== X-Google-Smtp-Source: AGHT+IEz9EsylQOvFcm5YT6wG5Ei6u3A+fC9Jb9hYZAZEkULjhxf5gcK8MkIZVJpjuccuJ10wRU8m+BG+uxTANyNurk= X-Received: by 2002:a05:690c:360c:b0:609:fef9:77b0 with SMTP id ft12-20020a05690c360c00b00609fef977b0mr3991111ywb.37.1714667049731; Thu, 02 May 2024 09:24:09 -0700 (PDT) MIME-Version: 1.0 References: <37de350c-1e5f-422f-b13a-c5a9a1e132ac AT linetec DOT nl> In-Reply-To: <37de350c-1e5f-422f-b13a-c5a9a1e132ac@linetec.nl> From: "Shashank Chintalagiri (shashank DOT chintalagiri AT gmail DOT com) [via geda-user AT delorie DOT com]" Date: Thu, 2 May 2024 21:53:58 +0530 Message-ID: Subject: Re: [geda-user] Gschem refdes autonumber over multiple pages? To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary="00000000000068516606177b084c" Reply-To: geda-user AT delorie DOT com --00000000000068516606177b084c Content-Type: text/plain; charset="UTF-8" I'm sorry if I'm missing something, but why not just use refdes_renum? Lepton has a version of it as well. You can provide as many schematic files as you want to it. The elements with refdes like U? Will get renumbered to a value past the highest number found for that type in any of the pages. Make sure you don't use --force so that the existing numbers aren't clobbered. It doesn't sound like you want --pgskip either. On Mon, 29 Apr 2024, 16:59 Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com], wrote: > Hi, > > I'm working on a project with several gschem-pages, based on an older, > existing schematic from someone else. I'm asked to add extra components > to these schematic pages, however while preserving the RefDes-numbering > of the older parts. > > This presents the problem that autonumbering in one page is not aware of > the numbering in other pages, so new components tend to get numbers that > are already in use in other pages, which is only signalled when I import > them into PCB. > > Is there a way to make gschem aware of all existing pages in a project? > Obviously, merely having those pages opened in the Page Manager doesn't > do the trick. I saw some references to defining a hierarchy and > sub-schematics, but I'm not sure if that is what I need (also, the wiki > page seems broken: wiki.geda-project.org/geda:hierarchy). > > I'd say it should be as simple as enumerating all project .sch files in > one place, but I can't find anything like this. > > TIA, > > Richard > > --00000000000068516606177b084c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm sorry if I'm missing something, but why not j= ust use refdes_renum? Lepton has a version of it as well.=C2=A0

You can provide as many schematic files a= s you want to it. The elements with refdes like U? Will get renumbered to a= value past the highest number found for that type in any of the pages.=C2= =A0

Make sure you don't use --force so that the existing numbers = aren't clobbered. It doesn't sound like you want --pgskip either.= =C2=A0

On Mon, 29 Apr 2024, 16:59 Richard Rasker (rasker AT linetec DOT nl) [via geda-user AT delorie DOT com], <geda-user AT delorie DOT com> wrote:
Hi,

I'm working on a project with several gschem-pages, based on an older, =
existing schematic from someone else. I'm asked to add extra components=
to these schematic pages, however while preserving the RefDes-numbering of the older parts.

This presents the problem that autonumbering in one page is not aware of the numbering in other pages, so new components tend to get numbers that are already in use in other pages, which is only signalled when I import them into PCB.

Is there a way to make gschem aware of all existing pages in a project? Obviously, merely having those pages opened in the Page Manager doesn't=
do the trick. I saw some references to defining a hierarchy and
sub-schematics, but I'm not sure if that is what I need (also, the wiki=
page seems broken: wiki.geda-project.org/geda:= hierarchy).

I'd say it should be as simple as enumerating all project .sch files in=
one place, but I can't find anything like this.

TIA,

Richard

--00000000000068516606177b084c--