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=majenko.co.uk; s=key1; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=HlGsjYt1+3r5GgEL7++OW1nZHGiOdvjcfEQJLDzYr/k=; b=VdoVpjCwSMry7qkPDb523uhD/v7vmUQ73ZiZe0/OuVce88Li6TjkDDaYGEataxljNX MilUY6zBTrKrRfeyEhkklbBW8uekQCHnBjGatLOxd25Z2Oyt+6sUZIFyd1jJDWoAk4kF v53Bp8oK+vw8MXdQ93CCTeRKAU1i04yKoI0RHJy0h1QG3DIijcoMaDk1VNhGcWc/HCNu QlDu+sf/DCYBRgUII4UmWF0HjZViFFwTXfOYWH/XjZotN4bwenMjPe8FmjqDFF15DVSH MBLBQljWffmNUyxjWkhKOToiK3p8OAr90hzkuI9m2kUeGX0nQzPH+3ZRoBQ55eVrN10l f4jw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=HlGsjYt1+3r5GgEL7++OW1nZHGiOdvjcfEQJLDzYr/k=; b=DMwpe3qZBEPBYGeA7yRJ0/oumYQ+IgkXbkQ/42nuzUADYbO09roA8oGa4tbpuTj0+E cba4WoMeg0qB7ly3qBbHlIqEJtJkmyoxGIwSpZRAb7PFodtpNcTBRqUCxCRFCw8anlJN ycAcDpZELYmhVD9taXxdAaXSYjKc/xkyMg1oFkfTbmTiwHUe36OJ/EHzJdYgrp/JyH6/ sdVuRoJjXKBmEljZgkkNGOHDOShmx4C5ahSk+CKOeP/IONhLkgUyLJwe1tzqpl18yLmd bI0FrlSC5Pp5dKASEW87tKmsHUtptcJojejHAIdQKSu31tfHQPKGaukeLnhRQs577l7L epKg== X-Gm-Message-State: APjAAAXDvBC5XoQnXiINxnciKWvkXdH+HCQcJ+eM1zwKyZ3caKLav8Lo R50JI1Wka3yWJcy3kJmIK7/hNfwH3G30smxKG3vbrTWc X-Google-Smtp-Source: APXvYqyMP/CCOFL+5CrKI875Md9/A83GDGDw9QZVnftBZPMbcjd41XuQ/LMxMd5wMTaZhqQ1KyJtoreZm2KMUnbNYvo= X-Received: by 2002:a2e:3a13:: with SMTP id h19mr2432620lja.220.1567461528831; Mon, 02 Sep 2019 14:58:48 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Majenko Technologies (matt AT majenko DOT co DOT uk) [via geda-user AT delorie DOT com]" Date: Mon, 2 Sep 2019 22:58:37 +0100 Message-ID: Subject: Re: [geda-user] gschem interaction from external processes To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary="000000000000a0166f05919913b5" Reply-To: geda-user AT delorie DOT com --000000000000a0166f05919913b5 Content-Type: text/plain; charset="UTF-8" Oh, and if you're wondering, the changes that I have made in PCB are: * Implemented "ElementPoly" so you can have silk polygons in elements - essential for logos * Added an extra layer that operates like an inverse of the solder mask layer for adjusting the solder paste size for pads - essential for making stencils * Added rudimentary scaling of the contents of the pastebuffer (not elements, but everything else) which is essential, again, for making logos and getting them the right size. The first of those adds extra stanzas to the footprint (and hence the pcb) files. The second adds an extra value to each Pad entry for the solder paste stencil aperture size. Both of those mean that my PCB files can't be opened by a normal copy of PCB since it doesn't know what they are. I added the changes a long, long, long time ago, and I have no clue how I did them. So reimplementing them would be a lot of re-learning. If someone has already implemented those, though, then I could look at switching to a newer version and experimenting with the new facilities, but until then I am stuck where I am. On Mon, Sep 2, 2019 at 10:47 PM Majenko Technologies wrote: > Well, yes at the moment I do have to use it. I don't have the import > functionality. The changes I have made to PCB have broken my ability to > pull upstream updates. Until I get round to re-creating the changes in PCB > (unless someone else has already done the things I have) in the current > codebase I'm stuck with an older version. I mean, I can't even open my > files in the new version (unless someone has changed the file format into > the exact same as I have...) > > I guess I should check out the latest version sometime and see what I > would need to reimplement to get myself up to date. > > On Mon, Sep 2, 2019 at 10:44 PM DJ Delorie wrote: > >> "Majenko Technologies (matt AT majenko DOT co DOT uk) [via geda-user AT delorie DOT com]" >> writes: >> > The way this system is designed, yes, I need to save and revert. You >> > need to ensure that the file is saved before running gsch2pcb >> > otherwise it won't know what he current elements are. And you need to >> > revert afterwards so that any removed elements vanish in PCB. >> >> I guess my question is "do you really need to run the obsolete gsch2pcb, >> instead of the new file->import that bypasses it and has much better >> functionality?" >> >> File->Import does not use gsch2pcb, it uses a different netlist filter >> that lets you do in-place updates. >> > > > -- > *Matt Jenkins* > Majenko Technologies > > -- *Matt Jenkins* Majenko Technologies --000000000000a0166f05919913b5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Oh, and if you're wondering, the changes that I have m= ade in PCB are:

