<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/gerbertogcode/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/gerbertogcode/bugs/</id><updated>2009-09-09T00:49:49Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>Compile bug</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/10/" rel="alternate"/><published>2009-09-09T00:49:49Z</published><updated>2009-09-09T00:49:49Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.netbf1e99eaf728e3732aaaed3ea7f3075469f444b6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thomas Olson reported problems compiling the program with g++ 4.3.1  .  This could be a problem with configure requiring a version of g++ that is to high.  It could also be a problem with g++ 4.3.1  .  I am using g++ 4.2.4  .&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Using wrong movement G code and feedrate not set</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/9/" rel="alternate"/><published>2007-09-08T00:31:23Z</published><updated>2007-09-08T00:31:23Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.netcdf66e6e0e266240b916fc99f0d9dd8a15f25085</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;This was found by Chenah.&lt;/p&gt;
&lt;p&gt;I have been using G0 for rapid movement.  I should have been setting the tool feedrate with G94 and then using G01 for movement.  This will be changed in the future.  The feedrate with be a setting that is set in the same place the the spendel speed is set.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Only plots round vias.</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/8/" rel="alternate"/><published>2006-12-16T01:56:33Z</published><updated>2006-12-16T01:56:33Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.net339e1dad2a3973236d18738d20590717e55b9fc9</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently the gerber parser only parses round vias and then only plots round vias.  This needs to be changed for future releases.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Line segments in a trace are not being sorted correctly</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/7/" rel="alternate"/><published>2006-10-02T11:48:34Z</published><updated>2006-10-02T11:48:34Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.netd1c3e1d11850544185b5ba938cb02216c66612a6</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I found a bug where trace segments were not being&lt;br /&gt;
sorted correctly.  The segments have to be sorted for&lt;br /&gt;
the find_trace_edge function to work correctly.  The&lt;br /&gt;
problem is in optimize_segments and/or sort_points&lt;br /&gt;
functions.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Data structure change (better mem management)</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/6/" rel="alternate"/><published>2006-09-14T16:32:31Z</published><updated>2006-09-14T16:32:31Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.netd3bb9800a29017ce794962635b6db69dc855cd41</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Need to change the way memory is alocated.  Staticly &lt;br /&gt;
right now.  This needs to change to a dynamic system.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>parsing of coordinate</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/5/" rel="alternate"/><published>2006-09-09T02:30:50Z</published><updated>2006-09-09T02:30:50Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.netd1b9381e89a52b1acb917e0dfcd68c29738e2dcf</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;There is a problem where coordinates are not being&lt;br /&gt;
parsed correctly.  The problem is not occuring with all&lt;br /&gt;
coordinates, just some of them.&lt;/p&gt;
&lt;p&gt;-checking %FS statment and parse coordinate function.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Duplicate points in the gcode layer file</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/4/" rel="alternate"/><published>2006-09-01T11:31:22Z</published><updated>2006-09-01T11:31:22Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.netb095c0666b5e73cdcb4f740acae1f2f3770f863e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Sometimes the same point gets writen to the file.  This&lt;br /&gt;
is a consern from a size/speed of the file.  The main&lt;br /&gt;
place that this happens is at the beginning and end of&lt;br /&gt;
a trace segment.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Arcs at the end of traces are the wrong direction</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/3/" rel="alternate"/><published>2006-08-29T11:19:41Z</published><updated>2006-08-29T11:19:41Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.netfc45128b4e7723aaf603db314def09dc17718d23</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;The arc direction is wrong on some segments.  This&lt;br /&gt;
depends on how you draw them in the PCB program.&lt;/p&gt;
&lt;p&gt;Working of a fix that uses the other end of the trace&lt;br /&gt;
segment to determine if the arc should be clockwise or&lt;br /&gt;
counter clockwise.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Must have a via in the file</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/2/" rel="alternate"/><published>2006-08-29T11:14:13Z</published><updated>2006-08-29T11:14:13Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.net63f55138eb6818c160a970c613101a0565eec906</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Currently you must have a via in the layer file or the&lt;br /&gt;
program will parse the trace segments.&lt;/p&gt;
&lt;p&gt;The problem will be in gerber.h most likely in the way&lt;br /&gt;
the D code commands are parsed.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Finding trace edges</title><link href="https://sourceforge.net/p/gerbertogcode/bugs/1/" rel="alternate"/><published>2006-08-24T22:14:31Z</published><updated>2006-08-24T22:14:31Z</updated><author><name>matthew</name><uri>https://sourceforge.net/u/userid-1575798/</uri></author><id>https://sourceforge.net445cb1036a5ca0c3a8f82b34e8359e04c01005b0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Curently not finding all trace edges correctly.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>