X-Authentication-Warning: delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient: geda-help AT delorie DOT com
Subject: Re: [geda-help] gSchem to PCB: incremental design
From: Carlos Moreno <moreno+geda-help AT mochima DOT com>
To: geda-help AT delorie DOT com
References: <xnbmkt5rb7 DOT fsf AT envy DOT delorie DOT com>
 <fe4248de-67b4-ac9c-ad20-cac46d963693 AT mochima DOT com>
 <e1a6127e-ba8f-07c7-ad40-d80cdb25be57 AT mochima DOT com>
Message-ID: <36c96ec0-9e51-0eeb-2f9e-0db127ad2ed8@mochima.com>
Date: Fri, 27 Oct 2017 15:38:36 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <e1a6127e-ba8f-07c7-ad40-d80cdb25be57@mochima.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id v9RJcu4F003585
Reply-To: geda-help AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-help AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 10/26/2017 09:51 PM, Carlos Moreno wrote:
> [ ··· ]
> (I guess you can tell that right after my previous
> reply I went and ran a few tests of this feature....
> works beautifully!!!)

Actually, it seems to work beautifully with PCB version
20140326  (installed from source directly downloaded
from the gEDA web site).  But it does not work on
version 4.0.2 with the same .sch and .pcb files (this
version also installed from source).

Now, I cannot post the files, since they are part of a
research project being done with an industry partner
under NDA.

I'm posting this message in case this is a systematic
problem, or in case you can think of anything obvious
that I may be doing wrong.

When I do "Import Schematics" using the same .sch
and .pcb files but with version 4.0.2, it does not add
the elements, nor does it change the footprint of
two of the components, nor does it flag a bunch of
shorted nets (the orange-ish highlight).  It only flags
*one* shorted net  (i.e., it highlights in orange *one*
pin).

Sorry I can't be more helpful  (to determine whether
it is indeed a bug and to have an instance to help
debug it).

Cheers,
Carlos
--