delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2019/02/05/14:40:39

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=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=uRsSW21jmECjUEwXjlwTht6we8GGs15o6afXSdduz9A=;
b=Z/93giJvhqp3LKkHowBSg/53Qgvt4yZw/HI4DIUfG9EfO11SzY+l6mrSaCplTiqgCx
Er/39kjFjq6nhuqGEClDQltHiddK1gRqPDU9e5TFxkWgNRy0oddfJJEQUdxqHIFFXFsT
CRqIB5H/UyGTU1vHJNb95T3HzbmZ6peOcsj7xyvEfIwk4J0YYOKedK2F3X5tssqpaooj
4Zbpb52MOqBXMkL2Qe9oV6D2HeIsvUN+ccESVfbLKsdQzW3SXZqShhsI5Tkm0LgIzobI
lLpfrsWs9lCPm+z1i0MPkpsJbmCp+GnQrprEb7rl1ToL0AUP2gsKopD/ifsoMzONl03a
0EOg==
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=uRsSW21jmECjUEwXjlwTht6we8GGs15o6afXSdduz9A=;
b=PdPhw8zM1o8tx9xwdaHU03zv+0QaxsXTxsB+3rvD3A93Bp/PIT+q/2MYgTNr877a/G
pSadMeArSFq5jYAFAEdtlE3I5Kv1e11Wz+dte65L8uDVVlkUopyWVmM+v6EzO/7AvcNC
OoJ0+rVGCojj14dvjg2Kx7nGJ5W4OmM0jhaPlw/P1F9mPRZ35FsyEyP68y2bSNSh5jWi
pX/r0PdQbalr8WCw6j6KmQfuQvBUf6uSenjwlQKbUaqOuA3eYn7WtqkDtC7g7mDn4WI2
twcynC7pNGDlKX9AF//tA1BZ26lA6LmuZW+ikVK4zEl8peCv11b5BpqFDqhU6TY8Ogoj
TgZQ==
X-Gm-Message-State: AHQUAuYmXZI7nxurd5vfhOBfehzWs+U8c7T0/NGolxbJYyeLVyQRFdym
3sn1oEWhSUuVejAmS8QnzLEW9q1jKz+iBexyBliwWg==
X-Google-Smtp-Source: AHgI3IYjDY0dh9qRE0iKgmAnl22vVWcf/5HKzN7vRmfrmv5eYjgVS/HawMDBxaP8CpuwdlE7o5P9nn7M0IebRzL6gVE=
X-Received: by 2002:a62:42d4:: with SMTP id h81mr6583809pfd.259.1549395481582;
Tue, 05 Feb 2019 11:38:01 -0800 (PST)
MIME-Version: 1.0
References: <34d4880c-3aa0-26a2-0d02-ab740ccda6be AT fastmail DOT com>
<xnva2714ug DOT fsf AT envy DOT delorie DOT com> <CAJZxidCAe321UxZB4tDwamsSfa7VJTsdF6ucMGXYw2UA7LmGdQ AT mail DOT gmail DOT com>
<df1194d5-1347-3eb3-7a8a-f0de19b9e407 AT fastmail DOT com> <CAJZxidDS71EmH9vb1=DHscAB5c=CkiRv+7YpJuxNVqAV7jQPvQ AT mail DOT gmail DOT com>
<1993f267-eaba-d065-2a84-11d33a165b8e AT fastmail DOT com> <CAJZxidCU-w=PLqAjXvT6Vvx42XQ4NAxdPi9LWH+4sj42tZMyjg AT mail DOT gmail DOT com>
<02221dee-bb68-95bd-c28f-93db1f85043a AT fastmail DOT com>
In-Reply-To: <02221dee-bb68-95bd-c28f-93db1f85043a@fastmail.com>
From: "Chad Parker (parker DOT charles AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Date: Tue, 5 Feb 2019 14:37:50 -0500
Message-ID: <CAJZxidBz5DpZLyYkhAhJ_s+fVAOMiBCCJb2ru3N0p_6XB0ajLA@mail.gmail.com>
Subject: Re: [geda-user] PCB 4.1.3 png export acting weird
To: geda-user AT delorie DOT com
Reply-To: geda-user AT delorie DOT com

