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=KcG2rfL1RNIHPRipeYJmCkE4x6w
	Qy+aL/oWUg5/UBrM=; b=uFG2SfzF6JsKQ6xqErNyMZo8PYtXUFz4/FPJztGi14n
	eHzyCc3dcEwhMkZzJv87slIxOXgXsDzkf/tsMHvWhyLpIE+1YR2t88meFtrojaYU
	z6E9wiOGGODoErlsoNPpBrEYZti+lS0U/BBLrWhlbybFEnnRP1U4zHmAiQjPVCcr
	eGAJlgN4j4nZs/QnluXUenTi5a3x6Ynm89gCzzDuWUNsUXmMnM6qXEzCVhme4rcb
	Ih6dTJZyXo/ZzPIU2YCdaixXSf4ThXEsvrCayqXJKYLjLQOL5XugczUVWZriGSyK
	yxcnnVaqW4GEDnSb7FNHtzA0zTca5lmU/56hUCs4Y8A==
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=KcG2rfL1RNIHPRipeYJmCkE4x6wQy+aL/oWUg5/UBrM=; b=H18IV5KG
	FX89J2LD1R2MeRI0RUQyHgCshBJ/mpC0k42MYjHhxtxg43X6HHoUk7ns+C8zsVf0
	IpZowdD9Il1B3OEDEjgv5b3sliO067gUgCC37D/VFqGx5kIYGUlPlhKM4C+mbbPY
	ESVlgpOj77SqXsqU3gNujXxEDDcoP83PfY54Ke+7fIKi65avXTWF9zo4Iu+QYzOX
	VbMMOYV+zSPFPQpCHPJ63lYIDG6YvuPh1IfN3yeMzcPsSesu4mH+a038tYbGZp66
	rsk1YbajAjkyirCWeAiqz2Tw/3WoNveRQZND9h6oe4bXu+FdnKXRuGD/qF9j6DOx
	OxIMo0djmRuZxg==
X-ME-Sender:	<xms:ZuBQXMU1ist5ZclOni1D2fAkoQYHCYxHfvrcYfv35HR_kRxjK7bIZw>
X-ME-Proxy-Cause:	gggruggvucftvghtrhhoucdtuddrgedtledrjeefgddutdcutefuodetggdotefrodftvf
	curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt
	tdenucenucfjughrpehruffvfhfhkffffgggjggtsegrtderredtfeejnecuhfhrohhmpe
	fiihhrvhhinhcujfgvrhhruceoghhhvghrrhhlsehfrghsthhmrghilhdrtghomheqnecu
	kfhppedutdekrddvudehrdduleehrddvtdehnecurfgrrhgrmhepmhgrihhlfhhrohhmpe
	hghhgvrhhrlhesfhgrshhtmhgrihhlrdgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy:	<xmx:ZuBQXCdLsqBQDojoZVrM4TjDcHMLfls2DiWlzO9c53PWauONju-DaA>
	<xmx:ZuBQXFBGI8CpJKirqf19UV0i6xQycpRr9EGu3fDVXlLJKd_Qj2gYOg>
	<xmx:ZuBQXJ0YWkX6V3LvWfQZIQj90yllGkkchEdeIAqolyAWIb1U9hM9Sg>
	<xmx:ZuBQXFWBMaTRkqupdGHYjGOh1ZDFKoV7YIB-xY8twSeJV-X6bMQvQQ>
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>
From:	"Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<df1194d5-1347-3eb3-7a8a-f0de19b9e407@fastmail.com>
Date:	Tue, 29 Jan 2019 15:24:53 -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:	<CAJZxidCAe321UxZB4tDwamsSfa7VJTsdF6ucMGXYw2UA7LmGdQ@mail.gmail.com>
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

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

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 
> <mailto:dj AT delorie DOT com>> wrote:
>
>
>     Please make sure you have also checked the "only-visible" option
>     in the
>     png exporter dialog.
>

--------------A3459F29459736C2C63D3EFA
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 &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="moz-cite-prefix">On 1/29/19 2:39 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:CAJZxidCAe321UxZB4tDwamsSfa7VJTsdF6ucMGXYw2UA7LmGdQ AT mail DOT gmail DOT com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <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"
            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>
  </body>
</html>

--------------A3459F29459736C2C63D3EFA--

- Raw text -