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=fastmail.com; h=
	reply-to:subject:to:references:from:message-id:date:mime-version
	:in-reply-to:content-type; s=fm2; bh=2r6/+no9RuW5DTPdSRm1rEbDPvs
	25EwgjF0dE8WR3oE=; b=A7tXSL+puqy/wxotYUJXicNRjF+4WVqxyzriZ2AMUjx
	UFUmVzCec4t4/flWG6IW8b8HoZ8eWTCUYNmAPiO23SCB8NtkZsYSzNfM8HDU9/p4
	9I2s9N6+4p86kZTQrvXr9MD6tSwm7Sys1AoXKGb1zrcpB1jTLZXStbWkhChpQnSj
	GdvpBIcyEV6H9BSgYAtXUd1VbmjSE6wjYwe6jUtrOiZZOZZkL015Ltf1toyq3RCu
	IUGSPpv7fnN5PlWgGzP4NIg1Cjgj7NeFk2SCM8Ya54vn5L7sOVJMQiGby81j0vHE
	ZP06/lDu8ObCBgVoMQziAEyPFy60TwQZdKMpSkCJ2NQ==
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-type:date:from:in-reply-to
	:message-id:mime-version:references:reply-to:subject:to
	:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=
	fm1; bh=2r6/+no9RuW5DTPdSRm1rEbDPvs25EwgjF0dE8WR3oE=; b=vaUn24NQ
	1WaLJfLx3y5VGyugcQQ1k+oMB5lknUf9nLJuwHhafYb30XzTlAoCBIVvyVHTNXFQ
	fUtRaZmnZRuBtA3l33ZV8QQnvHEEyv+z88MAscXLr7ZtRHpVvJL+mPfVOsL+MfM7
	2pw+HKaY4qr46bRT8/vhV0S/fGHokUKHwpV4V5x5/H/gWCWCnAmSb+hUe58vvBVo
	LeMmFZQdRzn0JR+Ns0SbVWKHoDsDKWYQs1ANtJmvErunJ0Qxeetj5XabIQZqcTQF
	aMOE6scQ2e7lrtyYfPwFMckYWSZHByO7b5opl7dXpicumXciOZ8tT7rC3Mp34ehW
	8+OBDludsjrSeg==
X-ME-Sender: <xms:WOlQXJtaDfFBGSoL_qVzCjAeVUWzyXa-giUW0Xj7q692qr8CceR3Ew>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjeefgddukecutefuodetggdotefrodftvf
    curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt
    tdenucenucfjughrpehruffvfhfhkffffgggjggtsegrtderredtfeejnecuhfhrohhmpe
    fiihhrvhhinhcujfgvrhhruceoghhhvghrrhhlsehfrghsthhmrghilhdrtghomheqnecu
    ffhomhgrihhnpehlrghunhgthhhprggurdhnvghtnecukfhppedutdekrddvudehrddule
    ehrddvtdehnecurfgrrhgrmhepmhgrihhlfhhrohhmpehghhgvrhhrlhesfhgrshhtmhgr
    ihhlrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:WOlQXNRnM2Lksdv-O-Q_PPVzVf_gzEsPxzRnc5CSwoPT5Eitq0nQWg>
    <xmx:WOlQXLB5w2AsxEq-IP32VOk6uBHUjmR2P5hwCyNqur7dR8qInm1Vnw>
    <xmx:WOlQXPyntqr6mTH0Jbb3eu_JrWS3igPheyDUm2NUqWhuuImoZ64wxA>
    <xmx:WelQXBS0N8-_I0kOCrT54gcyZ-ZGniKVFmp4MZgTlXbA6JFIxotyrw>
Subject: Re: [geda-user] PCB 4.1.3 png export acting weird
To: geda-user AT delorie DOT com
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>
From: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID: <1993f267-eaba-d065-2a84-11d33a165b8e@fastmail.com>
Date: Tue, 29 Jan 2019 16:03:04 -0800
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:60.0) Gecko/20100101
 Thunderbird/60.4.0
MIME-Version: 1.0
In-Reply-To: <CAJZxidDS71EmH9vb1=DHscAB5c=CkiRv+7YpJuxNVqAV7jQPvQ@mail.gmail.com>
Content-Type: multipart/alternative;
 boundary="------------56032AC365593CDE058CD08E"
Content-Language: en-US
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

This is a multi-part message in MIME format.
--------------56032AC365593CDE058CD08E
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

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 
> <mailto:gherrl AT fastmail DOT com>) [via geda-user AT delorie DOT com 
> <mailto:geda-user AT delorie DOT com>] <geda-user AT delorie DOT com 
> <mailto: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
>     <mailto:parker DOT charles AT gmail DOT com>) [via geda-user AT delorie DOT com
>     <mailto: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
>>     <mailto:dj AT delorie DOT com>> wrote:
>>
>>
>>         Please make sure you have also checked the "only-visible"
>>         option in the
>>         png exporter dialog.
>>

--------------56032AC365593CDE058CD08E
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Chad,</p>
    <p>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.<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="moz-cite-prefix">On 1/29/19 3:35 PM, Chad Parker
      (<a class="moz-txt-link-abbreviated" href="mailto:parker DOT charles AT gmail DOT com">parker DOT charles AT gmail DOT com</a>) [via <a class="moz-txt-link-abbreviated" href="mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAJZxidDS71EmH9vb1=DHscAB5c=CkiRv+7YpJuxNVqAV7jQPvQ AT mail DOT gmail DOT com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>Okay, so, it's not a recent thing. That means I didn't
          break anything (that I don'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="ltr"><br>
        </div>
        <div>LaunchPad is the bug tracker that we use:<br>
        </div>
        <div dir="ltr"><a href="https://launchpad.net/pcb"
            moz-do-not-send="true">https://launchpad.net/pcb</a><br>
        </div>
        <div dir="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="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Tue, Jan 29, 2019 at 6:30
          PM Girvin Herr (<a href="mailto:gherrl AT fastmail DOT com"
            moz-do-not-send="true">gherrl AT fastmail DOT com</a>) [via <a
            href="mailto:geda-user AT delorie DOT com" moz-do-not-send="true">geda-user AT delorie DOT com</a>]
          &lt;<a href="mailto:geda-user AT delorie DOT com"
            moz-do-not-send="true">geda-user AT delorie DOT com</a>&gt; wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div bgcolor="#FFFFFF">
            <p>Chad &amp; DJ,</p>
            <p>Thanks for your prompt response.<br>
            </p>
            <p>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.<br>
            </p>
            <p>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.<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="gmail-m_1362729497396179040moz-cite-prefix">On
              1/29/19 2:39 PM, Chad Parker (<a
                class="gmail-m_1362729497396179040moz-txt-link-abbreviated"
                href="mailto:parker DOT charles AT gmail DOT com" target="_blank"
                moz-do-not-send="true">parker DOT charles AT gmail DOT com</a>)
              [via <a
                class="gmail-m_1362729497396179040moz-txt-link-abbreviated"
                href="mailto:geda-user AT delorie DOT com" target="_blank"
                moz-do-not-send="true">geda-user AT delorie DOT com</a>] wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="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'll take a look.<br>
                </div>
              </div>
              <br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Tue, Jan 29, 2019
                  at 5:29 PM DJ Delorie &lt;<a
                    href="mailto:dj AT delorie DOT com" target="_blank"
                    moz-do-not-send="true">dj AT delorie DOT com</a>&gt; wrote:<br>
                </div>
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex"><br>
                  Please make sure you have also checked the
                  "only-visible" option in the<br>
                  png exporter dialog.<br>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>

--------------56032AC365593CDE058CD08E--