--0000000000004be1b205812abf14
Content-Type: text/plain; charset="UTF-8"

Thanks Girvin. The consistency of the exporters is something that's on my
radar/todo list.

I was going to suggest that you try the eps output instead of the png
output, if for no other reason than it's a vector file, and so easily
scalable. It can be a little dicey sometimes with polygons because they get
diced up into pieces for the export, but otherwise works pretty well. I've
done this with Inkscape, and it works pretty well.

On Tue, Feb 5, 2019 at 2:17 PM Girvin Herr (gherrl AT fastmail DOT com) [via
geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> Chad,
>
> Just an update to let you know what I discovered since my last message. I
> discovered that LibreCad (LC) does not handle PNG imports very well. It
> imports the file, but it is huge. When I tried to "scale" it down by a
> reasonable amount, the image disappeared! I later read that LC prefers
> vector graphics to raster bit-maps, of which PNG is, and suggests
> converting the raster file to DXF using inkscape. I have tried that in the
> past, but with less than successful results.
>
> However, I tried exporting the PCB layers I want using the EPS option
> instead of the PNG option, and then running the EPS file through pstoedit,
> which converts it to DXF, which is LC's native file format for "blocks". I
> then imported the DXF file as a block into my LC drawing and it worked
> fine. I was then able to make my assembly drawing using the PCB exported
> design without re-drawing it. Slick.
>
> BTW: For another "data point", I was going to try to export my design as
> EPS without the work-around you suggested (no copper layers selected), but
> DJ mentioned in a previous message in this thread that the EPS option also
> has the same problem. So, I will not bother testing it.
>
> BTW2: I discovered the "PS" PCB export option produces the same output as
> File > Print - all board layers on separate pages - which is not the same
> format as the other export options. That was not expected but may be by
> design for some reason. It may be more intuitive to "Print" to a file using
> PostScript and let the PS export have the same result as the other export
> options.
>
> Girvin
>
>
> On 1/29/19 4:31 PM, Chad Parker (parker DOT charles AT gmail DOT com) [via
> geda-user AT delorie DOT com] wrote:
>
> Great! I'm glad we have a working solution for now.
>
> Since you have something that works, I'll look into it some more this
> weekend.
>
> Cheers,
> --Chad
>
> On Tue, Jan 29, 2019 at 7:08 PM Girvin Herr (gherrl AT fastmail DOT com) [via
> geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>
>> Chad,
>>
>> Okay, here's what I did. As you suggested, I used the unused "signal2"
>> layer to create a box around the board edge and kept it turned on with the
>> "component" and "solder" layers turned off. In the PNG dialog, I checked
>> the "screen-layout-order" option and that gave me what I want - silkscreen,
>> pins, and outline. If I leave the "screen-layout-order" option unchecked
>> and nothing else changed, then I get everything again - traces from both
>> sides and all.
>>
>> So, I thank you for your work-around and I can continue my work wile you
>> get it sorted out. I will look into posting a bug report ASAP.
>>
>> Thanks Again.
>> Girvin
>>
>>
>> On 1/29/19 3:35 PM, Chad Parker (parker DOT charles AT gmail DOT com) [via
>> geda-user AT delorie DOT com] wrote:
>>
>> Okay, so, it's not a recent thing. That means I didn't break anything
>> (that I don't already know about) :)
>>
>> As a temporary workaround, do you have a spare copper layer? Maybe you
>> could draw the outline on the spare layer and enable it. Perhaps that would
>> trick the pads into being drawn while we get this sorted out.
>>
>> LaunchPad is the bug tracker that we use:
>> https://launchpad.net/pcb
>>
>> Generally common sense applies. Provide enough info so that the devs can
>> reproduce the problem. The easier you make it for us and the more specific
>> you can be, the easier it is for us to help you.
>>
>> Thanks,
>> --Chad
>>
>>
>> On Tue, Jan 29, 2019 at 6:30 PM Girvin Herr (gherrl AT fastmail DOT com) [via
>> geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
>>
>>> Chad & DJ,
>>>
>>> Thanks for your prompt response.
>>>
>>> Yes, I have "Only-visible" checked in the PNG dialog. That was the first
>>> thing I did, since the prompt specifically said "...visible items...",
>>> which implies visible on the screen.
>>>
>>> I thought I did this before, but my notes from then say to enable
>>> "Component" side to get pads. Otherwise will only get silkscreen. Sounds
>>> familiar. However, that board was a single-sided board, so it didn't
>>> matter, since there were no traces on the Component side. This new board is
>>> a double-sided board. I just checked and exporting with "Component" layer
>>> turned on will produce the top silk, pins and both component and solder
>>> layer traces, which still is not what I want. I don't want the traces for
>>> this export. According to the PNG file date on that single-sided board, it
>>> was February of 2015. So, this process was giving me problems that far back
>>> at least.
>>>
>>> I have never used LaunchPad before or filed a bug report. How do I do
>>> that? Is there a process document I can read to do it? If so, where can I
>>> find it?
>>>
>>> Thanks again.
>>> Girvin
>>>
>>>
>>> On 1/29/19 2:39 PM, Chad Parker (parker DOT charles AT gmail DOT com) [via
>>> geda-user AT delorie DOT com] wrote:
>>>
>>> It does appear that the pins and pads not being drawn. Did this ever
>>> work for you? Did it break recently?
>>>
>>> Could you please file a bug report on LaunchPad? I'll take a look.
>>>
>>> On Tue, Jan 29, 2019 at 5:29 PM DJ Delorie <dj AT delorie DOT com> wrote:
>>>
>>>>
>>>> Please make sure you have also checked the "only-visible" option in the
>>>> png exporter dialog.
>>>>
>>>

--0000000000004be1b205812abf14
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Thanks Girvin. The consistency of the exporters is so=
mething that&#39;s on my radar/todo list.</div><div><br></div><div>I was go=
ing to suggest that you try the eps output instead of the png output, if fo=
r no other reason than it&#39;s a vector file, and so easily scalable. It c=
an be a little dicey sometimes with polygons because they get diced up into=
 pieces for the export, but otherwise works pretty well. I&#39;ve done this=
 with Inkscape, and it works pretty well.<br></div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Feb 5, 2019 at 2=
:17 PM Girvin Herr (<a href=3D"mailto:gherrl AT fastmail DOT com">gherrl AT fastmail.=
com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT co=
m</a>] &lt;<a href=3D"mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</=
a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF">
    <p>Chad,</p>
    <p>Just an update to let you know what I discovered since my last
      message. I discovered that LibreCad (LC) does not handle PNG
      imports very well. It imports the file, but it is huge. When I
      tried to &quot;scale&quot; it down by a reasonable amount, the image
      disappeared! I later read that LC prefers vector graphics to
      raster bit-maps, of which PNG is, and suggests converting the
      raster file to DXF using inkscape. I have tried that in the past,
      but with less than successful results.<br>
    </p>
    <p>However, I tried exporting the PCB layers I want using the EPS
      option instead of the PNG option, and then running the EPS file
      through pstoedit, which converts it to DXF, which is LC&#39;s native
      file format for &quot;blocks&quot;. I then imported the DXF file as a=
 block
      into my LC drawing and it worked fine. I was then able to make my
      assembly drawing using the PCB exported design without re-drawing
      it. Slick.</p>
    <p>BTW: For another &quot;data point&quot;, I was going to try to expor=
t my
      design as EPS without the work-around you suggested (no copper
      layers selected), but DJ mentioned in a previous message in this
      thread that the EPS option also has the same problem. So, I will
      not bother testing it.</p>
    <p>BTW2: I discovered the &quot;PS&quot; PCB export option produces the=
 same
      output as File &gt; Print - all board layers on separate pages -
      which is not the same format as the other export options. That was
      not expected but may be by design for some reason. It may be more
      intuitive to &quot;Print&quot; to a file using PostScript and let the=
 PS
      export have the same result as the other export options.<br>
    </p>
    <p>Girvin</p>
    <p><br>
    </p>
    <div class=3D"gmail-m_-6479530618421771643moz-cite-prefix">On 1/29/19 4=
:31 PM, Chad Parker
      (<a class=3D"gmail-m_-6479530618421771643moz-txt-link-abbreviated" hr=
ef=3D"mailto:parker DOT charles AT gmail DOT com" target=3D"_blank">parker DOT charles AT gma=
il.com</a>) [via <a class=3D"gmail-m_-6479530618421771643moz-txt-link-abbre=
viated" href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT d=
elorie.com</a>] wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div>Great! I&#39;m glad we have a working solution for now. <br>
        </div>
        <div><br>
        </div>
        <div>Since you have something that works, I&#39;ll look into it som=
e
          more this weekend.</div>
        <div><br>
        </div>
        <div>Cheers,</div>
        <div>--Chad<br>
        </div>
      </div>
      <br>
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 29, 2019 at 7:08
          PM Girvin Herr (<a href=3D"mailto:gherrl AT fastmail DOT com" target=3D"=
_blank">gherrl AT fastmail DOT com</a>) [via <a href=3D"mailto:geda-user AT delorie DOT c=
om" target=3D"_blank">geda-user AT delorie DOT com</a>]
          &lt;<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">ge=
da-user AT delorie DOT com</a>&gt; wrote:<br>
        </div>
        <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div bgcolor=3D"#FFFFFF">
            <p>Chad,</p>
            <p>Okay, here&#39;s what I did. As you suggested, I used the
              unused &quot;signal2&quot; layer to create a box around the b=
oard
              edge and kept it turned on with the &quot;component&quot; and
              &quot;solder&quot; layers turned off. In the PNG dialog, I ch=
ecked
              the &quot;screen-layout-order&quot; option and that gave me w=
hat I
              want - silkscreen, pins, and outline. If I leave the
              &quot;screen-layout-order&quot; option unchecked and nothing =
else
              changed, then I get everything again - traces from both
              sides and all.<br>
            </p>
            <p>So, I thank you for your work-around and I can continue
              my work wile you get it sorted out. I will look into
              posting a bug report ASAP.</p>
            <p>Thanks Again.<br>
              Girvin</p>
            <p><br>
            </p>
            <div class=3D"gmail-m_-6479530618421771643gmail-m_8606545683239=
727187moz-cite-prefix">On
              1/29/19 3:35 PM, Chad Parker (<a class=3D"gmail-m_-6479530618=
421771643gmail-m_8606545683239727187moz-txt-link-abbreviated" href=3D"mailt=
o:parker DOT charles AT gmail DOT com" target=3D"_blank">parker DOT charles AT gmail DOT com</a>)
              [via <a class=3D"gmail-m_-6479530618421771643gmail-m_86065456=
83239727187moz-txt-link-abbreviated" href=3D"mailto:geda-user AT delorie DOT com" =
target=3D"_blank">geda-user AT delorie DOT com</a>] wrote:<br>
            </div>
            <blockquote type=3D"cite">
              <div dir=3D"ltr">
                <div>Okay, so, it&#39;s not a recent thing. That means I
                  didn&#39;t break anything (that I don&#39;t already know
                  about) :)<br>
                </div>
                <div><br>
                </div>
                <div>As a temporary workaround, do you have a spare
                  copper layer? Maybe you could draw the outline on the
                  spare layer and enable it. Perhaps that would trick
                  the pads into being drawn while we get this sorted
                  out.<br>
                </div>
                <div dir=3D"ltr"><br>
                </div>
                <div>LaunchPad is the bug tracker that we use:<br>
                </div>
                <div dir=3D"ltr"><a href=3D"https://launchpad.net/pcb" targ=
et=3D"_blank">https://launchpad.net/pcb</a><br>
                </div>
                <div dir=3D"ltr"><br>
                </div>
                <div>Generally common sense applies. Provide enough info
                  so that the devs can reproduce the problem. The easier
                  you make it for us and the more specific you can be,
                  the easier it is for us to help you.</div>
                <div><br>
                </div>
                <div>Thanks,</div>
                <div>--Chad<br>
                </div>
                <div><br>
                </div>
              </div>
              <br>
              <div class=3D"gmail_quote">
                <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan 29, 2019
                  at 6:30 PM Girvin Herr (<a href=3D"mailto:gherrl AT fastmail=
.com" target=3D"_blank">gherrl AT fastmail DOT com</a>) [via
                  <a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank=
">geda-user AT delorie DOT com</a>]
                  &lt;<a href=3D"mailto:geda-user AT delorie DOT com" target=3D"_b=
lank">geda-user AT delorie DOT com</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                  <div bgcolor=3D"#FFFFFF">
                    <p>Chad &amp; DJ,</p>
                    <p>Thanks for your prompt response.<br>
                    </p>
                    <p>Yes, I have &quot;Only-visible&quot; checked in the =
PNG
                      dialog. That was the first thing I did, since the
                      prompt specifically said &quot;...visible items...&qu=
ot;,
                      which implies visible on the screen.<br>
                    </p>
                    <p>I thought I did this before, but my notes from
                      then say to enable &quot;Component&quot; side to get =
pads.
                      Otherwise will only get silkscreen. Sounds
                      familiar. However, that board was a single-sided
                      board, so it didn&#39;t matter, since there were no
                      traces on the Component side. This new board is a
                      double-sided board. I just checked and exporting
                      with &quot;Component&quot; layer turned on will produ=
ce the
                      top silk, pins and both component and solder layer
                      traces, which still is not what I want. I don&#39;t
                      want the traces for this export. According to the
                      PNG file date on that single-sided board, it was
                      February of 2015. So, this process was giving me
                      problems that far back at least.<br>
                    </p>
                    <p>I have never used LaunchPad before or filed a bug
                      report. How do I do that? Is there a process
                      document I can read to do it? If so, where can I
                      find it?</p>
                    <p>Thanks again.<br>
                      Girvin<br>
                    </p>
                    <p><br>
                    </p>
                    <div class=3D"gmail-m_-6479530618421771643gmail-m_86065=
45683239727187gmail-m_1362729497396179040moz-cite-prefix">On
                      1/29/19 2:39 PM, Chad Parker (<a class=3D"gmail-m_-64=
79530618421771643gmail-m_8606545683239727187gmail-m_1362729497396179040moz-=
txt-link-abbreviated" href=3D"mailto:parker DOT charles AT gmail DOT com" target=3D"_b=
lank">parker DOT charles AT gmail DOT com</a>)
                      [via <a class=3D"gmail-m_-6479530618421771643gmail-m_=
8606545683239727187gmail-m_1362729497396179040moz-txt-link-abbreviated" hre=
f=3D"mailto:geda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com<=
/a>]
                      wrote:<br>
                    </div>
                    <blockquote type=3D"cite">
                      <div dir=3D"ltr">
                        <div>It does appear that the pins and pads not
                          being drawn. Did this ever work for you? Did
                          it break recently?<br>
                        </div>
                        <div><br>
                        </div>
                        <div>Could you please file a bug report on
                          LaunchPad? I&#39;ll take a look.<br>
                        </div>
                      </div>
                      <br>
                      <div class=3D"gmail_quote">
                        <div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jan
                          29, 2019 at 5:29 PM DJ Delorie &lt;<a href=3D"mai=
lto:dj AT delorie DOT com" target=3D"_blank">dj AT delorie DOT com</a>&gt;
                          wrote:<br>
                        </div>
                        <blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
br>
                          Please make sure you have also checked the
                          &quot;only-visible&quot; option in the<br>
                          png exporter dialog.<br>
                        </blockquote>
                      </div>
                    </blockquote>
                  </div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </div>

</blockquote></div>

--0000000000004be1b205812abf14--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019