Comment 15 for bug 1771726

Hi guys-

I just wanted to check in on this and see if it's been resolved.

Dr. M-

I think Bert's above comment (post #13) was in reference to the "gotcha" you mentioned in your earlier message (post #5). So, it may not be quite as out-of-the-blue as it seems.

Can you please confirm the various versions of the tools that are creating the issues? I'm having trouble reproducing it myself, so, it may have already been fixed.

The other thought that occurred to me was that the library footprint could have become corrupted. I think that you were testing some of the other bugfixes I was working on, so, if your footprint file happened to be corrupt, it might have been fixed by installing my bugfix work.

Roland-

Regarding the output in #10 above, where is that? The problematic output, I believe, was in the .pcb files produced by gsch2pcb. When I run it myself (gsch2pcb -V reports 1.6), I get an element in the resulting pcb file defined this way:

Element(0x00 "DIODE_LAY-300.fp" "D1" "unknown" 0 0 0 100 0x00)
(
 Pin(0 150 50 30 "1" 0x101)
 Pin(300 150 50 30 "2" 0x01)
 ElementLine(0 150 100 150 10)
 ElementLine(200 150 300 150 10)
 ElementLine(100 150 200 100 10)
 ElementLine(200 100 200 200 10)
 ElementLine(200 200 100 150 10)
 ElementLine(100 100 100 200 10)
 Mark(0 150)
)

I believe Dr. M was getting the following corrupted output:

Element(0x00 "DIODE_LAY-300.fp" "D1" "unknown" 20 0 100 0x00)
(
 Pin(0 50 30 "1" 0x101)
 Pin(300.fp 50 30 "2" 0x01)

 ElementLine(0 10)
 ElementLine( 300.fp 10)

 ElementLine( 10)
 ElementLine( 10)
 ElementLine( 10)
 ElementLine( 10)
 Mark(0 )
)

I apologize for not being much help on this... I've been so buried in the pcb core that I haven't actually dug into footprint libraries, or the import process.

Thanks for your help tracking this down.
--Chad