kicad-developers team mailing list archive

[Jeff Young <jeff@xxxxxxxxx>]

Hi Michael,

Odd.  

FWIW, if you set the interactive router to “Highlight Collisions” mode it will put you in the driver’s seat.  (I think it then acts more like Default, although it’s been so long since I’ve used Default I can’t remember exactly.)

Cheers,
Jeff.


> On 17 Apr 2018, at 11:14, Michael McCormack <mike@xxxxxxxxxx> wrote:
> 
> Not a help,
> <image.png>
> 
> And I'd do more outside of default view if backspace and delete worked on traces the same or maybe if the interactive router wasn't so wonky when I'm trying to be precise about where I want traces (you pitched it so I'm providing the feedback.)
> 
> On Tue, Apr 17, 2018 at 5:59 AM, Jeff Young <jeff@xxxxxxxxx <mailto:jeff@xxxxxxxxx>> wrote:
> Hi Michael,
> 
> You appear to be in Legacy graphics mode (probably still called “Default” in 4.0.7).  Have you tried OpenGL or Cairo graphics mode?  (Note that the modes also change the toolsets, and are a big step up over the default/legacy toolset.)
> 
> Cheers,
> Jeff.
> 
> 
>> On 17 Apr 2018, at 10:45, Michael McCormack <mike@xxxxxxxxxx <mailto:mike@xxxxxxxxxx>> wrote:
>> 
>> I did try that, but given the oddness of the behavior, I did not resave the board in case someone wanted to check it out and saving would somehow mess things up.  Here is the screen shot with all layers and everything enable, still empty at the bottom.
>> 
>> 
>> <image.png>
>> 
>> 
>> On Tue, Apr 17, 2018 at 5:14 AM, jp charras <jp.charras@xxxxxxxxxx <mailto:jp.charras@xxxxxxxxxx>> wrote:
>> Le 17/04/2018 à 03:42, Steven A. Falco a écrit :
>> > I tried opening the board under Fedora Linux with Kicad 4.0.7 using pcbnew in stand-alone mode, and the hole is visible, as shown in the attached screen-shot.
>> > 
>> >       Steve
>> > 
>> > On 04/16/2018 09:30 PM, Jon Evans wrote:
>> >> I tested on Ubuntu and Windows 10 using 5.0rc2 and don't see the problem, so I guess it has been fixed somewhere along the way.
>> >>
>> >> On Mon, Apr 16, 2018 at 8:12 PM, Michael McCormack <mike@xxxxxxxxxx <mailto:mike@xxxxxxxxxx> <mailto:mike@xxxxxxxxxx <mailto:mike@xxxxxxxxxx>>> wrote:
>> >>
>> >>     OK, here is the boar file, if you need anything else, please let me know.
>> >>
>> >>     On Mon, Apr 16, 2018 at 6:09 PM, Jeff Young <jeff@xxxxxxxxx <mailto:jeff@xxxxxxxxx> <mailto:jeff@xxxxxxxxx <mailto:jeff@xxxxxxxxx>>> wrote:
>> >>
>> >>         Looks like a different bug (2.9mm drill is smaller than 3.2mm pad).
>> >>
>> >>         I can’t reproduce it on 5.0rc2 Mac.  Not sure if that’s because it’s fixed in 5.0, or it only shows up on Windows, or it’s something specific to Michael’s setup.
>> >>
>> >>
>> >>>         On 16 Apr 2018, at 22:44, Michael McCormack <mike@xxxxxxxxxx <mailto:mike@xxxxxxxxxx> <mailto:mike@xxxxxxxxxx <mailto:mike@xxxxxxxxxx>>> wrote:
>> 
>> I tried the board both under Pcbnew 4.07 last stable and the current 5.0rc2 and I do not have any
>> problem with these NPTH pads (I can edit the pad and move the footprint).
>> 
>> Be aware you have set many layers and NPTH to "no show".
>> Perhaps you should set all items and layers to "show"
>> 
>> 
>> >>>
>> >>>         This is the module snipped from the board file:
>> >>>
>> >>>           (module Ori:MountingHole_3.2mm_M3_ISO14580 (layer F.Cu) (tedit 59C8FBCE) (tstamp 5AC4E91C)
>> >>>             (at 138.25 141.050001)
>> >>>             (descr "Mounting Hole 3.2mm, no annular, M3, ISO14580")
>> >>>             (tags "mounting hole 3.2mm no annular m3 iso14580")
>> >>>             (path /583B5C0A)
>> >>>             (fp_text reference M1 (at 0 -3.75) (layer F.SilkS) hide
>> >>>               (effects (font (size 1 1) (thickness 0.15)))
>> >>>             )
>> >>>             (fp_text value "M3_Mounting Hole" (at 0 3.75) (layer F.Fab)
>> >>>               (effects (font (size 1 1) (thickness 0.15)))
>> >>>             )
>> >>>             (fp_circle (center 0 0) (end 2.75 0) (layer Cmts.User) (width 0.15))
>> >>>             (fp_circle (center 0 0) (end 3 0) (layer F.CrtYd) (width 0.05))
>> >>>             (pad "" np_thru_hole circle (at 0 0) (size 3.2 3.2) (drill 2.9) (layers *.Cu *.Mask)
>> >>>               (clearance 2))
>> >>>           )
>> >>>
>> >>>         I am using 4.0.7 under Windows 10, if you decode this is the known bug I sincerely apologize for having wasted your time.  I did not see a bug that I thought was the same thing.  If not, I will mail it to any and all of you to look at.  I won't obfuscate, I'd be afraid to disturb the problem.  I see no real problem sharing the board with Kicad developers but can also understand why my employer is not keen to have our boards posted on the internet.
>> >>>
>> >>>         Cheers
>> >>>         Mike
>> >>>
>> >>>
>> >>>         On Mon, Apr 16, 2018 at 5:13 PM, Jon Evans <jon@xxxxxxxxxxxxx <mailto:jon@xxxxxxxxxxxxx> <mailto:jon@xxxxxxxxxxxxx <mailto:jon@xxxxxxxxxxxxx>>> wrote:
>> >>>
>> >>>             That sounds like a bug (if there is invalid data like that, we should deal with it in a better way)
>> >>>             It sounds like it might be easy to make a trivial test case to attach to a bug report without using your employer's board as-is
>> >>>             (maybe by removing everything manually from the kicad_pcb file except for the hole in question and the board outline?)
>> >>>
>> >>>             I can't take a look at this right this moment, but I could in the next few days if no one else jumps on it first.
>> >>>
>> >>>             -Jon
>> >>>
>> >>>             On Mon, Apr 16, 2018 at 4:35 PM, Michael McCormack <mike@xxxxxxxxxx <mailto:mike@xxxxxxxxxx> <mailto:mike@xxxxxxxxxx <mailto:mike@xxxxxxxxxx>>> wrote:
>> >>>
>> >>>                 This might not be quite the right place to post this, but, I've found something that is a slightly problematic with Kicad and board file.  I have a PCB that has a NPH hole located off the board, I can't see it or select it inside PCBNew, however, it gets a hole in the gerbers and I can find it in the kicad_pcb file if I open the file with a text editor.
>> >>>
>> >>>                 As it is my employer's board, I can't see them being OK with me creating a bug report and posting the board file for just anyone to see; but, as I have used Kicad myself probably a decade I'd send it to someone to evaluate if it would help the project.
>> >>>
>> >>>                 Is anyone interested?
>> >>>
>> 
>> 
>> -- 
>> Jean-Pierre CHARRAS
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~kicad-developers <https://launchpad.net/~kicad-developers>
>> More help   : https://help.launchpad.net/ListHelp <https://help.launchpad.net/ListHelp>
> 
>