[Gerbv-devel] [ gerbv-Bugs-2976400 ] Clear layer polarity not parsed?
Brought to you by:
spetm,
thepurlieu
From: SourceForge.net <no...@so...> - 2010-03-25 14:09:04
|
Bugs item #2976400, was opened at 2010-03-25 05:38 Message generated for change (Comment added) made by thepurlieu You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=409538&aid=2976400&group_id=33921 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Gerber Parser Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Nobody/Anonymous (nobody) >Assigned to: Julian Lamb (thepurlieu) Summary: Clear layer polarity not parsed? Initial Comment: Gerbv is really good already, but I found a bug related to the LPC (layer polarity clear) gerber command. See the attached file: This describes a single inner-plane copper layer. The actual file has three %LN (layer name) sections: %LNSubstrate* describes a copper pour plane (dark polarity) and is rendered correctly. %LNData* describes actual copper traces (dark polarity) and is rendered correctly. However, %LNScratch* describes areas where the copper traces traverse the copper pour, and where therefore a wider track has to be erased inside the copper pour, so that the pour and trace don't touch each other. This is done by setting this layer polarity to "clear" or "erase". This %LN is not rendered correctly as subtractive (negative), instead it is also additive (positive), and the result is not rendered correctly. Please use the attached file to reproduce the rendering error. ---------------------------------------------------------------------- >Comment By: Julian Lamb (thepurlieu) Date: 2010-03-25 09:09 Message: Thanks for the great bug report. I was able to confirm the problem and push a fix to our git tree. The problem was in the extra whitespace between the LN and LP commands. If you want to confirm the fix, please feel free to compile the source from git. Thanks. Julian ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=409538&aid=2976400&group_id=33921 |