← Back to team overview

kicad-developers team mailing list archive

Re: FW: Next Grid hot key ` and the nightmare it can release


You are correct Dick, I never said it was a bug. I knew there was a half mil
Thrown away in the NC drill file generator, I just inadvertently pressed the
[`] key
And it changed the grid from 5 to 2.5 mils. Thank goodness I didn't do it
You know people make mistakes and our job should include minimizing the
Of those mistakes, kind of like the undo feature.
That being said I compiled Kicad with the updated NC drill file generator
and plotted
My design again. I submitted to the PCB house and it passed DRC with no
errors. Thanks
For Solving my problem I was looking at spending the holiday fixing the mess
I recommend anyone doing manual routing change the next grid hotkey to

-----Original Message-----
From: Dick Hollenbeck [mailto:dick@xxxxxxxxxxx] 
Sent: Tuesday, July 03, 2012 11:16 AM
To: Carl Rash; KiCad Developers
Subject: Re: [Kicad-developers] FW: Next Grid hot key ` and the nightmare it
can release

On 07/03/2012 05:09 AM, Carl Rash wrote:
> Dick,
> The diameter of the hole and the diameter of the via pad are correct 
> (verified with 3rd party gerber viewer), 0.015 and 0.025. The problem 
> is the hole is off center. I believe this code in gendrill.cpp is 
> selecting the size of the drill and that is correct. It may be that 
> placing a hole within one half a mil is not possible using the NC 
> format if that is the case then I would have like to have it detected 
> at the DRC phase and not after submission to the PCB fabrication 
> house. Perhaps a minimum annular ring test would be a good DRC check.
> I am going to try and change the next grid hot key to a combination 
> like
> Ctrl+G that way It will not be likely that I can inadvertently change 
> Ctrl+grid
> size without knowing it. I have never used auto routers, I prefer to 
> do it myself so I depend on the grid staying where I set it.
> Thanks for time
> Carl Rash

Is there actually a bug here?

It is sounding like a user error, not a true bug.

It is fully understandable that you do not like the current functionality,
which might be validly classified as something other than a bug.