* Implemented "ElementPoly" so= you can have silk polygons in elements - essential for logos
* A= dded an extra layer that operates like an inverse of the solder mask layer = for adjusting the solder paste size for pads - essential for making stencil= s
* Added rudimentary scaling of the contents of the pastebuffer = (not elements, but everything else) which is essential, again, for making l= ogos and getting them the right size.

The first of= those adds extra stanzas to the footprint (and hence the pcb) files. The s= econd adds an extra value to each Pad entry for the solder paste stencil ap= erture size.=C2=A0 Both of those mean that my PCB files can't be opened= by a normal copy of PCB since it doesn't know what they are.

I added the changes a long, long, long time ago, and I have no clue ho= w I did them. So reimplementing them would be a lot of re-learning. If some= one has already implemented those, though, then I could look at switching t= o a newer version and experimenting with the new facilities, but until then= I am stuck where I am.=C2=A0


On Mon, Sep 2, 2019 at 10= :47 PM Majenko Technologies <matt@= majenko.co.uk> wrote:
Well, yes at the moment I do have to use it.= =C2=A0 I don't have the import functionality. The changes I have made t= o PCB have broken my ability to pull upstream updates. Until I get round to= re-creating the changes in PCB (unless someone else has already done the t= hings I have) in the current codebase I'm stuck with an older version. = I mean, I can't even open my files in the new version (unless someone h= as changed the file format into the exact same as I have...)

=
I guess I should check out the latest version sometime and see what I = would need to reimplement to get myself up to date.

On Mon, Sep 2, 201= 9 at 10:44 PM DJ Delorie <dj AT delorie DOT com> wrote:
"Majenko Technologies (matt AT majenko DOT co DOT uk) [via geda-user AT delorie DOT com]"<= br> <geda-user AT de= lorie.com> writes:
> The way this system is designed, yes, I need to save and revert. You > need to ensure that the file is saved before running gsch2pcb
> otherwise it won't know what he current elements are. And you need= to
> revert afterwards so that any removed elements vanish in PCB.

I guess my question is "do you really need to run the obsolete gsch2pc= b,
instead of the new file->import that bypasses it and has much better
functionality?"

File->Import does not use gsch2pcb, it uses a different netlist filter that lets you do in-place updates.


--
= Matt Jenkins
Majenko Technologies



--
Matt Jenkins
Majenko= Technologies

--000000000000a0166f05919913b5--